Ouff… way too accurate.

mercii :)

when I do this I get the error message that the ports are already in use by the vpn container :|

but I thought the containers had to have “network_mode: container:vpn”, in order to strictly only be able to communicate through the VPN.

Ah thanks! That solves one of the services at least. Merciii <3

sorry im still quite new to this… do u have an example of another compose file that does this? Not sure where I put what.

how haha

Right, my bad for the misleading/wrong title. This is my question - how do i map a port to a container that uses network_mode: …

Sorry that was my question, dont want to use the port twice, I want to tell the compose file what to use for each container, but I dont know how.

• Fixed the title, mb

Thanks for the detailed answer, I was able to solve my problem just with what /u/mara said suggested above :)

Yeah I also don’t want my folks to have to “ignore” the warnings either. So will defo have the https set up before giving them access.

Yeah I do not have a domain. I did before but for some reason i struggled to wrap my head around reverse proxies and domains. And I prefer to not have to pay for yet another service as I’m just a student :P

This does seem like the easiest option so far, i’ll try to play around with this, thanks!

Do either of them matter in terms of life of the hardisks? My server just had one of its HDDs reach EoL :| Kind of want to buy something that will last a very long time. Also, not familiar with ZFS, but read that Synology uses Butterfs - which always sounds good in my ears, been having a taste of the filesystem with Garuda on my desktop.

Yeah already quite familiar, already got a server but looking for something more premium, but essentially deliver the most easy platforms for the rest of the family to use.