This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Custom HTTPS port not showing up in URL

I am trying to publish an internal web server over the WAF. The setup is as follows:

  • Internal name: , reachable via Port 8089.
  • External name: (I have a public DNS record pointing to my static public ip).
  • I've created a real webserver with the internal hostname / IP as the host, Type: HTTP and port 8089.
  • I've created a virtual webserver with type: 'HTTPS & Redirect', port 8089 and a valid letsencrypt certificate for the public name.

I can access the website and login, so that worked. The first problem was that any link on the website pointed to the internal hostname. I resolved this by activating "Pass host header" in the virtual webserver. Now the links point to the correct hostname but the custom port (8089) is missing so when I click on a link it tries to establish the connection via port 443. What am I missing?

This thread was automatically locked due to age.
Parents Reply Children
  • It shouldn't be a problem having more than one server listening on the external 443 port. The mapping is done by WAF based on the certificate and the real server.
    I host several external domains all resolving to one IP / port 443
    Internally they are mapped to ports 8281, 8282 etc.

    Grtz, Peter-Paul

    SFVH (SFVH (SFOS 18.0.4 MR-4) - Up since february 4th 2020
    [If any of my posts are helpful to you please use the 'This helped me' link]