[QUOTE=James Heinrich;563511]Hey, that's clever! It works in Incognito.[/QUOTE]

Well, not here. I had already tried it, and did it again just now, but to no avail.

[QUOTE=lycorn;563538]Well, not here. I had already tried it, and did it again just now, but to no avail.[/QUOTE]I fixed my Chrome weirdness: I deleted all site cookies for mersenne.ca and now it magically worked.

And then, for no reason I can fathom, my computer suddenly decided just now that mersenne.ca should be at the old 74.* IP. No idea why. I've just updated the DNS config for mersenne.ca on the old server to point to the new IP, requests should even be getting to the old server but just in case they do that may help fix it. I'll be taking the old server offline in a couple days and then (one hopes) the probably should go away entirely.

It's FAST!!!!

[QUOTE=James Heinrich;563589]I fixed my Chrome weirdness: I deleted all site cookies for mersenne.ca and now it magically worked.

And then, for no reason I can fathom, my computer suddenly decided just now that mersenne.ca should be at the old 74.* IP. No idea why. I've just updated the DNS config for mersenne.ca on the old server to point to the new IP, requests should even be getting to the old server but just in case they do that may help fix it. I'll be taking the old server offline in a couple days and then (one hopes) the probably should go away entirely.[/QUOTE]

Some ISP recursive resolvers don't respect short TTLs, especially under 60 seconds. When I looked at your DNS records earlier they were all set to 3600, so that shouldn't normally be a problem. And I think most of the problem resolvers have disappeared because DNS isn't a big bandwidth load like it used to be, and much of the modern internet would break.

I'd try power cycling your router. I'd also try `ipconfig /flushdns` on Windows if that's what you run.

So, things [I]were[/I] working fine, and then this morning they seem to have fallen apart again. Gmail alternates between knowing what mersenne.ca is and having no idea it even exists. I assume there's some DNS still pointing to the nonexistent old server that's slowly bleeding out and that it should eventually resolve itself, but it's highly frustrating.

This morning, around 10:30 am or so, I managed to connect. The site was apparently OK, except for the data tables that weren't showing up. Some other functionalities I tried were fine. Now (20:35) the site is again out of reach.

DNS is not my friend. I've been fighting with it, and GoDaddy tech support, as to how I should have it configured. It's still half-working, sometimes more, sometimes less:
[url]https://dnschecker.org/#A/ns1.sili.net/198.251.72.75[/url]

Good news, I think. I found a secret setting in GoDaddy DNS's management page that I needed to change. Sadly despite two support chats with them describing the issue they never once pointed me in the right direction. DNSchecker.org is now showing me 100% correctly resolved, so I think that part of the problem is (finally) resolved.

I still have a plethora of other migration headaches to deal with, but none (I think) that affect mersenne.ca

Everything fine here 👍

I am planning one more big database shuffle tomorrow, starting sometime around 12h from now. I will be taking the site down for however long it takes, which I'm roughly estimating at around 3h but it might be longer.

Hmm,... If it is working, don't fix it. 😁
Or is it not?
Good luck, anyway.