403 Forbidden after upgrade from 3.3.0 -> 3.4.0

I’m running in docker, and just tried upgrading from 3.3.0 to 3.4.0. I’m using a docker-compose.yml that’s basically the same as the one in the git repo. I followed the official upgrade instructions. The logs look normal:

web_1        | => Booting Puma
web_1        | => Rails 6.1.3.2 application starting in production
web_1        | => Run `bin/rails server --help` for more startup options
web_1        | [10] Puma starting in cluster mode...
web_1        | [10] * Puma version: 5.3.0 (ruby 2.7.2-p137) ("Sweetnighter")
web_1        | [10] *  Min threads: 5
web_1        | [10] *  Max threads: 5
web_1        | [10] *  Environment: production
web_1        | [10] *   Master PID: 10
web_1        | [10] *      Workers: 2
web_1        | [10] *     Restarts: (✔) hot (✖) phased
web_1        | [10] * Preloading application
web_1        | [10] * Listening on http://0.0.0.0:3000
web_1        | [10] Use Ctrl-C to stop
web_1        | [10] - Worker 0 (PID: 13) booted in 0.01s, phase: 0
web_1        | [10] - Worker 1 (PID: 19) booted in 0.0s, phase: 0

The web container shows as unhealthy:

$ docker-compose ps
        Name                      Command                   State              Ports
-------------------------------------------------------------------------------------------
mastodon_db_1          docker-entrypoint.sh postgres    Up (healthy)
mastodon_redis_1       docker-entrypoint.sh redis ...   Up (healthy)
mastodon_sidekiq_1     /usr/bin/tini -- bundle ex ...   Up               3000/tcp, 4000/tcp
mastodon_streaming_1   /usr/bin/tini -- node ./st ...   Up (healthy)     3000/tcp, 4000/tcp
mastodon_web_1         /usr/bin/tini -- bash -c r ...   Up (unhealthy)   3000/tcp, 4000/tcp

If I try to load any page I get a 403 Forbidden error:

~$ wget -q -S -O - localhost:3000
  HTTP/1.1 403 Forbidden
  Content-Type: text/html; charset=UTF-8
  Content-Length: 4950

I’m ashamed to admit I didn’t backup my database before running the migrations, so I probably can’t downgrade. Any ideas on how to fix it?

This might be the cause. If I run the edge docker image, it works.

This is indeed the cause, this will be fixed in 3.4.1.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.