Discourse interface don't start after upgrading to v3.4.0.beta3-dev

Product Support

AI-generated summary

Hilario upgraded their Discourse instance to v3.4.0.beta3-dev, which required upgrading Docker and Ubuntu. After the upgrade, they encountered a login issue: after entering credentials, the page hangs with a loading spinner, though public content remains accessible. They tested multiple browsers without success. bob_the_tomato suggested waiting or reloading, while Moin recommended checking the browser console and trying safe mode. RGJ identified a likely culprit: the “Moderator attention” plugin, which is known to prevent moderators from logging in by causing infinite loading. Hilario confirmed that entering safe mode helped diagnose the issue, and uninstalling the problematic plugin resolved the login hang. They thanked the community for their help and expressed relief that their data was intact.

1

For being able to upgrad to 3.4.0 I had to upgrade docker to 20.0.7 and for doing this, I had to upgrade Ubuntu to 20.04
Now everything is upgraded, no aparent error message on the console.
When I start my discourse from an anonymous windows y get the login windows

image
image789Ă—645 41.9 KB

When I type my autentication info it seams I am going to log but the screen remain as next image.
An image of a blank computer screen with a loading circle at the center. (Captioned by AI)
An image of a blank computer screen with a loading circle at the center. (Captioned by AI)789Ă—645 12.7 KB

I tried with different explorers (firefox, brave) but problem is the same. As soon as I enter the login info my sesion is hang.
If I don’t log, I can navigate and see public information.

Thank you for any suggestion
I am very worried to return to my previous system after all the work of upgrading.
Thanks

2

Try reloading it again, or wait it out, the forum might be in extreme load at the time.

3

Are there any errors in the browser console after logging in?
Did you try safe mode?

4

You seem to have a few relatively unknown plugins. At least one of them is known to cause issues which are very similar to yours:

So you might try uninstalling that one.

What does your browser console say?

5

I forgot this option. Thanks to remember it allow me to continue debugging the problem and to be more relax (at least everything was there :rofl: )

You are correct. Uninstalling these plugin solve the point. Thanks a lot for everybody help.