Selfhosted

40438 readers

633 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

Anyone hosting Lemmy and Mastodon on the same server? (self.selfhosted)

submitted 1 year ago by TrinityTek to c/selfhosted

45 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] veroxii 18 points 1 year ago (4 children)

You need a reverse proxy like nginx or traefik. Your mastodon server is using the web ports. Lemmy also wants to use the same ports. Obviously the can't both use them.

The solution is to let neither use the ports and set them up on some other ports.

The reverse proxy is then set up as your main "web server". It will then look at every request coming in and based on the domain name or url requested redirect (or rather forward or proxy) the request to the correct service.. mastadon or Lemmy.

I run dozens of services on the same server. And use traefik to sit in front and manage it all.

[–] TrinityTek 2 points 1 year ago* (last edited 1 year ago) (3 children)

I have reverse proxy configured for Mastodo using Nginx. It's the Lemmy Easy Deploy script trying to bind all traffic on port 443 where I run into problems.

[–] [email protected] 8 points 1 year ago (2 children)

Don't use that silly script. Easiest is to use the docker compose method and modify the compose file to remove the nginx container since you already have nginx. Then once you have lemmy's containers running, add config to nginx to point to the ports lemmy/lemmy ui listen on

[–] TrinityTek 4 points 1 year ago

Thanks for the tips! That sounds like a great approach. I'll give it a shot.

load more comments (1 replies)