Changed IP, can't access site

[ikouhsdfikuh]

So, I changed the IP (from a shared IP to a dedicated) of a page/account, everything went fine. Waited for the IP to propagate (almost 5 days today), but it doesn't work despite whatsmydns.com telling me that the new IP A-record has been correctly registered. The DNS A-record is indeed correct (checking the account in WHM), but accessing the domain only yields the following error page: - Removed -

Entering the new IP doesn't work either.

I suspect the fix is pretty simple, but I have no clue how to approach this. Suggestions?

 

[cPanelMichael]

Hello,

Does the website resolve to the same IP address that it's assigned in WHM? If so, let us know if the following command helps:

/scripts/rebuildhttpdconf

Thank you.

 

[ikouhsdfikuh]

I have the same problem... So, if the website's A-record resolves to the correct (newly assigned) IP when pinging the domain, I should try running the above script?

 

[ikouhsdfikuh]

So, 10 hours ago I changed the IP of a site through WHM. Everything went fine and the associated webmail sends from the new IP. The site is not yet available, though.

What's presented is the "SORRY!" cPanel error page.
Seeing as this could be the ISP's ageing DNS records, I've tried with 3 different ISP's, all showing the same result.

The domain's pointing to the IP properly through pinging and the site is available through the WHM "List Accounts" interface, when clicking the site's IP (which is the new one). - That makes me end up at [NEW IP]/~[USERNAME]/

The A-record has a TTL of 4 hours, whereas the SOA-record has a life time of 24 hours.

It's pretty important that the site gets online ASAP.

Should I take a breather and wait until 24 hours has passed or is this possibly an error somewhere?

 

[24x7server]

Hello,

I will suggest you please try to check your domain through proxy site. I think due to to browser cache you are getting cPanel default page at your end.

 

[cPanelMichael]

Hello

You can try rebuilding the Apache configuration file via:

/scripts/rebuildhttpdconf

Let us know the outcome.

Thank you.

 

[ikouhsdfikuh]

Hello,

I will suggest you please try to check your domain through proxy site. I think due to to browser cache you are getting cPanel default page at your end.

I tried through different ISP's, proxies, browsers and devices. Nothing worked. However:

Hello

You can try rebuilding the Apache configuration file via:

/scripts/rebuildhttpdconf

Let us know the outcome.

Thank you.

Did the trick. Thanks a lot.

BTW: Pretty crazy that I actually replied to my own thread, completely without noticing. I guess it worked back then as it does today - I'm sorry for not responding originally.

Again thanks a lot for the help, really appreciate it.

 

[cPanelMichael]

I am happy to see the issue is now resolved. Thank you for updating us with the outcome.