Sorting out post-migration mastodon server issues. :/
I have zero knowledge on how mastodon works, so making observations loaded with assumptions here.
This server is responding to what appears to be federated timeline updates with 401 errors. These are POST requests to /inbox
The application server sees these requests, routes them to a controller, then responds with 401.
Only change from old server to new is moving to traefik from nginx-proxy...
Solved for now...
Guess it was a bad idea to put an extra nginx proxy container in front of the app to tweak nginx config. A bit irritated that I don't understand why that broke only some http requests and not others. They all seemed to make their way through to mastodon.
I have a timeline again at least
Mastodon server for furries. 18+ only. Open to lions, their friends, nerds, and others.