Wow, thank you for these great resources! I will check it out. I really appreciate it!

Thanks for the suggestion! As Nix asked, do you happen to know of a guide or any documentation I could reference for this?

That sounds like a good idea. Do you know of any documentation for this? I’d like to give it a try.

Thank you, that SQL command looks like exactly what I’m after! I’m going to give that a shot. I appreciate the help!

Thanks for the perspective! I am a reluctant newcomer to Docker so I appreciate it. Time for me to get with the times and embrace Docker since that’s the most popular installation method for many of my favorite self hosted platforms these days. It might take a while for me to really get used to it though. Since I have this setup and working it will probably remain as is, but I’ll make a point to do a pure Docker setup on a similar build in the future.

Thanks for the suggestion. What would be the benefit of switching to a docker install of Mastodon?

Thanks for pointing that out! In this case I am using subdomains so hopefully I won’t run into any issues with that. I recently bought fdr8.us with the intention of creating subdomains under it for my federated projects. Mastodon.fdr8.us and Lemmy.fdr8.us are now live. If I do a kbin instance it will probably follow the same format.

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!

I didn’t plan it that way. I installed Mastodon first and didn’t use a Docker install. I configured Nginx and reverse proxy and then tried a non-Docker Lemmy install from scratch. That failed, and I believe the reason was some minor version differences in the dependencies. That’s when I asked for advice and got a few recommendations to try the Lemmy Easy Deployment script. I would prefer to have done the from scratch install if there was current documentation and dependencies were available, but if there is I wasn’t finding it. The Docker compose Lemmy install method worked well enough though so I’m happy with that.

Thanks for talking through it with me, everyone. I got it working with a Docker compose install of Lemmy and a non-Docker Mastodon install. Reverse proxy was configured manually in nginx. Mastodon.fdr8.us and Lemmy.fdr8.us are now live! I have some fine tuning to do still and a lot of setup, but I’m happy that they are working. Cheers!

This worked great! Thanks again for the advice! When the from scratch install didn’t work, multiple people suggested the easy deployment script. For my setup the Docker compose deployment was perfect and offered the opportunity for customization I needed. The easy deployment script does look pretty slick though if someone just wants a turnkey setup and wants to dedicate their whole box to it.

I just got it working. I used a Docker install for Lemmy but not for Mastodon and setup reverse proxy manually. I still have some fine tuning to do, but it works! Woot!

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.

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

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.

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.

Interesting point. I hadn’t given that any consideration but if my Mastodon/Lemmy plans don’t work out I might give it a shot.

I gave that a try but actually ran into a problem with that too. I setup Mastodon on the same server earlier and was planning to use Nginx server blocks to send traffic for mastodon.fdr8.us and lemmy.fdr8.us to the appropriate destination, but the script failed when it tried to bind all traffic on port 443 and Mastodon is already listening on port 443. I had hoped for both to listen on port 443. This is actually somewhat unfamiliar territory for me as usually I am working with Apache and virtual hosts, but I’m hopeful I can make it work. I am very familiar with Apache virtual hosts and have worked with them extensively. I hope I wasn’t crazy to assume I could run Lemmy and Mastodon on the same server on Nginx in a similar fashion.

Mastodon.fdr8.us is now live. Lemmy.fdr8.us coming soon!

Thanks for the advice. I’m old school and never use Docker, but maybe it’s time I get over that. I’m actually out of my element anyway in that I do a lot of self-hosting but up to this point it has almost all used Apache and MySQL rather than Nginx and Postgres. Hopefully someone will come along with a solution for the diesel-async compiling error while I’m at work for the next few hours, but if not I’ll give your suggestion a shot this evening.