3 ms·
John here from ghost.org/fail - not sure what happened there! Can't reproduce, but sounds like it was a temporary DNS resolution glitch. Will keep an eye on it
by johnonolan 9y ago
John here from ghost.org/fail - not sure what happened there! Can't reproduce, but sounds like it was a temporary DNS resolution glitch. Will keep an eye on it
- jacquesm 9y agoIn case this helps to debug the problem: there was a Cloudflare interstitial page for a bit before it started to redirect to the 404 page. Also, I just re-tested and it is still not working.
- johnonolan 9y agoYeah, sounds a lot like a CF DNS resolution problem at one particular edge node. Are you able to stop the browser on the CF error page and copy/paste the RayID for me? Would be helpful for us to report upstream and ask CF to flush their DNS cache at that location :)