Suddenly getting a server error on my instance

I don’t know when it started, I usually check my instance through the Voyager app and it never showed a problem, but I’m suddenly getting “server error” and 502 bad gateway errors on my instance on desktop. I haven’t made any major changes (read, any at all) since I last confirmed it worked on desktop.

Checking the logs I don’t see any obvious proxy issues but I am getting weird connection issues in lemmy-ui:


<span style="color:#323232;">TypeError: fetch failed
</span><span style="color:#323232;">lemmy-lemmy-ui-1  |     at Object.fetch (node:internal/deps/undici/undici:11730:11)
</span><span style="color:#323232;">lemmy-lemmy-ui-1  |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
</span><span style="color:#323232;">lemmy-lemmy-ui-1  |   cause: ConnectTimeoutError: Connect Timeout Error
</span><span style="color:#323232;">lemmy-lemmy-ui-1  |       at onConnectTimeout (node:internal/deps/undici/undici:6869:28)
</span><span style="color:#323232;">lemmy-lemmy-ui-1  |       at node:internal/deps/undici/undici:6825:50
</span><span style="color:#323232;">lemmy-lemmy-ui-1  |       at Immediate._onImmediate (node:internal/deps/undici/undici:6857:13)
</span><span style="color:#323232;">lemmy-lemmy-ui-1  |       at process.processImmediate (node:internal/timers:478:21) {
</span><span style="color:#323232;">lemmy-lemmy-ui-1  |     code: 'UND_ERR_CONNECT_TIMEOUT'
</span><span style="color:#323232;">lemmy-lemmy-ui-1  |   }
</span><span style="color:#323232;">lemmy-lemmy-ui-1  | }
</span>

Where on earth can I even begin to address this?

penguin_ex_machina,

So…it’s working now? I haven’t touched anything yet, but I just checked my instance again and it works perfectly fine on desktop now. It always worked through Voyager, so I was able to let people know there was an issue. If it comes back I’ll try some of these suggestions to find a more permanent fix.

haui_lemmy,

I would start at the github repo and check if that issue has been documented.

If yes, follow the instructions. If not, check your dns since 502 often came from dns in my case.

If both doesnt reveal anything, you could open an issue in the repo and post your (sanitized) logs and wait for answers.

The error suggests a problem with the lemmy-lemmy-ui-1 container. Maybe it needs an update or has pulled a wrong update. When did you update last? Did you try restarting the stack?

Good luck.

Dave,
@Dave@lemmy.nz avatar

If the error is with the UI, then trying a mobile app is a good place to start (since they should connect to the API directly).

  • All
  • Subscribed
  • Moderated
  • Favorites
  • selfhosted@lemmy.world
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #