Page 1 of 1

https on custom port

Posted: 04 Feb 2016 01:26
by tdurham
Using rweb (reverse proxy) to access some cPanel and Virtualmin resources (servers admin panels) I'm having trouble setting up https to occur over a non-standard SSL port (other than 443).
Example: https://web2.example.com:2087 or https:web1.example.com:10000

Is there a processes to get this handled in the CacheGuard Reverse Web Configuration?

Your assistance is greatly appreciated.

Re: https on custom port

Posted: 04 Feb 2016 08:15
by david
Hi tdurham

With the current version (v1.1.5) it's not possible. CacheGuard uses standard ports (80,443) for cloaked Web servers and can act as a SSL terminator (if needed). Some reasons for that limitation are:

- Keep a CacheGuard configuration as simple as possible.
- Minimise the number of opened ports.

I suggest you to either:

- PAT your specific ports (2087, 10000...) to CacheGuard's IP:443 on your frontal router/firewall
OR
Use specific names for each service (service1.example.com:443, service2.example.com:443...). FYI the current version (v1.1.5) supports the SNI (Server Name Indication) extension of TLS so you can use the same IP address for different HTTPS names.

Best Regards