Been hosting Public Websites and Gameservers since 2020 from my residential connection and never got ddosed in that time

point the AAAA/A records to your corresponding ips and allow incoming traffic on port 443, 80 on your Firewall. You may also need to set up a dyndns client if your isp changes your ipv4 frequently.

Had the same problem a while ago, you need to regenerate the machineid: https://wiki.debian.org/MachineId

a mercury arc rectifier

its a mercury arc rectifier. They look quite neat under load

Not routing all your unencrypted traffic through a company located in an dictatorship

the original tempo got abandoned by its developer

You dont have local ips with ipv6, everything is globally routable

ipv6. No need to deal with hacky translation and dns bs if dont do nat.

deleted by creator

You are pretty much as safe as it gets as long as you update that container. Ip/Port scanning basically isnt a thing in ipv6 land as youd have to scan the entire /64 which amounts to 18,446,744,073,709,551,616 addresses.

The owls are not what they seeem, dad

they do

I know how to selfhost stuff, I just dont want to deal with docker

Any way to set this up without docker? Couldnt find anything in the docs

Mountains. We got a lot of em

Having something as critical as your vpn depend on a 3rd party kinda sounds like a bad idea

Are there any european alternatives to Serverpartdeals?

Cat.