I have Mastodon running on a VPS running Debian 11. Now I would like to add a Lemmy instance on the same server. I tried using the from scratch method from Lemmy documentation, but ran into errors that likely stemmed from minor version incompatibilities of the dependencies. I tried using the Lemmy easy deploy script but it wants to bind all traffic on port 443 for Lemmy which would break my Mastodon install. Has anyone managed to get Lemmy and Mastodon running on the same box, and if so, can you share any details of your setup?

  • @TrinityTek@lemmy.worldOP
    link
    fedilink
    11 year ago

    Thanks for the advice. I’m actually very experienced with vhosts, but my understanding was that vhosts are an Apache thing and Nginx uses different terminology. Unfortunately I am still very green when it comes to Nginx. What you described is exactly what I intend to implement though, and I believe my Mastodon install is already configured properly for that to work. It’s just the Lemmy Easy Deploy script that tries to bind all traffic on port 443 where I run into problems.

    • immibis
      link
      fedilink
      41 year ago

      @TrinityTek vhosts also refers to the general concept. In nginx you configure multiple servers with the same listening addresses but different names.

      • @TrinityTek@lemmy.worldOP
        link
        fedilink
        11 year ago

        Yes, it’s very similar in Apache, but different enough for me to feel a little out of my comfort zone. I appreciate the tips.

        • immibis
          link
          fedilink
          21 year ago

          Here’s what I have for Pleroma.

          server {
          server_name social.immibis.com; # this is what matches the domain name
          root /var/www/social_html; # empty folder
          location / {
          proxy_pass http://localhost:4000;
          }

          # this block was from the pleroma documentation, I think. Mastodon and Lemmy might have their own recommendations. Upgrade is to enable proxying websockets. and the rest seems generally sensible for proxying.
          proxy_set_header Upgrade $http_upgrade;
          proxy_set_header Connection “upgrade”;
          proxy_set_header Host $http_host;
          proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
          client_max_body_size 16m;
          ignore_invalid_headers off;

          # when you run Certbot it will change this to 443, insert SSL configuration, and set up a redirect on port 80
          listen [::]:80;
          listen 80;
          }

          • @TrinityTek@lemmy.worldOP
            link
            fedilink
            11 year ago

            Thank you for sharing your config and advice! I appreciate it. I got it working along with ssl certs installed with certbot and all is well. Cheers!