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.

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 hope it is released soon as well. I’m hoping some of the other open issues are addressed.

Currently there are 15 lemmy-ui bugs open, and 20 lemmy backend bugs open, against 0.18.0.

• lemmy backend bugs
• lemmy-ui bugs

Upgrading my instance to 0.18.0 has caused a lot of problems. One major issue is the main web UI won’t even load (returns a blank page with just text Server error), unless you manually remove the site’s image icon via a SQL query in the Postgres database. So, upgrade to 0.18.0 at your own risk.

Also, this is not intended as a criticism to anyone. Just a warning that 0.18.0 is a bit unstable and waiting for 0.18.1+ is a safer option for the larger hosted communities (my opinion).

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.

Don’t upgrade to 0.18.0! It has a lot of issues.

There was a pretty big jump in active instances, too!

Active daily user count is about 50k.

Great write up!

Huzzah!

Commenting to bookmark this for future reference! Great write up. I’ll likely try this on my instance at some point.

Also testing to see if my comment shows up…

I ended up nuking my Postgres DB, and recreating that container from scratch. Not sure what went wrong, but it feels like some data in the DB when upgrading from 0.17.4 to 0.18.0 perhaps broke stuff? 🤷‍♂️

The question is: what percentage of those users are bots? And does it matter?