this post was submitted on 12 Jun 2023
10 points (100.0% liked)

Selfhosted

39918 readers
463 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

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

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
10
[SOLVED] How to configure Lemmy instance nginx proxy for websockets? (lemmy.world)
submitted 1 year ago* (last edited 1 year ago) by penguin_ex_machina@lemmy.world to c/selfhosted@lemmy.world
23 comments fedilink hide all child comments
 

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!

you are viewing a single comment's thread
view the rest of the comments
[–] aucubin@lemmy.aucubin.de 1 points 1 year ago (1 children)

No, you are right. If you are using the nginx container from the docker installation guide then you will also need to add port 80 atleast in order to see anything, as nginx will otherwise not listen on the port 80 of the droplet.

How does your nginx.conf look now?

[–] penguin_ex_machina@lemmy.world 0 points 1 year ago (1 children)

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

[–] aucubin@lemmy.aucubin.de 2 points 1 year ago (2 children)

Ah, so you added another nginx on the host by installing it from the package store of the distro and have that proxy port 80 to the docker nginx?

If you do that then you also need to add the websocket settings I had in the first comment to the host nginx.

What I meant what that the nginx in the docker-compose from lemmy also listens to port 80 and you just need to add

server {
    listen 80;
    server_name my_domain.tld;

    location / {
        proxy_pass http://localhost:LEMMY_PORT;
        proxy_set_header Host $host;
        include proxy_params;
    }
}

to the nginx.conf of the container.

Then you should have it accessable from port 80 without the host nginx (of course you need to stop the host nginx then).

[–] penguin_ex_machina@lemmy.world 2 points 1 year ago

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.

[–] penguin_ex_machina@lemmy.world 1 points 1 year ago

Ahaaaa ok. I'll try that a little later this afternoon. Thanks for explaining it to me.