overview for penguin_ex

Google promised a better search experience — now it’s telling us to put glue on our pizza in c/technology@lemmy.world

[–] penguin_ex_machina@lemmy.world 6 points 6 months ago (2 children)

I’ve actually had pretty good success with ChatGPT when I go in expecting it to hallucinate a significant chunk of what it spits back at me. I like to think of it as a way to help process my own ideas. If I ask questions with at least a base understanding of the topic, I can then take whatever garbage it gives me and go off and find real solutions. The key is to not trust it whole cloth to give you the right answer, but to give you some nuggets that set you on the right path.

I think I’ve basically turned ChatGPT into my rubber duck.

Suddenly getting a server error on my instance in c/selfhosted@lemmy.world

[–] penguin_ex_machina@lemmy.world 1 points 10 months ago

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.

15

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

submitted 10 months ago by penguin_ex_machina@lemmy.world to c/selfhosted@lemmy.world

5 comments fedilink

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?

[SOLVED] Need some guidance with upgrading in c/selfhosted@lemmy.world

[–] penguin_ex_machina@lemmy.world 1 points 11 months ago (1 children)

Meaning I just wait a bit and retry later?

[SOLVED] Need some guidance with upgrading in c/selfhosted@lemmy.world

[–] penguin_ex_machina@lemmy.world 1 points 11 months ago (5 children)

Upgraded to 0.18.5, which now gives me this error:

lemmy-lemmy-ui-1  | API error: FetchError: request to http://lemmy:8536/api/v3/site?auth=AUTH_KEY failed, reason: connect ECONNREFUSED IP_ADDRESS:8536

[SOLVED] Need some guidance with upgrading in c/selfhosted@lemmy.world

[–] penguin_ex_machina@lemmy.world 1 points 11 months ago (7 children)

I created a gist with my compose file: https://gist.github.com/osiriswrecks/26a875576d3bbcf11923d7715ac15e6e. It should be stripped of all private info. I tried changing the version from 0.17.3 to 0.18.0 and the server returns a gateway error after restarting.

10

[SOLVED] Need some guidance with upgrading (lemmy.world)

submitted 11 months ago* (last edited 11 months ago) by penguin_ex_machina@lemmy.world to c/selfhosted@lemmy.world

9 comments fedilink

Hi! I'm hoping for some guidance upgrading my instance. I'm still running on v0.17.3 because I ran into some issues upgrading to 0.18 and didn't have time to really figure it out. Now that the current release is v0.19, I have people on my instance asking to upgrade and I don't blame them. Can I simply point Docker compose at the latest release, or do I have to do incremental upgrades? What do I need to look out for with v0.18? Documentation seems to be pretty slim for whatever breaking changes happened during that release cycle and how to deal with them. Any help is appreciated!

EDIT: Thank you for all the help! I also had to update pictrs and fix some small config issues and then everything worked as expected. I'm now on 0.19.1!