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

Reddthat Announcements

776 readers
2 users here now

Main Announcements related to Reddthat.

founded 2 years ago
MODERATORS
ticoombs@reddthat.com
reddthat@reddthat.com
example@reddthat.com
30
[Migration Complete] Moving to Dedicated Server (& Lemmy v0.19.15) (reddthat.com)
submitted 2 days ago* (last edited 2 days ago) by ticoombs@reddthat.com to c/reddthat@reddthat.com
19 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 6 points 2 days ago* (last edited 2 days ago) (13 children)

Migrated Successfully!

Pictrs Test:

[–] ticoombs@reddthat.com 4 points 2 days ago (12 children)

Working on fixing old.reddthat.com.

[–] e0qdk@reddthat.com 2 points 2 days ago (10 children)

old.reddthat.com is currently not working (at time of posting this comment). Most pages show unable to retrieve site., although I did get dial tcp (an IP address):443: connect: connection refused. (where (an IP address) is an IP that I've redacted) on some pages.

[–] ticoombs@reddthat.com 2 points 2 days ago* (last edited 2 days 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 1 day 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 1 day ago* (last edited 1 day 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 1 day ago (2 children)

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

[–] ticoombs@reddthat.com 2 points 17 hours ago (1 children)

SORTED! Ended up patching it myself. Enjoy :D

[–] e0qdk@reddthat.com 1 points 14 hours ago* (last edited 13 hours ago) (1 children)

It's up and running again, but now it seems like pagination is broken. (Going to any page and clicking "Next" at the bottom returns a "there doesn't seem to be anything here" error.)

Probably has to do with page=0 being in the URL for next page links?

Edit: Looks like line 213 of state.go should be changed to q.Set("page", strconv.Itoa(p.Page+1)) -- I tagged you in the comment I made about it on the FHF repo too but not sure how well GitHub handles @ notifications.

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

Thanks, patched and its page=2 now. (I wonder how LW never managed to see that... They must not be using that image...!

[–] e0qdk@reddthat.com 2 points 12 hours ago

Sweet. There's another issue open on the FHF repo where someone was questioning :latest vs :main tag so, yeah, there may be some mismatch between what they're running and what they think they are running / was originally documented...

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

😥. I will fix it! I think because we are still going via nginx, it's still has to pass the go-away challenges, which it must be failing and thats why...

Annnd, as we just moved I also only have key access to the server and I made all new keys and don't have one on my other devices yet. (A classic)

Edit: nope, it's now attempting to connect over https to the container... I think I'll need to write a proper patch for it to allow for a override.
It also looks dead in the water/feature complete. So I've moved to FSFs container. (https://github.com/Fedihosting-Foundation-Forks/mlmym).

If I end up making a patch I'll upstream. (I'm surprised LW hasn't made one already)

load more comments (8 replies)
load more comments (9 replies)
load more comments (9 replies)