• 4 Posts
  • 8 Comments
Joined 1Y ago
cake
Cake day: Jun 12, 2023

help-circle
rss

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.


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`: ``` 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?
fedilink

Meaning I just wait a bit and retry later?


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

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.


[SOLVED] Need some guidance with upgrading
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!
fedilink

I feel like if anyone would appreciate this video as much as I do it'd be you guys. It's a little long but *totally* worth it.
fedilink

So looking at this again now, am I taking that whole block and adding it to the container’s nginx.conf? If so, does that mean I have to change what port it’s currently listening to (because there’s already a rule in the file for port 80)?

There’s a comment in that server rule that says “this is the port inside docker” and a comment immediately after that says “this is facing the public web”, which confuses me.


The one meant for the Docker container or the one on the host?


I think this is where my lack of experience with Docker is showing.

I spun up a DO droplet and installed nginx, Docker CE, and Docker Compose. Then I went through the instructions on the page you linked to and it set it up just fine but when I went to my droplets IP address it wouldn’t connect. I had to add a config file that pointed traffic coming into the droplet on port 80 to redirect to the Docker container instead. Am I overcomplicating it?


I seem to be having a lot of lag at the moment, and my post was created twice so I’m just going to delete the other one and start from here…

So I have this set up per the instructions. My instance is on a Digital Ocean instance, and I’m using nginx on the host to point to localhost:1235, but that’s about all that conf file is doing. Is there something else I need to do?


[SOLVED] How to configure Lemmy instance nginx proxy for websockets?
I'm playing around with my own instance of Lemmy but I keep getting a "websocket connection failed" error in my console. I'm having a really hard time understanding how to set up nginx for websockets - I'm more used to Apache and not familiar with WS at all. Is there documentation hiding somewhere that will help me set up my proxy forwarding properly? EDIT: Solved! Check out my solution here: https://lemmy.world/comment/141648. Thanks everyone!
fedilink