Bad Gateway

[ulwen1]

Hi!

Why the 502 Bad Gateway for allmost every topic in the sound areas?
It has been so for a week now.

[Audio-Tool]

Hi there,

I saw there was one other post about my topic "BAD GATEWAY" but I wasn't even able to read anything else because when I clicked on the topic a new page opened stating "502 Bad Gateway nginx".
This has been going on for at least a week or two - and initially I thought the problem would have been solved.
So maybe the problem's on my side. I'm using Safari by the way. Any suggestions? Thanks!

[yeppie]

Sorry for the 502 Bad Gateway problem, this seems to happen from time to time. I haven´t figured out why and when this appears and why it seems to happen to only some members.

But we found a few workarounds that worked:
On the server side I deleted all cookies and temporarily changed the way, the "message-read" status gets stored. If this doesn´t help on your side, than please delete your cookies and close all browser windows before visiting the community again.

Did this help? Are there more members experiencing this error?

thx, yeppie

[Audio-Tool]

Hi,
Well, at first I wasn't even able to read your message yeppi, but I read somewhere else that deleting cookies helps - and - taxa - it worked!
Thanks in any case!

[yeppie]

That´s great, Audio-Tool!

[ulwen1]

First I could not read this thread after the first post.
But I found a way, due to a tips from a friend. I used Internet Explorer, and it's a little more itchy about missconfigured Proxys on the server-side when it comes to DNS/IP translation as I understood it.
I switched to Edge in Windows 10 and the site work much better now.

[Jeremy]

oddly I have been getting this error on my phone, but not my computer!

[lblack]

Had the same problem using Internet Explorer, but switching to Edge in Windows 10 seems to have solved the problem - for me at least. Deleting cookies in Explorer didn't make much difference - still got the Bad Gateway message