I upgraded my instance (at scicomm.xyz) to 3.3.0 about a week ago, following the instructions on the release page. I didn’t encounter any problems or errors during the upgrade. However, today, a user on my instance reported that the API isn’t working correctly.
The front-end is working fine.
Restarting nginx and/or the Mastodon processes hasn’t fixed the issue.
journalctl -u mastodon-web -f I can see:
path=/api/v1 format=html controller=ApplicationController action=raise_not_found status=404 duration=12.06 view=2.30 db=1.63
And also in the nginx access.log:
xxx.xxx.xxx.xxx - - [08/Jan/2021:11:06:42 +0000] "GET /api/v1 HTTP/2.0" 404 647 "-" "Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Firefox/78.0" xxx.xxx.xxx.xxx - - [08/Jan/2021:11:06:42 +0000] "GET /oops.png HTTP/2.0" 304 0 "https://scicomm.xyz/api/v1" "Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Firefox/78.0"
The last major change to my system was the upgrade to v3.3.0.
I am not too sure where to go next in troubleshooting this issue so any advice would be appreciated!