So…it’s working now? I haven’t touched anything yet, but I just checked my instance again and it works perfectly fine on desktop now. It always worked through Voyager, so I was able to let people know there was an issue. If it comes back I’ll try some of these suggestions to find a more permanent fix.

Meaning I just wait a bit and retry later?

Upgraded to 0.18.5, which now gives me this error:

lemmy-lemmy-ui-1  | API error: FetchError: request to http://lemmy:8536/api/v3/site?auth=AUTH_KEY failed, reason: connect ECONNREFUSED IP_ADDRESS:8536

I created a gist with my compose file: https://gist.github.com/osiriswrecks/26a875576d3bbcf11923d7715ac15e6e. It should be stripped of all private info. I tried changing the version from 0.17.3 to 0.18.0 and the server returns a gateway error after restarting.

It’s a bold strategy, Cotton. Let’s see if it pays off for them.

Following this trend, I would love to see r/superbowl turn into just photos of John Owliver.

“Alright boys, you heard him. He said the magic word. Let’s pack our things and get out of here.”

100% this. I ended every day doomscrolling until I got bored or the feed accidentally refreshed and sent me back to the top. Now I’m starting to see how bad that was for me.

I’ve felt this so hard the past few days. I would often post on Reddit and never get noticed or find myself just wading through a sea of garbage. Here, it’s a lot less noisy but the interactions I do have are noticeably more genuine and that feels great.

If you’re a politician or a business owner, you are accountable to your constituents. So a politician needs to be elected, and a business owner can be fired by its shareholders,” he said.

Someone get this man a hearing aid, because he’s gone completely tone deaf.

This makes sense to me. I was wondering how many were active, engaged communities and how many were shells or ghost towns.

Wait WHAT.

So looking at this again now, am I taking that whole block and adding it to the container’s nginx.conf? If so, does that mean I have to change what port it’s currently listening to (because there’s already a rule in the file for port 80)?

There’s a comment in that server rule that says “this is the port inside docker” and a comment immediately after that says “this is facing the public web”, which confuses me.

It blows my mind that Reddit can look at 90% of its communities going dark in some way and think, “yeah, this is fine.”

EDIT (AGAIN): Thank you all for the comments on total subs. It’s still clearly not 90%, but it still appears to be a significant portion of the active Reddit community. For the interested, check out the comments below for stats. :)

The one meant for the Docker container or the one on the host?

I think this is where my lack of experience with Docker is showing.

I spun up a DO droplet and installed nginx, Docker CE, and Docker Compose. Then I went through the instructions on the page you linked to and it set it up just fine but when I went to my droplets IP address it wouldn’t connect. I had to add a config file that pointed traffic coming into the droplet on port 80 to redirect to the Docker container instead. Am I overcomplicating it?

I seem to be having a lot of lag at the moment, and my post was created twice so I’m just going to delete the other one and start from here…

So I have this set up per the instructions. My instance is on a Digital Ocean instance, and I’m using nginx on the host to point to localhost:1235, but that’s about all that conf file is doing. Is there something else I need to do?

It’s working fine for me, too. I’m spending the next week or so pulling my saved content but even if old Reddit stays I don’t think I can anymore.