# Recent server timeout errors — anyone else getting them? **URL:** \ **Category:** About This Message Board\ **Created:** [December 7, 2019, 4:13pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514 "2019-12-07T16:13:54Z")\ **Posts on this page:** 20\ **Page:** 13
**Author:** ![Senegoid](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/senegoid/32/6606_2.png) [@Senegoid](https://boards.straightdope.com/u/Senegoid)\ **Post date:** [January 7, 2020, 4:26am UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/241 "2020-01-07T04:26:18Z")
I found the solution: 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 . . . ETA: Well, dang! It worked the first time. ---
**Author:** ![Bullitt](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bullitt/32/5725_2.png) [@Bullitt](https://boards.straightdope.com/u/Bullitt)\ **Post date:** [January 7, 2020, 5:07am UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/242 "2020-01-07T05:07:40Z")
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. ---
**Author:** ![Bullitt](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bullitt/32/5725_2.png) [@Bullitt](https://boards.straightdope.com/u/Bullitt)\ **Post date:** [January 7, 2020, 7:52pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/243 "2020-01-07T19:52:21Z")
502 Server Error Error: Server Error The server encountered a temporary error and could not complete your request. Please try again in 30 seconds. ---
**Author:** ![margin](https://avatars.discourse-cdn.com/v4/letter/m/65b543/32.png) [@margin](https://boards.straightdope.com/u/margin)\ **Post date:** [January 7, 2020, 10:53pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/244 "2020-01-07T22:53:41Z")
Yeah, just got a server error that ate my bloody comment. It doesn’t seem to be logging me out, though. ---
**Author:** ![Bullitt](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bullitt/32/5725_2.png) [@Bullitt](https://boards.straightdope.com/u/Bullitt)\ **Post date:** [January 8, 2020, 3:28am UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/245 "2020-01-08T03:28:45Z")
> [@margin](#): > > Yeah, just got a server error that ate my bloody comment. It doesn’t seem to be logging me out, though. None of the errors I got ever logged me out. ---
**Author:** ![Kent\_Clark](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/kent_clark/32/105_2.png) [@Kent\_Clark](https://boards.straightdope.com/u/Kent_Clark)\ **Post date:** [January 8, 2020, 5:17pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/246 "2020-01-08T17:17:23Z")
**Error: Server Error The server encountered a temporary error and could not complete your request. Please try again in 30 seconds.** That started about five minutes ago, and since then I’ve gotten the message three times. I’m not even trying to post, just read threads. ---
**Author:** ![Bullitt](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bullitt/32/5725_2.png) [@Bullitt](https://boards.straightdope.com/u/Bullitt)\ **Post date:** [January 8, 2020, 7:04pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/247 "2020-01-08T19:04:57Z")
Just now, at 1104U hrs: **504 Gateway Time-out shield** ---
**Author:** ![Bullitt](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bullitt/32/5725_2.png) [@Bullitt](https://boards.straightdope.com/u/Bullitt)\ **Post date:** [January 8, 2020, 7:07pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/248 "2020-01-08T19:07:01Z")
That was followed up with this, at 1106U hrs: **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. ---
**Author:** ![WolfpackJeep](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/wolfpackjeep/32/2921_2.png) [@WolfpackJeep](https://boards.straightdope.com/u/WolfpackJeep)\ **Post date:** [January 8, 2020, 7:19pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/249 "2020-01-08T19:19:00Z")
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) ---
**Author:** ![Bijou\_Drains](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bijou_drains/32/2814_2.png) [@Bijou\_Drains](https://boards.straightdope.com/u/Bijou_Drains)\ **Post date:** [January 8, 2020, 8:21pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/250 "2020-01-08T20:21:50Z")
Is there any evidence anything is being done to fix the problem? I know the site is free to me. But it is getting more and more frustrating. ---
**Author:** ![Bijou\_Drains](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bijou_drains/32/2814_2.png) [@Bijou\_Drains](https://boards.straightdope.com/u/Bijou_Drains)\ **Post date:** [January 8, 2020, 9:57pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/251 "2020-01-08T21:57:58Z")
> [@Bijou\_Drains](#): > > Is there any evidence anything is being done to fix the problem? I know the site is free to me. But it is getting more and more frustrating. To clarify it would be nice to know they tried , X,Y,Z etc. ---
**Author:** ![TheCuse](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/thecuse/32/2854_2.png) [@TheCuse](https://boards.straightdope.com/u/TheCuse)\ **Post date:** [January 8, 2020, 11:50pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/252 "2020-01-08T23:50:50Z")
twice in the last five minutes. ---
**Author:** ![Bullitt](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bullitt/32/5725_2.png) [@Bullitt](https://boards.straightdope.com/u/Bullitt)\ **Post date:** [January 9, 2020, 2:23am UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/253 "2020-01-09T02:23:39Z")
504 Gateway Time-out shield Just now. Laptop, Win 10 pro, Chrome, wifi. ---
**Author:** ![Bijou\_Drains](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bijou_drains/32/2814_2.png) [@Bijou\_Drains](https://boards.straightdope.com/u/Bijou_Drains)\ **Post date:** [January 9, 2020, 6:03pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/254 "2020-01-09T18:03:40Z")
since nobody will post what is being done to fix the issues I assume the answer is nothing is being done. I guess that’s OK since I don’t pay to be here, but I would pay if given the chance. ---
**Author:** ![Chefguy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/chefguy/32/138_2.png) [@Chefguy](https://boards.straightdope.com/u/Chefguy)\ **Post date:** [January 9, 2020, 6:05pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/255 "2020-01-09T18:05:22Z")
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. ---
**Author:** ![ftg](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ftg/32/2801_2.png) [@ftg](https://boards.straightdope.com/u/ftg)\ **Post date:** [January 9, 2020, 7:24pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/256 "2020-01-09T19:24:00Z")
Everything was going swimmingly this afternoon until I opened this thread. Just a long delay, no 50x error. Not the first time this has happened with this thread. Hmmm. ---
**Author:** ![Dallas\_Jones](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/dallas_jones/32/3277_2.png) [@Dallas\_Jones](https://boards.straightdope.com/u/Dallas_Jones)\ **Post date:** [January 9, 2020, 7:31pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/257 "2020-01-09T19:31:40Z")
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. [Logging - Fiddler](http://fiddler2.com/r/?FiddlerLog) for details. 10:15:31:4105 Fiddler Running… 10:15:31:7073 Windows 8+ AppContainer isolation feature detected. 10:16:35:1318 HTTPSLint\> Warning: ClientHello record was 418 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) 10:16:35:1318 HTTPSLint\> Warning: ClientHello record was 418 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) 10:17:48:6661 [Fiddler] No HTTP request was received from (microsoftedgecp:8448) new client socket, port 50810. 10:20:24:5266 [Fiddler] No HTTP request was received from (microsoftedgecp:6836) new client socket, port 50871. 10:21:46:5110 [Fiddler] No HTTP request was received from (microsoftedgecp:6296) new client socket, port 50942. 10:22:36:4148 HTTPSLint\> Warning: ClientHello record was 421 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) 10:22:36:7741 HTTPSLint\> Warning: ClientHello record was 413 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) 10:22:36:8053 HTTPSLint\> Warning: ClientHello record was 413 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) 10:25:11:2068 HTTPSLint\> Warning: ClientHello record was 413 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) 10:29:20:9077 HTTPSLint\> Warning: ClientHello record was 413 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) 10:30:01:6542 HTTPSLint\> Warning: ClientHello record was 421 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) 10:50:26:1107 HTTPSLint\> Warning: ClientHello record was 421 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) 10:59:05:8985 HTTPSLint\> Warning: ClientHello record was 421 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) 10:59:06:6955 HTTPSLint\> Warning: ClientHello record was 413 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) 11:02:44:0441 HTTPSLint\> Warning: ClientHello record was 413 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) 11:02:44:1843 HTTPSLint\> Warning: ClientHello record was 413 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) 11:04:28:8781 HTTPSLint\> Warning: ClientHello record was 413 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) 11:09:07:3861 HTTPSLint\> Warning: ClientHello record was 384 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) 11:12:43:9739 HTTPSLint\> Warning: ClientHello record was 421 bytes long. Some servers have problems with ClientHello’s greater than 255 bytes. [Long Handshake Intolerance · ssllabs/research Wiki · GitHub](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance) ---
**Author:** ![Dallas\_Jones](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/dallas_jones/32/3277_2.png) [@Dallas\_Jones](https://boards.straightdope.com/u/Dallas_Jones)\ **Post date:** [January 9, 2020, 7:39pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/258 "2020-01-09T19:39:31Z")
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. > **[Long Handshake Intolerance](https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance)** > > Contribute to ssllabs/research development by creating an account on GitHub. ---
**Author:** ![Bijou\_Drains](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bijou_drains/32/2814_2.png) [@Bijou\_Drains](https://boards.straightdope.com/u/Bijou_Drains)\ **Post date:** [January 9, 2020, 7:45pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/259 "2020-01-09T19:45:33Z")
they should be able to find the problem if they want to. It’s not a money issue, there are many free tools to monitor website performance. ---
**Author:** ![atimnie](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/atimnie/32/11_2.png) [@atimnie](https://boards.straightdope.com/u/atimnie)\ **Post date:** [January 9, 2020, 8:26pm UTC](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514/260 "2020-01-09T20:26:37Z")
Are there any apps or tools that can speed things up on the user’s end? [Previous page](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514.md?page=12) [Next page](https://boards.straightdope.com/t/recent-server-timeout-errors-anyone-else-getting-them/844514.md?page=14)