Selfhosted

39158 readers

560 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Suddenly getting a server error on my instance (lemmy.world)

submitted 8 months ago by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

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:

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

Where on earth can I even begin to address this?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 8 months ago

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).