

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.
I’m Oha and I run the funny fake download button instance. More about me: https://ohaa.xyz/


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.
how do you tell?


Had the same problem a while ago, you need to regenerate the machineid: https://wiki.debian.org/MachineId
Not routing all your unencrypted traffic through a company located in an dictatorship


the original tempo got abandoned by its developer


ipv6. No need to deal with hacky translation and dns bs if dont do nat.
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.
just use firefox. its not that hard
Been hosting Public Websites and Gameservers since 2020 from my residential connection and never got ddosed in that time