Updated to 2.9.1 from 2.6 or 2.7, getting 500 and nginx errors

I think what’s happening here is that some path or URL changed between these versions and that’s why I’m getting the keyboard elephant.

If I look at nginx logs, I get a lot of this:

2019/06/28 17:58:33 [error] 764#764: *291 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.9.29, server: twinja.club, request: “POST /inbox HTTP/1.0”, upstream: “http://127.0.0.1:3000/inbox”, host: “twinja.club”
2019/06/28 17:58:34 [error] 764#764: *293 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.9.29, server: twinja.club, request: “POST /inbox HTTP/1.0”, upstream: “http://127.0.0.1:3000/inbox”, host: “twinja.club”
2019/06/28 17:58:58 [error] 764#764: *295 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.9.29, server: twinja.club, request: “POST /inbox HTTP/1.0”, upstream: “http://127.0.0.1:3000/inbox”, host: “twinja.club”
2019/06/28 17:59:03 [error] 764#764: *297 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.9.29, server: twinja.club, request: “POST /inbox HTTP/1.0”, upstream: “http://127.0.0.1:3000/inbox”, host: “twinja.club”

Redis is running. nginx is running. All three systemd services are running. It almost looks like it’s trying to connect via http to itself instead of https after the update, but I could be reading this wrong.

I have an nginx proxy machine (that’s 192.168.9.29) forwarding connections to the host running Mastodon; that hasn’t changed and is clearly working the same way it did before or I wouldn’t be able to see the keyboard elephant.

Help?

nothing there related to path or URL changes, it’s just saying that it expects to find mastodon at 127.0.0.1 port 3000 and it’s not finding anything there. is Mastodon running at 127.0.0.1:3000 relative to the server running nginx? if not, you’ll need to modify your nginx config to point at the right location

It sure is:
tcp 0 0 0.0.0.0:3000 0.0.0.0:* LISTEN 1002 54234 4858/puma 3.12.1 (t

Just bumping this because my instance is down until someone can help me figure out how to resolve it.

Please post error logs: Troubleshooting - Mastodon documentation

Solved: Thanks to Eugen I realized I hadn’t run DB migrations; everything’s behaving normally now. As a reminder to anyone else who runs into these situations: upgrade instructions will not include instructions from previous x.x releases, which will often include RAILS_ENV=production bundle exec rake db:migrate as a requirement.

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