503, 403 and 401 errors: But why?

[Scepticalscribe]

@Scepticalscribe and @SandboxGeneral the 503s should be resolved. There are some coding errors causing the error but we made some tweaks to stop the errors from occurring altogether. If it happens to pop up again, please let me know.

With pleasure.

And thank you.

 

[Scepticalscribe]

And yet another "503" Error showed up this afternoon.

 

[S.B.G]

Another one when I clicked to reply to the thread 'What Movie Are You Watching' in the Community Forum.

 

[HDSam]

Thank you both. It appears the coding error still exists. I'll let the dev team know to see if it can be resolved as quickly as possible.

 

[Scepticalscribe]

Thank you both. It appears the coding error still exists. I'll let the dev team know to see if it can be resolved as quickly as possible.

Yes, I came across one yesterday also.

I suspect that it has been reduced as I now seem to come across it a lot less then when it was initially reported, but it still turns up - in the 'movie' thread, and - I think - either the books or TV thread.

 

[Scepticalscribe]

Another 503 has just appeared, this time in the Movie thread.

 

[Scepticalscribe]

Just now, in the "Wine & Beer" thread (community section) another '503 Error" flashed up at me.

 

[Scepticalscribe]

Another "503 Error" materialised in the Petite iPhones thread, while I had considerable difficulty in opening a page, clicking on 'likes' and making a post in the same thread.

 

[Weaselboy]

Another "503 Error" materialised in the Petite iPhones thread, while I had considerable difficulty in opening a page, clicking on 'likes' and making a post in the same thread.

I'm seeing the error also. I've alerted the admins.

 

[Scepticalscribe]

I'm seeing the error also. I've alerted the admins.

Thanks; much appreciated.

 

[Scepticalscribe]

And another one appeared this morning: In the "what are you reading thread"?

 

[Scepticalscribe]

And another appeared in the "Picture of the Week - Weekly Photography Contest" when I paid a visit there, this evening.

 

[Scepticalscribe]

A "503 Error" materialised (plus a stall leading to a possible double post) in the "Favourite Whisky" thread just this very minute.

 

[1050792]

Today the forum is almost inaccessible, very slow loading and lots server overload errors.

 

[C DM]

Today the forum is almost inaccessible, very slow loading and lots server overload errors.

Been seeing that too for a little while, although it seems to have gotten more or less back to normal just recently.

 

[Scepticalscribe]

Today the forum is almost inaccessible, very slow loading and lots server overload errors.

Been seeing that too for a little while, although it seems to have gotten more or less back to normal just recently.

I'm seeing this as well, plus freezing, hanging, stalling (and, as a consequence) double posts which are a bit of a nuisance.

 

[Scepticalscribe]

Another "503 Error" put in an appearance today in the long thread in PRSI that is discussing the Senate hearings on a possible appointment to the SCOTUS.

 

[Apple fanboy]

I just had it in the UK iPhone XS preorder thread.

 

[Mac'nCheese]

Just got one in the pc forum, thread DIY Pc Gaming thread on my iPhone. Hit refresh and it worked fine so no biggie. Wasnt sure if someone is tracking these.

 

[Scepticalscribe]

Another 503 made an appearance - fleeting - this morning in (I think) the espresso thread.

 

[Scepticalscribe]

Just this very minute I received a "503 Error" in the What's On Your Mind Thread of the Community section of the forum.

 

[Scepticalscribe]

And yet another "503 Error" has just made an appearance in the "What's For Dinner?" thread of the Community section of the forum.

 

[Scepticalscribe]

Another "503 Error" in the Wine & Beer enthusiasts thread.

Also, the forum has been stalling when I tried to press "post reply" in the same thread.

 

[D.T.]

It's [very likely] not thread/area/forum specific, it's just a resource contention issue, it can kind of happen anywhere, in fact, I had one in a Mac area the other day.

 

[Scepticalscribe]

It's [very likely] not thread/area/forum specific, it's just a resource contention issue, it can kind of happen anywhere, in fact, I had one in a Mac area the other day.

Agreed, but when I report them, or anyone else reports them, I have been asked (by the staff) to specify just where the error occurred.