Thx I appreciate the input. I have already a lot of things set up on the server and switching now would be painful and time consuming. I also use docker in conjunction with kvm-qemu and had I known about proxmox a month ago I would not have construct it at such but alas. I will however in the future get another hardware which I will use as a home server and I will definitely give proxmox a shot.

Unrealted but Alpine Linux is based af!

Well I already got static IP from my ISP and configured Wireguard on my directly on my router so I think I’m good.

Something secure and easy to understand and setup for beginner. The easier the better. I don’t mind writing config files if I can understand it.

Omg thank you very much. I’ll definitely look it up.

I mean i have a wireguard on my router but how can I point the domain from my provider like (godaddy) to my server without opening ports?

And if i wanted to install nginx from debian repo and make the config file for immich docker instance, bitwarden dcoker instance… how would the config files and ssl certificates for nginx look like?

I’m currently cannot post it here and also since it didn’t work the first time I’m using only http for jellyfin and immich but i can later post the docker config for bitwarden.

I’ll definitely take a look at so thx. Also I’m using duckdns right now so i didn’t need to port forward anything but if I use my domain do i need to port forward ports 80&443 from through my router to my debian server (192.168.200.101)?

Okay and in that case can you please point me in the right direction how should i write the nginx configs for each of my services and also make ssl certificates?

Yeah but when I last tried nginx on my bitwarden host and another on my jellyfin host i could access the one for bitwarden on port 81 of my server but couldn’t access the other nginx web page on port 85 even though i have written it in docker compose file and the port 85 was also open on my server.

Nah I get what you said earlier but what I’m saying is that you should also inform you ISP. And that they don’t care isn’t necessarily true for every ISP especially if they may get a letter about it.

Ok forgot to mention you gotta verify if it’s okay with your ISP first.

I mean it’s not ideal but if you don’t mind the extra electricity, have some old laptop or raspberry pi you can use to run relay or bridgde and limit your bandwidth than I don’t see why you shouldn’t.

Also I2P is really faster than tor since you contribute to the network just by using it unlike tor. Although I’m not sure how many users this network has nowadays :/

I think the I2P is better designed for torrenting plus Tor is just way too slow especially for bigger files simce most people only use tor but don’t run their own relays.

Since I care more about anonymity I think I would rather sacrifice speed and use I2p even on clearnet.

Yes. But the main ssd where the OS is installed is also encrypted with different password. So you must first unlock the ssd anyway to automount the hdd.

Oh sorry seems i explained it poorly.

That encrypted drive drive is set to automount on boot since I added it to /etc/fstatb and /etc/crypttab.

This makes things easier. Thank you for clarifying.

And if I make docker compose file for jellyfin and specify that path to encrypted hdd example( /media/user/sda1/jellyfin-media) will it be able to read that media?

Would it be okay to contact you via signal/simplex or any messaging app for help if I’ll have more very specific questions?

And is there any problem to setting this up in docker compose?