Talk:403.shtml

Why people are being sent here

I'm 99% sure that this is some sort of typo or something in the code blocking edits when it's nighttime in the US. When I try to edit after 11 I get sent here. I think it should be 403.html, but an actual error page. Sievert 81 (talk) 22:51, 7 October 2020 (EDT)

I don't think it is related to night mode. I'm excluded from night mode but still get this error, and not always at night. The HTTP 403 error code indicates that for some reason, access to a requested resource was rejected. Since this only started happening recently along with our other database issues, my guess is that the database is getting overloaded, and rejecting some requests. I'm not certain though--that's just a guess. It would make more sense if it was timing out, instead. --DavidB4 ^(TALK) 22:49, 7 October 2020 (EDT)

It could be that too, but that is consistent for me. I've never got 403.shtml when it's not in night mode. This page was created and deleted in 2006 so this issue has been happening at least since then. Sievert 81 (talk) 22:51, 7 October 2020 (EDT)

Well, that is interesting, Sievert. I'll pay better attention to when it happens to me.

LiberalTears, the problem with mentioning pressing F5 repeatedly is that at this point, you are already on a different page. You will simply be refreshing this page. If you go back to that one without being redirected, then perhaps multiple refreshes will solve other issues, like the CSS not loading in. However, I'm not certain if that tip fits well on this page. --DavidB4 ^(TALK) 00:33, 8 October 2020 (EDT)

Oh, alright. —LT^{May D.C., his mother, and I.S. be all well!} Thursday, 07:47, 8 October 2020 (EDT)

There are times when I can't view the web page using a web browser on a computer, but it seems to usually work just fine if I open it on a phone browser in the same moment. Progressingamerica (talk) 09:10, 8 October 2020 (EDT)

Good point, using a different connection tends to work just fine. --DavidB4 ^(TALK) 16:27, 8 October 2020 (EDT)