When I open any thread successfully, I always immediately open several others in separate tabs that look interesting while I can. Then when I try to open a thread and it gets stuck, I have other threads open in other tabs I can switch to for a while instead of sitting there twiddling my thumbs. Likewise, if it gets stuck when I try to post something, I just go read another thread for a while, knowing that the stuck attempted post actually did get posted, probably. Alternatively, I can have stuff open in other tabs from other sites (like news articles) I can switch to reading.
And, as an experiment (we’re still allowed to used ATMB for test posts, right?), if it gets stuck when I post this, I’ll try again and again and see how many duplicate posts I can get out of this! Here goes . . .
Well Senegoid, when it works for you that’s good. But to be a little nit-picky that’s not a solution, it’s a workaround. I have a workaround too — from my subscriptions page, instead of selecting the last post in the trivia dominoes thread game, which is where I usually see the errors, I first select the thread OP, then select the last page, then scroll to the bottom. That workaround usually works for me.
The following errors occurred with your submission:
This forum requires that you wait 60 seconds between posts. Please try again in 60 seconds.
This bug apparently includes the system thinking I pressed Post Quick Reply 2x when I did not.
Just got the “504 Gateway Time-out shield” message when trying to read a thread by clicking on a link in an email. I clicked the email link a second time, and it worked.
(Android 10 on 1st Gen Pixel, Chrome, Wi-Fi connection)
I have not bitched about these things in the past, as I just figure the hamsters are having a bad day, but the board has been dragging for weeks now, with no relief in sight. Clicking on a topic may or may not take you to your destination, and sometimes I get the same ‘timed out’ message that others are getting. I don’t need instant gratification, but eventually getting somewhere would be nice.
Does anyone here understand the logs from a de-bugger tool like Fiddler? I have it installed and I just had another error message when taking too long to compose a post. This is the latest part of the log.
I am just a computer operator type. But it looks to me like a SDMB server issue. If anyone is more familiar with these tools, please explain what the log means.
Looks like it could be Long Handshake Intolerance. Whatever the hell that is. Or maybe not. SOMEBODY on this board should be able to use one of these tools to point in the general direction of the problem.
Here goes . . .