I’m using Digital Ocean droplet to host Discourse(last version) with Nginx+Let’s Encrypt SSL in front. Yesterday when I was working to enable LinkedIn OAuth login. I’d enabled FORCE_HTTPS to try if it will make OAuth login work but I lost the ability to login from to all accounts. After I’d tried m…

Try this: /var/discourse/launcher enter app rails c SiteSetting.force_https = false

Can you try disabling force_https for now? My guess is that your problem is similar to https://meta.discourse.org/t/users-unable-to-login-after-container-rebuild/51709

Many thanks @fefrei . You saved my day!. I announce you a man of the DAY :tada: It’s Worked :slight_smile:

Just a brief explanation on why that worked versus the prior attempt. The prior attempt you tried using bundle exec rails c which was designed for development environments, not the official docker installations. With the official docker installations, you don’t need to invoke it through bundle exec …

Its great to understand the reason @cpradio . It was a question in my head that you answered. Thank you very much. :sparkles: The problem in here, sometimes people do not mention/aware what environment they are giving advice to. Maybe a lot of people like me, creating a lot of unnecessary problems t…

[afbeelding] fefrei: /var/discourse/launcher enter app rails c SiteSetting.force_https = false As we used to do ./launcher rebuild app at every change so I did it too. But after a thought, I wasn’t sure if that was necessary this time? Not urgent but it would be very much helpful. Any othe…

A rebuild is necessary when you modified app.yml (with a few exceptions where a restart is enough) or want to update the base image. With the SiteSetting object on the rails console, you can update everything listed in the admin UI under site settings, plus a few secret bonus settings …

Just to add to @fefrei ’s explanation, rebuild is unnecessary for this round because you weren’t changing the app.yml, you were invoking Discourse’s internal API which updated the database and thus the next time you attempted to access your Discourse instance, it was able to read force_https as false…

That’s great info Felix. Where I could find the SiteSetting object elements lists (and its options if possible) without digging into the source code? :blush:

There shouldn’t really be a reason to do this – almost all site settings can be configured from the web UI (and if you need to configure them from the console, just replaces spaces in their name with _), and the others aren’t really meant to be tweaked :wink:

Discourse lost the ability to login for all accounts

Ondersteuning

ewanly (EW 👌) 20 oktober 2016 om 11:06 3

Thank you @tgxworld. Because I’m not able to login at all there was no way to do it from the site. So I’d tried to follow the instruction on how to do it from console (as I’d tried yesterday when I’d faced the same problem) but I’m getting a fatal error again as seen here:

Topic		Antwoorden	Weergaven
Lost access to Discourse login (no credentials), lost original domain- now trying to migrate to new DO droplet Support	9	190	21 januari 2025
Forced https deactivate Support	11	1740	22 augustus 2019
Twitter, Github and normal username and password logins not working after upgrade Self-hosting unsupported-install	35	7431	22 oktober 2016
No login is possible after recovery a Discourse Backup on a new server Support	13	1054	24 oktober 2021
Can't login after restoring Self-hosting	14	3185	14 juli 2019

Discourse lost the ability to login for all accounts

Gerelateerde topics