footty

Well, I'm here again. I get a 504 gateway timeout after upgrading or doing docker-compose down, and found a weird fix for it.

1. docker kill your postgres instance
2. Go to your webpage and wait for it to tell you an error
3. docker-compose up -d and now it'll work

I tried killing postgres and bringing it up immediately as well but that did not fix the problem. Weird magical incantation and downvote me all you want, just wanted to throw it out there.

That is a conf for the host system nginx, in which you enter the lemmy port defined on the left side of your proxy service's port section.

...
ports:
      # actual and only port facing any connection from outside
      # Note, change the left number if port 1236 is already in use on your system
      # You could use port 80 if you won't use a reverse proxy
      - "{{ lemmy_port }}:8536"

Yup, this thread doesn't show up in my own instance, even though it shows me as subscribed.

On the other hand, a comment of mine showed up in a community which still says pending. Over time these bugs will be ironed out we just gotta stay patient.