Reddthat Announcements

776 readers

25 users here now

Main Announcements related to Reddthat.

For all support relating to Reddthat, please go to !community@reddthat.com

founded 2 years ago

MODERATORS

ticoombs@reddthat.com

reddthat@reddthat.com

example@reddthat.com

[Migration Complete] Moving to Dedicated Server (& Lemmy v0.19.15) (reddthat.com)

submitted 1 day ago* (last edited 1 day ago) by ticoombs@reddthat.com to c/reddthat@reddthat.com

16 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

[–] e0qdk@reddthat.com 2 points 1 day ago (4 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) (3 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 1 points 9 hours ago* (last edited 6 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 (1 replies)