this post was submitted on 28 Dec 2025
27 points (100.0% liked)

Reddthat Announcements

776 readers
29 users here now

Main Announcements related to Reddthat.

founded 2 years ago
MODERATORS
ticoombs@reddthat.com
reddthat@reddthat.com
example@reddthat.com
27
[Migration Complete] Moving to Dedicated Server (& Lemmy v0.19.15) (reddthat.com)
submitted 1 day ago* (last edited 12 hours ago) by ticoombs@reddthat.com to c/reddthat@reddthat.com
14 comments fedilink hide all child comments
 

I found some time. and in 15 minutes from this post we will go down for ~1 hour to ensure we have complete data consistency.

  • 09:00 UTC to 10:00 UTC

~~See you soon!~~

HI!!!!!!!!

you are viewing a single comment's thread
view the rest of the comments
[–] ticoombs@reddthat.com 2 points 13 hours ago* (last edited 13 hours ago) (1 children)

I believe I've fixed it.

A recent docker update no longer supports overriding hosts with hostnames. (I was telling mlmym that 'reddthat.com' is 'lemmy-ui'. Which would make it request directly to the lemmy-ui container rather than going back out to CF and back again.

(For others/if you want to know the nitty gritty). I was doing this:

    networks:
      lemmy_internal:
    extra_hosts:
      - "reddthat.com:lemmy-ui"

Which did actually work, but now it doesn't since I updated/installed docker compose v5.0.0. (Seems the correctly enforce the host:IP format now). So I had to do a work around.

[–] e0qdk@reddthat.com 2 points 12 hours ago (1 children)

Thank you. It seems to be working now.

I remember having a devil of a time trying to get mlmym and lemmy to talk to each other on my local system when I was poking around at trying to fix some issues in mlmym a few months back. (I should really get back to that at some point...) They had "https://" hard-coded in front of the domain name parameter -- and I didn't want to have to change the Go source code just to get a dev environment up. I ended up working around it by modifying my hosts file (to add a .INTERNAL domain), ran things under podman with host networking, configured Apache on the host to reverse proxy into both containers, and set up a self-signed cert that I had to rebuild into the mlmym docker (by copying in the appropriate crt files + running update-ca-certificates via the Dockerfile). In retrospect, I probably should've just modified the code...

What was the workaround you had to implement to fix this one?

[–] ticoombs@reddthat.com 2 points 11 hours ago* (last edited 11 hours ago) (1 children)

I had to tell our main_nginx that it is "reddthat.com".

services:
  proxy:
    image: docker.io/library/nginx
    ...etc...
    networks:
      default:
      lemmy_internal:
        aliases:
          - reddthat.com

Now its: {user} -> CF -> {server_nginx} -> {frontend_nginx} -> mlmym => ((docker internal network)) -> {main_nginx} -> {{lemmy-ui/api}}
Instead of: {user} -> CF -> {server_nginx} -> {frontend_nginx} -> mlmym => CF -> {main_nginx} -> {{lemmy-ui/api}}

[–] e0qdk@reddthat.com 1 points 6 hours ago

...and it's down again. 🫠️