This weekend I installed my own Lemmy instance, so I want to share the instructions to help others, who want to do the same.

I used the Ansible script and it was pretty easy. First I wanted to use my existing PosgreSQL server, what I already use for my Akkoma server. It didn’t really work out that well, the migrations failed and I couldn’t figure out what didn’t work. Eventually I just went back using PostgreSQL on Docker. If you don’t start modifying the script, and just use the dockerized PostgreSQL, you will have no problems with the installation.

What you need first is a cheap (or expensive, if you decide to invite million friends to your instance) VPS: I use Hetzner Cloud, which has been working for me super well for many years and I’m very happy with the service. I got the second cheapest AMD instance, with two cores and two gigabytes of RAM. Before buying the instance, you need to upload an SSH key to Hetzner. If you don’t have one, creating is easy from the command line: ssh-keygen -t ecdsa. What you need to give to Hetzner is your public key; the one with the .pub extension in your $HOME/.ssh directory. Do not give the private key to anyone. Go with Ubuntu, might work the best with the Ansible script.

You can now SSH to the instance: ssh root@<ip-address from the Hetzner control panel>.

Next what you need is a domain name for the server. Lemmy wants an A record, and being a good internet citizen, you also get an AAAA record for the IPv6 users. I use Cloudflare for my DNS records. It’s very easy to set them from their control panel. Do not set the proxy on just yet, we’ll come back to that later. You can get the IP addresses from the Hetzner panel. The IPv4 you just copy, for the IPv6 you have to replace the ::/64 with ::1.

Now you should be able to ssh to your instance with the new domain name. It’s time to follow the Ansible instructions for Lemmy, just run the script and see it’s done correctly with no errors. When you can login to your Lemmy instance as an admin, go back to Cloudflare and turn on proxying to your A and AAAA records to hide your server IP and prevent DDOS attacks.

The first time federation is a bit slow in the beginning. Go to search in your instance, and search for !lemmy@lemmy.ml. It takes a while for the result to arrive. You can SSH to your instance, and look for the logs of your Lemmy image:

root@lemmy:~# docker ps
CONTAINER ID   IMAGE                        COMMAND                  CREATED        STATUS        PORTS                                NAMES
9e940b84cc45   dessalines/lemmy-ui:0.17.3   "docker-entrypoint.s…"   22 hours ago   Up 22 hours   127.0.0.1:6719->1234/tcp             lemmynaukio_lemmy-ui_1
6442d9d93554   dessalines/lemmy:0.17.3      "/app/lemmy"             22 hours ago   Up 22 hours   127.0.0.1:20926->8536/tcp            lemmynaukio_lemmy_1
36a030f7bf27   asonix/pictrs:0.3.1          "/sbin/tini -- /usr/…"   22 hours ago   Up 22 hours   6669/tcp, 127.0.0.1:8934->8080/tcp   lemmynaukio_pictrs_1
979be89076b2   postgres:15-alpine           "docker-entrypoint.s…"   22 hours ago   Up 22 hours   5432/tcp                             lemmynaukio_postgres_1
774112d48c87   mwader/postfix-relay         "/root/run"              23 hours ago   Up 23 hours   25/tcp                               lemmynaukio_postfix_1

> docker logs -f 6442d9d93554

This should start showing you the federated posts in real time. Eventually your search will show up, you can click the community open and subscribe to it. Do the same for other communities what you want to follow, federate other instances and eventually you are part of the federation. It gets faster and easier for the other users, but the beginning is a bit slow.

Congratulations, you’re now a Lemmy admin and part of the bigger federation.

  • Demigodrick@lemmy.zipEnglish
    1·
    2 years ago

    Hey, have you managed to get emails working? Hetzner blocks port 25 and i cannot for the life of me figure out how to get emails to send using any of the external services.

      • phase_change@sh.itjust.worksEnglish
        1·
        2 years ago

        I played a bit with trying to get a lemmy instance set up on my xcp-ng instance in the home lab. This is the first time I’ve ever touched docker, and email was where I failed. I’ve got a working mail server, but I couldn’t figure out how to get docker to talk to it. Any pointers for some howto in that piece for someone who’s pretty technical but new to docker?

      • Demigodrick@lemmy.zipEnglish
        1·
        2 years ago

        Thanks, i don’t want to unblock port 25 particularly, i’ve been trying to use port 587 with no luck (I get an error about connections). Not sure if the issue is with my postfix relay or with my lemmy hjson file. No matter what i try to change, i can’t seem to get a connection to work.

        I’ll keep trying :)

    • ture@rational-racoon.deEnglish
      1·
      2 years ago

      By default they block ports 25 and 465 afaik you can request getting them unblocked after you paid your first invoice and your account is at least one month old. For some reason they aren’t blocking port 587 so you could connect to your mail server via that port if you don’t want to wait for the first month to be over using starttls and after a month switch to 465 with normal tls. And as @mrmanager@lemmy.today already mentioned you shouldn’t use port 25 since you’d be sending your mails unencrypted.