Octavusss

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.

The cake is a lie

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.

Some of my best slaves were argonian's.. Ok that came out wrong.

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.