Question

Mastodon - 500 Internal Server Error

Posted November 6, 2021 62 views
DigitalOcean 1-Click Apps Marketplace

Hello,
Mastodon basic is fully operational then simply stops (error messages below) then it works again. Can you please review and suggest possible solutions or causes. Thanks, all the best D.

XHRGEThttps://dorijan.io/api/v1/timelines/home
[HTTP/2 500 Internal Server Error 5839ms]

GETwss://dorijan.io/api/v1/streaming/?stream=user
[HTTP/1.1 502 Bad Gateway 2976ms]

XHRGEThttps://dorijan.io/api/v1/timelines/home
[HTTP/2 500 Internal Server Error 6553ms]

XHRGEThttps://dorijan.io/api/v1/notifications?excludetypes[]=followrequest
[HTTP/2 500 Internal Server Error 6524ms]

XHRGEThttps://dorijan.io/api/v1/suggestions
[HTTP/2 500 Internal Server Error 7823ms]

XHRGEThttps://dorijan.io/api/v1/trends
[HTTP/2 500 Internal Server Error 6400ms]

XHRGEThttps://dorijan.io/api/v1/follow_requests
[HTTP/2 500 Internal Server Error 7717ms]

XHRGEThttps://dorijan.io/api/v1/announcements
[HTTP/2 500 Internal Server Error 6369ms]

XHRGEThttps://dorijan.io/api/v1/filters
[HTTP/2 500 Internal Server Error 5970ms]

XHRPOSThttps://dorijan.io/api/web/push_subscriptions
[HTTP/2 500 Internal Server Error 6052ms]

Firefox can’t establish a connection to the server at wss://dorijan.io/api/v1/streaming/?stream=user. emojipickerdropdown.js:85:59
GETwss://dorijan.io/api/v1/streaming/?stream=user
[HTTP/1.1 502 Bad Gateway 2164ms]

Firefox can’t establish a connection to the server at wss://dorijan.io/api/v1/streaming/?stream=user. emojipickerdropdown.js:85:59
GETwss://dorijan.io/api/v1/streaming/?stream=user
[HTTP/1.1 502 Bad Gateway 276ms]

Firefox can’t establish a connection to the server at wss://dorijan.io/api/v1/streaming/?stream=user. emojipickerdropdown.js:85:59
GETwss://dorijan.io/api/v1/streaming/?stream=user
[HTTP/1.1 502 Bad Gateway 265ms]

Firefox can’t establish a connection to the server at wss://dorijan.io/api/v1/streaming/?stream=user. emojipickerdropdown.js:85:59
GETwss://dorijan.io/api/v1/streaming/?stream=user
[HTTP/1.1 502 Bad Gateway 282ms]

Firefox can’t establish a connection to the server at wss://dorijan.io/api/v1/streaming/?stream=user. emojipickerdropdown.js:85:59
XHRGEThttps://dorijan.io/api/v1/timelines/home
[HTTP/2 500 Internal Server Error 601ms]

XHRGEThttps://dorijan.io/api/v1/notifications?excludetypes[]=followrequest
[HTTP/2 500 Internal Server Error 694ms]

GETwss://dorijan.io/api/v1/streaming/?stream=user
[HTTP/1.1 502 Bad Gateway 292ms]

XHRGEThttps://dorijan.io/api/v1/announcements
[HTTP/2 500 Internal Server Error 687ms]

Firefox can’t establish a connection to the server at wss://dorijan.io/api/v1/streaming/?stream=user. emojipickerdropdown.js:85:59
GETwss://dorijan.io/api/v1/streaming/?stream=user
[HTTP/1.1 502 Bad Gateway 349ms]

Firefox can’t establish a connection to the server at wss://dorijan.io/api/v1/streaming/?stream=user. emojipickerdropdown.js:85:59
GETwss://dorijan.io/api/v1/streaming/?stream=user
[HTTP/1.1 502 Bad Gateway 249ms]

Firefox can’t establish a connection to the server at wss://dorijan.io/api/v1/streaming/?stream=user. emojipickerdropdown.js:85:59
GETwss://dorijan.io/api/v1/streaming/?stream=user
[HTTP/1.1 502 Bad Gateway 452ms]

Firefox can’t establish a connection to the server at wss://dorijan.io/api/v1/streaming/?stream=user. emojipickerdropdown.js:85:59
XHRGEThttps://dorijan.io/api/v1/timelines/home
[HTTP/2 500 Internal Server Error 1293ms]

XHRGEThttps://dorijan.io/api/v1/notifications?excludetypes[]=followrequest
[HTTP/2 500 Internal Server Error 1210ms]

XHRGEThttps://dorijan.io/api/v1/announcements
[HTTP/2 500 Internal Server Error 2908ms]

GETwss://dorijan.io/api/v1/streaming/?stream=user
[HTTP/1.1 502 Bad Gateway 764ms]

Firefox can’t establish a connection to the server at wss://dorijan.io/api/v1/streaming/?stream=user. emojipickerdropdown.js:85:59
XHRGEThttps://dorijan.io/api/v1/accounts/relationships?id[]=1
[HTTP/2 500 Internal Server Error 3609ms]

XHRGEThttps://dorijan.io/api/v1/accounts/1/identity_proofs
[HTTP/2 500 Internal Server Error 3861ms]

XHRGEThttps://dorijan.io/api/v1/accounts/1/statuses?pinned=true
[HTTP/2 500 Internal Server Error 3181ms]

XHRGEThttps://dorijan.io/api/v1/accounts/1/statuses?exclude_replies=true
[HTTP/2 500 Internal Server Error 3967ms]

Uncaught (in promise) TypeError: e is undefined
f alerts.js:38
Jt errors.js:11
Jt loadingbar.js:23
Redux 2
s identity
proofs.js:12
promise callbacks/< identity_proofs.js:12
a Redux
componentWillMount index.js:54
React 13
setState index.js:3
n bundle.js:79
promise callback
n/< bundle.js:77
componentWillMount bundle.js:37
React 29
setState index.js:3
n bundle.js:79
promise callbackn/< bundle.js:77
componentWillMount bundle.js:37
React 12
default main.js:24
r ready.js:5
default main.js:20
505 application.js:7
promise callback
505 application.js:6
Webpack 4
alerts.js:38:6
XHRGEThttps://dorijan.io/api/v1/timelines/home
[HTTP/2 500 Internal Server Error 1599ms]

XHRGEThttps://dorijan.io/api/v1/notifications?excludetypes[]=followrequest
[HTTP/2 500 Internal Server Error 2153ms]

XHRGEThttps://dorijan.io/api/v1/announcements
[HTTP/2 500 Internal Server Error 6670ms]

XHRGEThttps://dorijan.io/api/v1/timelines/home
[HTTP/2 500 Internal Server Error 6508ms]

XHRGEThttps://dorijan.io/api/v1/notifications?excludetypes[]=followrequest
[HTTP/2 500 Internal Server Error 8932ms]

XHRGEThttps://dorijan.io/api/v1/announcements
[HTTP/2 500 Internal Server Error 27375ms]

GETwss://dorijan.io/api/v1/streaming/?stream=user
[HTTP/1.1 502 Bad Gateway 6303ms]

Firefox can’t establish a connection to the server at wss://dorijan.io/api/v1/streaming/?stream=user. emojipickerdropdown.js:85:59
XHRGEThttps://dorijan.io/api/v1/timelines/home
[HTTP/2 502 Bad Gateway 27200ms]

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer

Hey there!

It seems that your application is failing to connect to the streaming service on occasion. I’d recommend you take a look at your webserver logs to get a better idea of what service it is failing to connect to. If you are running this using the 1-click app with nginx those should be in /var/log/nginx. Those logs should provide a better idea as to what is failing. It seems it could be caused by resource contention so I’d recommend reviewing your resource usage on your droplet and make sure you have sufficient RAM available. The top and free -mcommands should help check those resources.

Hope it helps!
Nate

  • And you were right. It was insufficient RAM issue. Used htop to spot the problem. Upgraded one step, works fine for current needs.
    Thanks D.