Cant disable read-only mode

Product Support

AI-generated summary

The user dje4321 is unable to disable read-only mode on their Discourse forum, even after attempting commands via the Docker image and Rails console. tgxworld explains that read-only mode can be triggered by different keys in PostgreSQL, referencing the relevant code. dje4321 resolves the issue using Discourse.disable_readonly_mode(Discourse::USER_READONLY_MODE_KEY) in the Rails console. Thomas_Rother confirms the same problem and notes that while discourse disable_readonly works, the read-only banner persists. Thomas_Rother suggests improving the UX by allowing admin access via a special login URL with a token, even in read-only mode.

1

I enabled read-only mode on my forums and im not able to disable it.

I cant disable read-only mode via the /admin/backups because i cant login.

entering the docker image and disabling it via rails does not work either.

rails c
Discourse.disable_readonly_mode

entering the docker image and running

discourse disable_readonly

does not work either.

Anything im missing?

sorry if the bug category is not the correct category. I think this might be a bug

2

It depends on how you trigger readonly mode.

There is a list of keys that you can pass to Postgres depending on how you trigger it

3

Thanks

This command in rails did the trick

Discourse.disable_readonly_mode(Discourse::USER_READONLY_MODE_KEY)

5

I have the same issue in the latest discourse version.

  1. from inside the web_only container
root@forum:/var/www/discourse# discourse disable_readonly
The site is now fully operable.
root@forum:/var/www/discourse#

  1. ./launcher enter web_only

  2. after that, I still have the “read only” banner on the main page.

So, the issue is not solved yet …

6

… ok, I could solve this now with the rails c commandline info.
But anyway, this should be improved: for example there could be a special login url with a token to allow admin operations from the UX even in readyonly mode.