Yes, there is: 0.18.2-rc.1, which has the hot fix, but will also require a DB query to “fix” the modlog once upgraded.

For me it’s 3AM rewatching a Star Trek series I’ve already watched many times (in this case, Voyager), knowing full well my work day starts in 5 hours.

Sorry I didn’t get a chance to look at this, but I’m mostly on mobile and the link doesn’t work.

For future reference you can put it in a code block and lemmy-ui should be able to render it for you.

Example code block

I recommend using the docker images directly. As you see, the ansible scripts are basically another abstraction layer used to build the docker containers and their configs (and has string substitutions like {{some_string}} which are not valid for docker-compose.yml). Some will disagree but I feel ansible adds unnecessary complexity to deploying lemmy containers.

Anyway, glad you figured it all out!

Hi there! This sounds like you might just have a typo in your docker-compose.yml file. It might be helpful if you posted your docker-compose.yml contents here (be sure to remove any sensitive information).

Line 26 of my docker-compose.yml file is the volume block/map for letsencrypt. Did you perhaps mix tabs and spaces, or have one too many spaces in your indentations, in your yaml file? That’s a no-no…

Personally, I setup my instance using the same guide as you, opting for the docker containers. There were definitely a few pitfalls to deal with.

Hi there!

TL;DR: probably have an nginx misconfiguration. Check the nginx logs for errors.

You don’t need to install and run nginx on the host. It has its own container in the docker-compose.yml which gets started up on docker-compose up -d

If both instances of nginx are trying to bind to the same port, one will start and one will fail.

Is the lemmy proxy nginx docker container running? Check with: docker ps or docker container ls. If the lemmy nginx proxy container isn’t running, try stopping the host instance of nginx (systemctl nginx stop) and restart docker lemmy (docker-compose down, docker-compose up -d), the try to access your site again.

I think the safest option is to not host from your home network. If you aren’t up to date on security patches, you could potentially expose a lot of data from an insecure server running inside your network.

There are precautions you can take, like isolating any external facing servers from the rest of your network, for example, but I generally recommend using a hosted service instead.

Great write up!

Is… is that a photoshopped nail?

From my instance, I’ve been crossing to other instances fine to post, upvote, etc.

Can you elaborate on your experience a bit more? I can’t say I have had any issues as you’ve described. If something doesn’t look right, or isn’t working the way you expect, it might actually be a bug.

Very true. It would be sad to build up a persona on a smaller instance to then have it go dark and take your user with it. Other than losing your collection of “upvotes,” you can just recreate a new user with the same display name on another instance and keep going. 👍

Holy crap, you can do Slack style emoticons? Huzzah! 🎉

It’s at the top of the list on join-lemmy.org’s popular server list, next to lemmy.world and beehaw.org, of course new users will sign up on the more popular ones. Plus, a few posts on reddit called out these three which set everything in motion.

Once folks start to understand how it works, they might start to sign up on other ones, for a “cooler handle @ address” for their user, or register a domain and start their own instance like I did.

Anyway, welcome aboard, right?