ujbens
By:
ujbens

Old Siteground home page showing up in Digital Ocean server

April 16, 2018 155 views
Caching Deployment DNS

I moved my site from SiteGround to Digital Ocean recently. The DNS has propagated successfully (domain.com and staging.domain.com). This has been confirmed by both the domain registrar and digital ocean. But when I go to my live site I still see the home page from Siteground ( I only had one page there as a placeholder). I can see all the other pages of my new site by typing them into the address bar, but not the home page. In trying to troubleshoot the problem, I went to Siteground and deleted everything having to do with this domain. But the Siteground home page is still showing up on the live site. The only explanation is that the page is cached somewhere. I called Siteground and they insist that it is nothing on their end, since the domain has been deleted.

More info that may help - before transferring my domain name servers to Digital Ocean on my domain registrar, I tried to redirect the domains from Siteground to Digital Ocean by creating A records (one for staging.domain.com and one for domain.com) and giving them my new Digital Ocean server's IP address. It didn't seem to work, so I went to plan B and changed the name servers on my domain registrar. I suspect Digital Ocean has that old page and is holding on to it, even though I have deleted those A records in Siteground.

One more thing - in my Siteground site in Filezilla I can see a .SGCache directory containing a cache_status file with this line: static||staging.domain.com||1. I tried to delete it but Filezilla says I don't have permission. There is also a 'staging' folder in the public HTML directory that contains a .htaccess file with rewrite conditions for the staging site.

I am a student and this is a project that I need to have done very soon. Prompt assistance would be very much appreciated!

2 comments
  • Sometimes this kind of error can be caused by cached redirects in your browser. Can you test something?

    Open up a different browser or an incognito session, and try visiting the exact correct variant of your domain:

    For example: httpS://WWW.mydomain.com/

    Does it work?

  • No, same result. I have tried several browsers and incognito windows, restarted computer, cleared browser cache, etc. over several days

1 Answer
ryanpq MOD April 16, 2018
Accepted Answer

By any chance do the files for your new site use a different extension (php vs html)? It sounds to me like the index.html file from your old site got copied over and the difference in the order that index files are pulled between the two hosts is resulting in your index.html being loaded instead of an index.php

  • Ryan, can you help please I cannot log into my account no emails are being sent for the recovery or passcode..

  • Yes! Thank you! I found the old original index.html file in the sea of files in the laravel public folder, along with the stock laravel index.php file. I changed its name to problem.html (just because I am nervous to delete anything at this point), restarted my computer and to my surprise I am still seeing the problem.html page. Any more suggestions?

  • Okay, deleting the html file did fix it after all. I was just on the wrong git branch when I pushed the change up to the server. Thank you

Have another answer? Share your knowledge.