Sorry page when opening from same subnet as server
Freshly installed cPanel on a centos VM, all updates applied.
When trying to reach certain websites from a server residing on the same subnet as the cPanel server we get the "Sorry" page informing that the website might be moved, IP changed etc.
Trying to reach the same website externaly works perfectly fine. I've verified that the DNS resolves correctly.
I see in the access_log in /var/log/apache2 that I get entries from the client with the correct domain.
Some websites work as expected, some dont.
Any thoughts to what could cause this?
-
Further investigation shows that this problem only exist for the main domain on the server. In other words, the domain used in the hostname of the server. Subdomains of that domain and other domains seems to work fine. Weird thing is if I do domain.com/cpanel I do get the redirect to domain.com:2083 The client "server" in this case is an administration windows server, so being able to test all websites on the cpanel server is needed =) 0 -
It almost sounds as though there may be a routing/caching issue, I'd suggest you bring this to the attention of your provider since it works externally. 0 -
It almost sounds as though there may be a routing/caching issue, I'd suggest you bring this to the attention of your provider since it works externally.
I manage this server myself, its a colocation server with several VMs on it, including a cPanel VM. Routing is fine, able to open every other webpage/customer page on the cPanel server. Including the management page as well as the problematicdomain.com/cpanel (gets redirected to problematicdomain.com:2083) So I can't see how this is not an issue with hostheader/webserver or similar. Though I can't see a difference between the problematic domain and every other domain. As mentioned, access_log on the server itself (so anything not matched to a customer) does get the hits when I try henche the "sorry page" it shown. Due to the incoming http request can't be matched to a customer.0 -
Hello @HelgeR , Could there be a hosts file entry or local DNS on the server you're connecting from that could cause the request to go to the wrong IP? Virtual host matching goes by IP and port first, so the connection coming in on the wrong IP could cause it to miss the intended virtual host. This is described further in the Apache documentation 0 -
Hello @HelgeR , Could there be a hosts file entry or local DNS on the server you're connecting from that could cause the request to go to the wrong IP? Virtual host matching goes by IP and port first, so the connection coming in on the wrong IP could cause it to miss the intended virtual host. This is described further in the Apache documentation
0 -
Hello @HelgeR , Thanks for the update. I'm glad to hear you got it sorted out. 0
Please sign in to leave a comment.
Comments
6 comments