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.

Easy one to miss! The documentation isn’t very detailed. 🙂

What is your domain set to?

Also I think the !selfhosted@lemmy.world community might be a better place to ask for help.

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!

That’s most definitely a bug, in my opinion. Might want to file an issue on GitHub.

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.

Neat! I’ll definitely check this out.

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), then try to access your site again.

Hell, I went for the longest time resisting the urge to get one, as I have a great gaming laptop (RTX 3070ti,) and eventually caved in. The draw of being able to play anywhere, anytime, plus the hype, is what eventually convinced me. The Steam Deck is pretty amazing, and worth every penny.

Oh, this span builder error. Yeah I’ve been seeing that error since I upgraded to 0.18.0. Sorry, I don’t have a solution for this one.

Glad you figured out your pictrs error though! One other thing I did was update my resolve.conf so that valid DNS hosts were making it to the containers. Also try rebooting your host.

Feel free to add to this discussion. https://github.com/LemmyNet/lemmy/issues/3314

Yay! Thank you for confirming

Yay! Small victories

I turned that off, as well as show online status, years ago.

You should disable tracking everywhere you can. Opt-out of personalized ads. Enable the do not track feature.

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

Active daily user count is about 50k.

Are you running lemmy 0.18.0? It breaks a bunch of internal network connectivity. The short term solution is to add an external network to both the lemmy-ui and pictrs containers, then you can change http://pictrs:8080 to http://your_domain.

Note: there are also some issues in 0.18.0 with comment federation at the moment. Please reply to confirm this comment was seen, thanks!

That was fast…

Wait, another one? Or is this a repost of the one I already subbed to?

Hell yeah! Let’s go Padres!