Migrating domain from old to new account throws 404 error

Hosting Support
1

Website URL

realsportsinteractive.gt.tc

Error Message

Connecting to IP:

This page isn’t working
xxx.xx.xxx.xxx didn’t send any data.
ERR_EMPTY_RESPONSE

Connecting to domain:

404!
We couldn’t find that page.
Please check to make sure you’ve typed the URL correctly.

This webserver is CaSe SenSiTiVe so ensure capital letters in the URL match the files uploaded.

Other Information

I removed the domain from my old account, and moved all of the source code onto my new account. When I try to connect to the domain, I don’t get a DNS error, rather I get a 404 error. I’ve quadruple checked - my index.html is in the htdocs subfolder of my domain folder, like InfinityFree instructed me to. Is this an issue on my end or InfinityFree’s end?

2

Welcome to the forum

image
image1084×967 46.6 KB

Working fine for me. Try clearing your browser cache, and if possible your PC’s DNS cache. It might be that you’re holding an old version of the site or an old ip causing the error

3

Hi, I’ve done that already (many times, through Windows, using Incognito, etc.)
Thanks for your help, seeing that you can access it is helpful. I’ll try accessing from different devices and seeking other options

4

@dan3008

Could it be possible you’re loading the old website? If you try to go to the Administrator Login page, show me if it says ‘Network error’ or just ‘Invalid password’. If it shows Network error, you’re on the old website from my old account.

5

The only way I’d be seeing the old site, is if DNS propagation hasn’t completed. Which is completely possible.

Because I’ve never visited your site before, then I will be getting the version that is currently showing everywhere.

6

I looked up the domain name and I see domain was added to the current account only 30 minutes before posting this message.

As you can see in the client area when you check the Health Check section for this domain: it can take up to 72 hours for a new domain name to start working everywhere.

This is due to DNS caching. And yes, for these purposes: a domain that was removed from one account and added to another is effectively a “new” domain.

So please have patience. Nothing is wrong and your website will start working automatically for you too. But that can take some time, up to 72 hours but usually much less.

7

@Admin So, the 404 error was just an issue with the DNS propagation? Alright. I’ll check back on the website soon! Thank you for your response and thanks for the amazing platform

8

@Admin @dan3008

Why is it throwing a 404 error and not a DNS error?

9

Simple, the url is still pointing at the old account. So when it requests the page, and the server can’t find it, it returns 404.

You’ll only see a DNS error if the DNS servers can’t find where the domain should be pointing

10

C:\Users\User>nslookup realsportsinteractive.gt.tc 9.9.9.9
Server: dns9.quad9.net
Address: 9.9.9.9

Non-authoritative answer:
Name: realsportsinteractive.gt.tc
Address: 185.27.134.112

C:\Users\User>curl -I http://realsportsinteractive.gt.tc
curl: (52) Empty reply from server

When checking in the terminal, it said that the website was visible to my DNS, but when using curl, it returned an empty reply.

I still have the 404 error even after flushing my DNS, restarting my computer, booting from my Linux installation, using a VPN, etc.

For many other people that I’ve asked (who have never opened the website in their lives), the old website still loads instead of the new one.

I’ve also tested on Cloudflare’s DNS server (1.1.1.1) which is supposed to be ‘mainstream’ and it’s still not working.

Is there something deeper to this?

11

Adding onto this with more testing:

C:\Users\User>nslookup realsportsinteractive.gt.tc
Server: UnKnown
Address: _________

Non-authoritative answer:
Name: realsportsinteractive.gt.tc
Address: 185.27.134.112

C:\Users\User>ping 185.27.134.112

Pinging 185.27.134.112 with 32 bytes of data:
Request timed out.

This means:

  • DNS resolved successfully.
  • A connection was made to… something?
  • Server closed the connection without a response.
12

I’m almost certain that the issue is after DNS resolution, but let me know if I’m wrong

13

In a way you’re not wrong, but you are also very wrong.

DNS is currently pointing to your old site. this is global DNS servers, not something you can change on your pc, and not something InfinityFree can change.

you’ll need to wait for these to be updated which can take up to 72 hours

Also you can’t ping free hosting servers. they are set up specifically to ignore pings.

14

This is what’s making me suspicious.

15

Noted

16

I’ve tried the ‘fastest’ DNS-es out there (and I’m pretty sure the people I’ve contacted have them too, by default), though the old site is still loading in. This should be an issue because they usually are quicker to update than other DNS servers. I made this thread 4 hours ago. The Owner of InfinityFree said I made the website 30 minutes before that. That’s 4 and a half hours of the DNS not propagating on the fastest servers. I don’t know if that’s how it works, or if it’s an issue

17

DNS propergation can take up to 72 hours. Even the fastest servers don’t update quickly. particularly not when a domain is being updated rather than created.

4 and a half hours is nothing.

18

cURL not working is to be expected, the security system blocks everything except actual web browsers from accessing your site.