Page 1 of 1

Problem Accessing Recent threads

Posted: 29 Feb 2016 22:20
by om4201
I've been getting 502 errors whenever I try to access a thread posted in the last couple days. Older threads are accessible, even when new comments have been posted, but the last few threads produce Error Number 502. The syntax of the address that the link points to is fine. Is there some cap on the t parameter in the address that is being exceeded, perhaps?

Re: Problem Accessing Recent threads

Posted: 29 Feb 2016 23:55
by thomas
If I have those problems sometimes it helps to restart the browser...

Re: Problem Accessing Recent threads

Posted: 01 Mar 2016 12:55
by om4201
Works ok with Chrome, but not with Firefox. Thanks.

Re: Problem Accessing Recent threads

Posted: 01 Mar 2016 13:45
by yeppie
Hey om,

there is already another thread for this question - I´ll move yours to the "know-how" subforum.

And thanks for the Chrome hint!

Re: Problem Accessing Recent threads

Posted: 02 Mar 2016 05:00
by reggind
I wish I knew what causes this. I had the same thing for a long time only Chrome gave me the error but Opera worked fine. Now months later Chrome is working once again. I think there may be something that gets set in your cookies as I tried clearing the browse cache and that did not help. I don't think it is browser specific, but if one starts acting up, try another and it will probably solve your problems.

Re: Problem Accessing Recent threads

Posted: 28 Mar 2016 11:05
by thedude4000
I've had this now and then but It seems restarting worked for me

Re: Problem Accessing Recent threads

Posted: 30 Mar 2016 08:17
by yeppie
Sorry guys, couldn´t fix this s far. But I learned that clicking on "mark these threads read" on the top of a forum´s listing always helped so far. I was able to open each thread that produced the 502 error before. And that might give me a hint...

Re: Problem Accessing Recent threads

Posted: 31 Mar 2016 12:13
by yeppie
I changed some settings and didn´t see 502 since then ... but opening threads seems to be significantly slower now. I will watch this and keep on searching for a good solution.