### Author:  [@Milenski](https://meta.discourse.org/u/Milenski)
#### Post date: [January 9, 2026, 5:26am UTC](https://meta.discourse.org/t/migration-error-in-rename-discourse-rewind-disabled-to-enabled/393049/9 "2026-01-09T05:26:10Z")
Honestly, I don’t know what the problem is with your Discourse installation. I just rebuilt my second forum through the server terminal and everything is fine again. Now I’m going to rebuild my third forum, hopefully it’s fine too.
If you have made any changes to the Discourse files, I know that it can cause problems in the future. Or if you have manually added/installed any plugins.
Wait, be patient and those who know more than me will help. This is one of the reasons I like and switched to this system, the community, this is what makes it even greater.
> Edit:
> However, on my third forum, the rebuild didn’t work.
> FAILED
>
> Pups::ExecError: cd /var/www/discourse && su discourse -c ‘bundle exec rake db:migrate’ failed with return #\
> Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.3.0/lib/pups/exec\_command.rb:131:in `spawn’
> exec failed with the params {“cd”=\>“$home”, “tag”=\>“migrate”, “hook”=\>“db\_migrate”, “cmd”=\>[“su discourse -c ‘bundle exec rake db:migrate’”]}
> bootstrap failed with exit code 1
> \*\* FAILED TO BOOTSTRAP \*\* please scroll up and look for earlier error messages, there may be more than one.
> ./discourse-doctor may help diagnose the problem.
> 63e30cde8c7295d25def35eef74dea30714627609c3d38b49a8f80865e5759cf
And now redirect to my second forum… what… what… 🤣
---
### Author:  [@sniper756](https://meta.discourse.org/u/sniper756)
#### Post date: [January 9, 2026, 5:33am UTC](https://meta.discourse.org/t/migration-error-in-rename-discourse-rewind-disabled-to-enabled/393049/10 "2026-01-09T05:33:50Z")
Thank you for your reply. I have not made any modifications or installed any additional plugins.
---
### Author:  [@Milenski](https://meta.discourse.org/u/Milenski)
#### Post date: [January 9, 2026, 5:42am UTC](https://meta.discourse.org/t/migration-error-in-rename-discourse-rewind-disabled-to-enabled/393049/11 "2026-01-09T05:42:35Z")
I also don’t have any manually installed plugins on my third forum, but after the failed rebuild, and the redirect to my second forum… I also checked the configuration file (nano containers/app.yml) and everything is fine there… what’s going on? 😃
---
### Author:  [@sniper756](https://meta.discourse.org/u/sniper756)
#### Post date: [January 9, 2026, 7:31am UTC](https://meta.discourse.org/t/migration-error-in-rename-discourse-rewind-disabled-to-enabled/393049/12 "2026-01-09T07:31:31Z")
rebuild success
---
### Author:  [@Milenski](https://meta.discourse.org/u/Milenski)
#### Post date: [January 9, 2026, 7:53am UTC](https://meta.discourse.org/t/migration-error-in-rename-discourse-rewind-disabled-to-enabled/393049/13 "2026-01-09T07:53:16Z")
Not for me ☹ I have a server restore point luckily from 01-05-2026. For the second time I can neither update nor rebuild Discourse. Now I’m restoring it again, and one thing is clear:
1. Backup all topics/articles in a text file.
2. Hopefully this will be resolved either with a new installation of Discourse, or with another system (which I don’t want to do).
There’s something somewhere I’m missing and I don’t know what it is and it’s driving me crazy. But apparently the retrograde uranium is having its say. For now I’ll leave things like this, and go clean up some bugs in HELLDIVERS 2 because I’m sad 🤣
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [January 9, 2026, 8:29am UTC](https://meta.discourse.org/t/migration-error-in-rename-discourse-rewind-disabled-to-enabled/393049/14 "2026-01-09T08:29:50Z")
I understand your frustrations and I apologize. I tested my “fixes” locally on both my local dev database, and then on a brand new database and they both worked just fine. Then I tested on a hosted instance that I run for a community I manage and it worked fine there as well. It also passed all our public CIs (on GitHub) as well as our internal CIs and smoke tests.
As it happens, none of those databases had data that was affected by that migration 😑…
I’m sorry you all had a bad experience and I’ll be more careful next time.
---
### Author:  [@Kartoon](https://meta.discourse.org/u/Kartoon)
#### Post date: [January 9, 2026, 10:04am UTC](https://meta.discourse.org/t/migration-error-in-rename-discourse-rewind-disabled-to-enabled/393049/15 "2026-01-09T10:04:29Z")
So…safe to try now or will it just make it worse? I have the same issue and haven’t attempted a rebuild yet after seeing this
---
### Author:  [@sniper756](https://meta.discourse.org/u/sniper756)
#### Post date: [January 9, 2026, 10:06am UTC](https://meta.discourse.org/t/migration-error-in-rename-discourse-rewind-disabled-to-enabled/393049/16 "2026-01-09T10:06:35Z")
After I rebuilt, I found that the data was not the latest, so I restored it using the backup from the day before yesterday from the management backend. Currently, no issues have been found yet.
---
### Author:  [@Kartoon](https://meta.discourse.org/u/Kartoon)
#### Post date: [January 9, 2026, 10:32am UTC](https://meta.discourse.org/t/migration-error-in-rename-discourse-rewind-disabled-to-enabled/393049/17 "2026-01-09T10:32:35Z")
Looks like it worked fine and it’s loading normally for anyone else wondering
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [January 9, 2026, 5:15pm UTC](https://meta.discourse.org/t/migration-error-in-rename-discourse-rewind-disabled-to-enabled/393049/19 "2026-01-09T17:15:37Z")
@here for those who are having issues, I _think_ @david and I may have found the root cause but [it’s complicated](https://github.com/discourse/discourse/pull/37037) to reproduce locally.
Could any of you run the following SQL queries and report the results here?
**Query #1**
```sql
SELECT table_schema, column_name, column_default
FROM information_schema.columns
WHERE table_name = 'user_options'
AND column_name = 'discourse_rewind_disabled'
ORDER BY table_schema;
```
**Query #2**
```sql
SELECT n.nspname, n.oid
FROM pg_namespace n
JOIN pg_class c ON c.relnamespace = n.oid
WHERE c.relname = 'user_options'
ORDER BY n.oid;
```
**Query #3**
```sql
SELECT table_schema, column_default IS NOT NULL as has_default
FROM information_schema.columns
WHERE table_name = 'user_options'
AND column_name = 'discourse_rewind_disabled';
```
**Query #4**
```sql
SELECT nspname, oid FROM pg_namespace
WHERE nspname NOT IN ('pg_catalog', 'information_schema', 'pg_toast', 'public')
AND nspname NOT LIKE 'pg_temp%'
AND nspname NOT LIKE 'pg_toast_temp%'
ORDER BY oid;
```
Thanks 🙏
---
### Author:  [@sniper756](https://meta.discourse.org/u/sniper756)
#### Post date: [January 10, 2026, 4:27am UTC](https://meta.discourse.org/t/migration-error-in-rename-discourse-rewind-disabled-to-enabled/393049/20 "2026-01-10T04:27:52Z")
Okay, no problem, I’m out right now, I’ll check when I get back.
---
### Author:  [@sniper756](https://meta.discourse.org/u/sniper756)
#### Post date: [January 10, 2026, 6:51am UTC](https://meta.discourse.org/t/migration-error-in-rename-discourse-rewind-disabled-to-enabled/393049/21 "2026-01-10T06:51:12Z")
Do these commands need to be run inside the container? What is the default password for PostgreSQL when deploying Discourse using Docker?
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [January 10, 2026, 10:03am UTC](https://meta.discourse.org/t/migration-error-in-rename-discourse-rewind-disabled-to-enabled/393049/22 "2026-01-10T10:03:35Z")
When inside the container, as the discourse user, at the root of the discourse directory, you can run `bin/rails db` to connect to the right db.
[Next page](https://meta.discourse.org/t/migration-error-in-rename-discourse-rewind-disabled-to-enabled/393049.md?page=2)