502 Bad Gateway nginx/1.8.0 on 05/25/2016 09:45 PM CDT
Links-arrows 1
Reply Reply
This is happening whenever I try to read a thread I have posted in and it happens when I post. I can refresh and see that my post went through but if I click on the link to the post the same error comes up.

I'm using Windows 7 with Chrome.

Chad, player of a few
Reply Reply
Re: 502 Bad Gateway nginx/1.8.0 on 05/25/2016 10:19 PM CDT
Links-arrows 2
Reply Reply


I've been experiencing the same. If I log out and check the thread (to see responses) I can then click the post button and log back in to post but it's a workaround at best.
Reply Reply
Re: 502 Bad Gateway nginx/1.8.0 on 05/26/2016 06:14 AM CDT
Links-arrows 3
Reply Reply
Same thing. I get a few pages fine after I first log in and then it gets horribly slow/502 errors.
Reply Reply
Re: 502 Bad Gateway nginx/1.8.0 on 05/26/2016 08:56 AM CDT
Links-arrows 4
Reply Reply
Specific threads seem to do it for me: in particular, threads I've replied to. Let's see if I can load this one after this.
Reply Reply
Re: 502 Bad Gateway nginx/1.8.0 on 05/26/2016 09:01 AM CDT
Links-arrows 5
Reply Reply
Logging on my F2P account to say I got a 502 error on the thread after I replied to it.

-PFLATS
Reply Reply
Re: 502 Bad Gateway nginx/1.8.0 on 05/26/2016 11:01 AM CDT
Links-arrows 6
Reply Reply
The issue seems to have resolved for me.

Chad, player of a few
Reply Reply
Re: 502 Bad Gateway nginx/1.8.0 on 05/27/2016 04:22 AM CDT
Links-arrows 7
Reply Reply
Seems to be resolved for me?

Assuming this post goes through...
Reply Reply