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!

  • penguin_ex_machina@lemmy.worldOPEnglish
    1·
    1 year ago

    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?

    • aucubin@lemmy.aucubin.deEnglish
      1·
      1 year ago

      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?

        • aucubin@lemmy.aucubin.deEnglish
          2·
          1 year ago

          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.worldOPEnglish
            1·
            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.