https on custom port

Discuss and get help to configure CacheGuard to protect Web servers
Post Reply
tdurham
Posts: 2
Joined: 03 Feb 2016 15:34

https on custom port

Post 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.
User avatar
david
Posts: 163
Joined: 08 Aug 2015 20:38

Re: https on custom port

Post 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
David Janeway
CacheGuard Technical Team
https://www.cacheguard.com
Post Reply