Solved Unable to login to web interface using FQDN

[sampegg]

Hi

We are unable to log into the web interface using the FQDN. Using the public IP works fine. I suspect with have an issue the 3CX provided SSL cert.

As this is a 4SC system we are unable to log a support ticket.

I'm totally stuck and unsure how to proceed from here.

Any advise appreciated.

Thanks

 

[NikosT_3CX]

@sampegg put your FQDN here " https://dns.google/ ", does it resolve to the correct public ip ?

 

[sampegg]

@sampegg put your FQDN here " https://dns.google/ ", does it resolve to the correct public ip ?

yeah it's resolving fine already checked that.
Looking like it might be a rebuild job tonight.

 

[bitn2]

Is the firewallcheck green? Where is the pbx installed?

 

[sampegg]

Is the firewallcheck green? Where is the pbx installed?

Yeah firewall check OK ran that this morning (should have put that on the original post!)
Self hosted in our DC

 

[paulodagraca]

Hello sampegg,

when you say: unable to log into what do you exactly mean?
Does the webpage show, or just goes blanc ? error received?
Can you clean the cache of the browser? try another browser?

Basically using the FQDN or IP, does make make any difference, also the FQDN should go to the (same) correct IP.

Paulo

 

[sampegg]

Hello sampegg,

when you say: unable to log into what do you exactly mean?
Does the webpage show, or just goes blanc ? error received?
Can you clean the cache of the browser? try another browser?

Basically using the FQDN or IP, does make make any difference, also the FQDN should go to the (same) correct IP.

Paulo

Just get general network error as in screen shot below

Browser not applicable, it does this on many devices even those that will have never accessed it before.

FQDN resolved to the correct address. We can log in if we use the public IP instead, but of course we get the red warning banner. As all users are using the web interface this is not ideal. As it works with the public IP and not the FQDN this us why I suspect this is a certificate issue.

 

[paulodagraca]

Hello sampegg,

I do not know your setup, so I am trying to think 'out of the box'.

Could it be any problem with IPv6 ?
Meaning, when you go to the IP (that would be IPv4), the server does responde correctly, and when you go to the FQDN, it can be using the IPv6, and that could be not setup correctly in the firewall ????

So, does the server have any IPv6 setup, if yes, does the 3CX installation has this in the config, and does the Firewall have any rule for this?

Paulo

 

[sampegg]

Hello sampegg,

I do not know your setup, so I am trying to think 'out of the box'.

Could it be any problem with IPv6 ?
Meaning, when you go to the IP (that would be IPv4), the server does responde correctly, and when you go to the FQDN, it can be using the IPv6, and that could be not setup correctly in the firewall ????

So, does the server have any IPv6 setup, if yes, does the 3CX installation has this in the config, and does the Firewall have any rule for this?

Paulo

Hi
No IPV6 here.

 

[paulodagraca]

Hello ,

You could try to re-create the SSL cert.
https://www.3cx.com/community/threa...ts-encrypt-ssl-certificate.134084/post-639598

This link will give you the information for a Linux server, if you have a Windows server please try to find the same or ask here, I will be able to find that as well.

Paulo

 

[sampegg]

Hello ,

You could try to re-create the SSL cert.
https://www.3cx.com/community/threa...ts-encrypt-ssl-certificate.134084/post-639598

This link will give you the information for a Linux server, if you have a Windows server please try to find the same or ask here, I will be able to find that as well.

Paulo

Fantastic that has resolve the issue, thanks very much