WHM no longer responds to server hostname, ip address still works. Help!

[jerrac]

Hey all,

For some reason, WHM is not responding when I try to visit using the server's hostname. If I visit via the server ip address, it works fine. Account cPanel's all work just fine as well. As in:

• https://cpanel.example.org:2087 times out.
• https://< ip address of cpanel.example.org >:2087 works.
• https://app.example.org:2083 works.

This started up in the past few months. It's been a low priority since I have a work around, hence why I'm only posting now.

It should not be a DNS issue on cPanel itself since our DNS is external to cPanel.

When I tail apache logs, I see no added lines when trying to visit https://cpanel.example.org:2087.

The only thing I can think of is that an update came through that did something to the apache config for WHM. Where do I go to check on that config? Specifically the part that would set the ServerName or ServerAlias values in the VirtualHost? I haven't been able to find that yet.

Anyone have any other ideas? Any specific logs you'd want me to share?

Thanks!

 

[quietFinn]

https://cpanel.example.org:2087 times out.

First you should check that the hostname resolves to your server's IP address, i.e:

nslookup cpanel.example.org

When you go to WHM you can use any hostname that resolves to your server's IP.
And it has nothing to do with Apache when you connect to WHM port.

 

[jerrac]

First you should check that the hostname resolves to your server's IP address, i.e:

It does.

When you go to WHM you can use any hostname that resolves to your server's IP.
And it has nothing to do with Apache when you connect to WHM port.

https://app.example.org:2087 times out just like https://cpanel.example.org:2087.

app.example.org resolves to my servers ip.

Thanks for the quick reply!

 

[quietFinn]

Is it the same if you try with address http://cpanel.example.org/whm ?

 

[jerrac]

Is it the same if you try with address http://cpanel.example.org/whm ?

http://cpanel.example.org/whm redirects me to http://cpanel.example.org:2086/, which times out. (I don't have 2086 open on the server or the Firewall dmz.)
https://cpanel.example.org/whm tries to use an old, expired, ssl cert, then redirects me to https://cpanel.example.org:2087. That times out.

The expired cert is odd. I updated the cert today via Home »Service Configuration »Manage Service SSL Certificates. Is there another place I need to update it?

 

[cPanelAnthony]

http://cpanel.example.org/whm redirects me to http://cpanel.example.org:2086/, which times out. (I don't have 2086 open on the server or the Firewall dmz.)
https://cpanel.example.org/whm tries to use an old, expired, ssl cert, then redirects me to https://cpanel.example.org:2087. That times out.

The expired cert is odd. I updated the cert today via Home »Service Configuration »Manage Service SSL Certificates. Is there another place I need to update it?

This might warrant a look from a ticket so we can use the actual domain names, IP addresses, and have access to the host. Would you be able to open a ticket using the link in my signature? If you provide me with the ID, I can keep this thread updated.

 

[jerrac]

:facepalm: I just resolved this. I finally thought to try another browser, and Chromium worked just fine for https://cpanel.example.org:2087 which (somehow) led to me wondering if dns over https had been turned on for Firefox. It was. Turning that off resolved my issue.

Still confused on why everything didn't break... I'd think I'd run into issues since everything would be resolving to external ip's only. And I have a lot of stuff not resolvable outside our network. Hm...

Anyway, thanks for the help everyone!

 

[cPanelAnthony]

I'm glad you got this resolved!