# AWS installation stuck in Read only mode

**URL:** <https://meta.discourse.org/t/aws-installation-stuck-in-read-only-mode/90226>\
**Category:** Product Support\
**Tags:** read-only\
**Created:** [June 19, 2018, 3:55pm UTC](https://meta.discourse.org/t/aws-installation-stuck-in-read-only-mode/90226 "2018-06-19T15:55:59Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![amoncadot](https://avatars.discourse-cdn.com/v4/letter/a/e9bcb4/32.png) [@amoncadot](https://meta.discourse.org/u/amoncadot)\
**Post date:** [June 19, 2018, 3:56pm UTC](https://meta.discourse.org/t/aws-installation-stuck-in-read-only-mode/90226/1 "2018-06-19T15:56:00Z")

</div>

Hello,

We’ve had our internal Discourse site for around 3 months now and suddenly it has gone into read only mode.

Based on other topics ([Stuck in 'Read Only' Mode](https://meta.discourse.org/t/stuck-in-read-only-mode/42820)) I have already tried the following:

- Login to docker instance: `./launcher enter app`
- Login to rails: `rails c`
- Disable read only: `Discourse.disable_readonly_mode(Discourse::USER_READONLY_MODE_KEY)`
- Quit rails: `quit`
- Exit container: `exit`

After doing this, our application seems to come out of read only mode, then goes back to read only mode.

I tried to rebuild a container but now I am getting the following error:

```
"Caused by:
PG::ReadOnlySqlTransaction: ERROR: cannot execute ALTER TABLE in a read-only transaction
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-1.0.0/lib/patches/db/pg.rb:92:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-1.0.0/lib/patches/db/pg.rb:92:in `async_exec'"

```

I guess because it’s stuck in read only mode for some reason?

Current setup is:

- 4 containers (2 cannot rebuild based on above, 2 are still running from 2 weeks ago)
- AWS
- Elasticache Redis
- RDS PostgreSQL

Regards,  
amoncadot

---

_[View the full topic](https://meta.discourse.org/t/aws-installation-stuck-in-read-only-mode/90226)._