• 0 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle

  • It sounds like what you need to do at this point is find what IP address your lemmy instance and mastodon instance containers are using on your VPS. you can do “docker inspect containername” and look for the IP address in there. it might be something like 172.16.0.1 for lemmy and 172.17.0.1 for mastodon. then you want to set up your reverse proxy to point lmy.my-domain.tld to 172.16.0.1:80 (or whatever port you set lemmy to use) and then mstdn.my-domain.tld to point to 172.17.0.1:80 (again, port might be different, i dont know what the default port is)

    -IF- both of the containers are using the same IP, then you will need to make sure that they are using different ports. if they are on the same ip and same port, whichever container loads 2nd will fail to properly load, because when a port is taken on an IP address, it is reserved and nothing else can try to listen on that port.


  • So a reverse proxy is sort of like a phonebook or directory, it routes outside requests to the appropriate place. So imagine your reverse proxy is a receptionist, someone comes in and says “hey I am looking for plex.mydomain.com” the receptionist would then use the phonebook and say “ok if you are looking for plex.mydomain.com, go to building 192.168.1.10 (the ip), room 9000 (the port)”

    Since you are asking about dockerized services, the networking for those can be done in several different ways, but the one thing that really matters is that each service needs to have a unique combination of ip and port, because only 1 service can live at each address. With docker, you could set up multiple services that use the host server’s ip, in which case each container will need to be on different ports, or you could have it so each container has its own ip, in which case the port can be anything.










  • To view only posts from your subscribed magazines, click the hamburger/3 lines icon next to your username on the top right and there is an option for subscribed.

    As for how you know where you’re about to click to, I believe there is a pr on the code git repo to add instance names to both the user and post so it’s more obvious when doing cross instance interactions

    And lastly fyi, kbin.social is an instance of the software called kbin



  • Typically you’d have a server running on a device on each UPS, and the clients would be the other devices also plugged into that UPS, so when that UPS is low, everything plugged into it will turn off. If you have another UPS elsewhere in the house, you would have another server installed on a device there so it can monitor that UPS that it is plugged into, and tell the other devices also plugged into that other UPS to shut down. Without knowing the layout you are running though, there’s no way to know if NUT is what you need or want.

    So in your case it would likely be to plug your server and nas both into the same UPS, and when the server detects the UPS is low battery, it will tell the NAS to shut down. This would also require the switches/router/whatever to also be on a UPS to hold power of course. So then it basically becomes each little cluster of devices that need UPS would also have a switch nearby that is also on the UPS