this post was submitted on 28 Dec 2025
29 points (100.0% liked)
Reddthat Announcements
776 readers
19 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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-certificatesvia the Dockerfile). In retrospect, I probably should've just modified the code...What was the workaround you had to implement to fix this one?
I had to tell our
main_nginxthat it is "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}}...and it's down again. 🫠️