In my old mail server on Windows Server, I did not have to add a port number after the webmail domain name. If I wanted to access webmail, I just went to:
In most cases that I’ve seen here, it has to do with your listeners and which ports that are set up for WebMail. If they are correct, check to see if they’re enabled.
I do have the listeners setup on ssl ports. I have a main domain, SSL with LetsEncrypt.
So, example.com and www . exa mple.com is secured with SSL on Apache - Unbuntu
(domain spaces deliberate)
The domain is using ports 80, and 443, (SSL), so those ports are being used by Apache.
I have Axigen setup for ports 8080 and 4343, (SSL)
But if I load a web browser and go to:
www. example . com:4343 ssl does not work I had to setup a self signed cert which works, but browsers say it is not trusted because it does not come from a CA.
I tried to get a LetsEncrypt through Axigen but that never worked.
Let’s Encrypt requires access to port 80 to verify you own the domain, and if the doc is still valid, Let’s Encrypt is accessing the /.well-known/acme-challenge/ path.
If you want to use your own cert, then you’ll need to load the CA root certificates on the devices or explicitly trust that cert. This is something I used to do as well, then moved to free CAs. Thankfully, with Axigen auto renewing the certificate for me, it’s been working seamlessly.