Sites do not load after IP change
After we assign a dedicated IP to websites, we run into a problem. Users cannot access webpages without either placing https://* in front or www.* in front. Simply trying to access the site via http://domain.com loads cpanels default webpage instead of the actual sites homepage. We've rebuild Apache's configuration file by running /scripts/rebuildhttpdconf and that didn't solve anything, we also flushed all our DNS's. Any ideas?
-
Is the IP change something that was done recently (past 24 hours or so)? If so, it may well be that the DNS changes are still propagating and you are visiting the site on the old IP address. Type the domain into [url=http://www.intodns.com/]intoDNS . Does it return any errors? Does it report the correct (new) IP address? 0 -
[quote="LDHosting, post: 1619912">Is the IP change something that was done recently (past 24 hours or so)? If so, it may well be that the DNS changes are still propagating and you are visiting the site on the old IP address. Type the domain into [url=http://www.intodns.com/]intoDNS . Does it return any errors? Does it report the correct (new) IP address?
Yes, it was done less than 24 hours ago. However, DNS isn't the problem. If we ping the site via Terminal, the correct IP appears. We've also done a DNS lookup and all the information found there is correct. I noticed that the site will load if you enter "https://site.com", "https://www.site.com", or "http://www.site.com." Only0 -
Have you tried accessing on a phone or computer that hasn't been to the site before? Sounds like a local cache problem. Sometime it is just impossible to get to a site when the IP changes because it is stuck in the PC's cache. You can try clearing the cache with something like CCleaner, but their is no guarantee that will work. Normally, you'll get some kind of cPanel screen that makes it look like there is an error on the server, but really it is just a silly cache issue. 0 -
Yes, Same problem for me. Please help me for this type of problem. 0 -
Serra was right. It was a local cache problem. It's solved now. Thank you. 0 -
I am happy to see the issue is now resolved. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
6 comments