Can't access SJ

I switched the site over to a new server last week that had double the CPU cores and double the memory capacity. My server logs show that since the move, the site is loading 5%-15% faster for 95% of visitors.

For problems accessing the site on a mobile phone, most likely your mobile provider hasn't updated to the new server address behind the scenes--this is very common with mobile phone providers who heavily cache server addresses for up to several weeks (even though I specifically set it so they're supposed to recheck the server address every 5 minutes). There's nothing I can do there other than wait it out for your mobile providers to update their DNS cache.

@spikechiquet - I also moved the site back to www.sportsjournalists.com from the non-www version to fix a few other small issues that were cropping up. Try manually typing that in on your home browser and see what happens? If you get redirected to the non-www version, then the problem is that Chrome/Firefox still have the old www to non-www redirect cached. IIRC, they'll keep it cached til the end of time, so likely you'll need to reset more browsing data in chrome. If you don't get redirected to the non-www version, and you stay on the www version, then it's something else... since you're on desktop, and not mobile internet, rare that a desktop ISP will cache longer than 24 hours unless they're told to by the website. Who is your internet provider?

 

@spikechiquet Thanks for checking. Weird.

Have her try a 'traceroute www.sportsjournalists.com'. Just run that command from the Mac terminal. It'll show the ping times to the various servers in between your computer and the SJ server... can help isolate whether the bottleneck is your router, ISP, someone intermediate, or the SJ server.

Can you also try 'dig www.sportsjournalists.com'? It'll show which DNS server is giving you the results, and where it currently points... If you can PM me the results of both commands, either text or screenshot, then I can diagnose further.

 

I've triple-checked and there's nothing wrong with the server or DNS routing. I've tried a number of external services, and they all report everything is fine accessing the server--for example: downforeveryoneorjustme.com/www.sportsjournalists.com

These issues are almost certainly caused by DNS caches in your ISP, your home router, or your device that still have the old IP address from the last server before I migrated. Since it's been this long, I suspect it's your home router DNS cache as your ISP should have updated their caches by now. You can verify it's the router and not the device by using the device both at home and at work and if it works one place but not the other then the cache issue is most likely in the router. @spikechiquet if you can get your wife to run those commands we can verify where the issue is... should take her less than 5 mins as they're simple diagnostic output where she just types in the commands and copies/pastes the output.

The way to reset your home route DNS cache depends on the router... I'm guessing you've already tried power cycling the device, make sure to power cycle your modem as well as it could also be the source of the bad cache. If power cycling aka soft reseting doesn't do it, then you may have to either do a hard reset or login to the admin panel and figure out where the DNS setting are and play around with them... it really depends on the model of the router and not something I can easily walk you through from a distance.