Users forum is unreachable (error 500)

[SethTisue]

problem may be intermittent, but I experienced it firsthand, and a user on Discord reported it, too

I wonder if it's related to the trouble Scaladex has been having with being hammered by excessive crawler traffic?

@fsalvi can you take a look...?

[JD557]

This has been going on for a few days.

I can't recall for sure when I first hit this issue, but I believe it was around the 26th of August.

[sjrd]

Clearing all caches for that websites restores it.

It would be better if that was not required of course, but it could be a lead.

[marcgrue]

I experience it too

[fsalvi]

I also noticed the problem. It appeared after I upgraded discourse to the latest version last week.
Try in a private window, it should work perfectly fine. It seems the only solution is to purge cache on the browser.

[tgodzik]

@fsalvi would downgrading discourse be possible as well?

[fsalvi]

It's not possible do downgrade (and also for security reasons), only to update.
I already updated discourse twice since the last upgrade. I cannot reproduce the problem as I already cleaned the cache for the website.
It looks quite ok now, there's activity this morning.
Note that it's easy to clean cache only for one website on google chrome or firefox (just using the button left aside the URL).

[tgodzik]

Och, actually the issue comes back after I reopen the tab, it was also reported on the contributors forum. Did you update the other forum as well?

[MateuszKubuszok]

In my case, clearing all cache for users.scala-lang.org works only until I reopen the tab, then it breaks and I have to clear it again (I already did it 4-5 times, each logging me out of contributors.scala-lang.org as well for some reason, so for now I decided it's not worth my time).

[fsalvi]

Yes, I saw the problem again this time after trying again to update discourse. I don't have much log except this "500 Internal Server Error" in rails. I'll report this problem to discourse.
I didn't update contributors.scala-lang.org, so this one is still running the previous version.

[tgodzik]

Let's hold off the contributors update then until we have some more info.

[fsalvi]

I modified the reverse proxy setting that could be the cause of the bug. Let's wait a couple of days to see if the problem is definitively fixed...