Getting a different SSL Cert than is listed in my webadmin SSL

1

So as the topic says.

“Getting a different SSL Cert than is listed in my webadmin SSL.” I have the LE cert that axigen generated, but i can not access my webadmin from say webadmin.example.com (obviously its not example.com, but you know what i mean.) Is there any fix to this, anything i need to provide to provide more insight into this? I got the webmail working just fine, but the webadmin won’t work at all, keeps redirecting to a different cert.

2

Hello,

Most probably this is because the WebAdmin SSL service listener (default on port 9443) is configured with the same certificate like the hostname used for the WebMail interface.

Thus, the first step should be to generate a LE certificate for your webadmin hostname.

Did you already execute this step?

This could be done via CLI or via WebAdmin > Security & Filrtering > SSL Certificates > Add > Generate a new SSL certificate + Let’s Encrypt > Hostname = webadmin.example.com

Obviously you have to be sure that webadmin.example.com is set in DNS accordingly (please double-check it) otherwise the certificate could not be issued by LE.

BR,
Ioan

3

So, the Webadmin has the cert for both IPV4 and IPV6 for Webadmin.example.com, and Webmail has a cert for IPV4 and IPV6 for Webmail.example.com, and they were pointing correctly to the host within dns and i had certs before i asked the question for both domains, and both were configured properly.

4

Hello,

In this case all should be fine.

Assuming that your WebAdmin service have a SSL listener on 0.0.0.0:9443 configured with the certificate of webadmin.example.com than, if you are connecting with a web browser to the following URL: https://webadmin.example.com:9443 than you should be presented with the WebAdmin interface + the correct certificate.

If this is not the case please share your axigen.cfg file so we could see if anything is not set up correctly.

Thx,
Ioan

5

axigen.zip (4.9 KB)
Here is my CFG, had to zip it up as the .cfg is not allowed to be uploaded to the forums, And i am sure that the 9443 is configured correctly with webadmin.

Tho anytime i try, i get a invalid certificate when i try. (I may be doing something totally stupid, but as far as i can see, everything is correct.)

6

Hello,

First of all you do not need at all example.com subdomains like webadmin.example.com and all the other ones - so you could safely delete them (before this please set example.com as your primary domain).

Secondly have you tried to connect to https://webadmin.example.com:9443 ?

:information_source: Please pay attention to: https AND 9443 port.

I’ve done (changing of course with your domain instead of example.com) and the certificate is the correct one (for webadmin).

If you still have problems please present the screen captures in which we could see the browser URL and the certificate details as most probably there is a misunderstanding somewhere.

HTH,
Ioan

7

So 9443 works if the port is included for SSL, without it, it does not. Pictures provided.

  1. Without the port

  2. With the port

  3. Both pages with the same certificate info.

    opera_hNFj4bVGgW
    opera_hNFj4bVGgW405×510 10.6 KB

(As a note, can’t upload all of these in images or just links as im a new user, so i have to do it this way. )

8

Hello,

From all you shared I see that all is fine as you have ALWAYS to use the 9443 port to connect on WebAdmin interface.

If you are connecting without specifying the 9443 port than the connection will be routed to the WebMail interface where you have the webmail certificate.

Just to summarize - you have to use the following URLs:

HTH,
Ioan

9

Ah so i can’t use webadmin.fioregaming.com by itself to connect, i have to use the port to connect, got it.

Thank you for your help, much appreciated.

1 Like