What is the issue, exactly, that led to FSE going down?
I don't want to maintain hardware for this reason. But I also don't want to cuck to VPS hosts, since if they ban me I lose my data. I found the ideal compromise: daily backups.
I have a cron job that runs every day to pull all the shit updated since the last time it ran. I specify this because sometimes the computer running that cron job is off for whatever reason and so a day or three are skipped. But it pulls the changed data from all those days.
So if the VPS host jannies me I'll either make a new account on it or just find another VPS host, and do the same thing. I keep all my data and they have to maintain the hardware to make my shit run.
@NEETzsche
You're over thinking this.
You have your app server on one VPS or dedi host, and then have an el cheapo VPS actually talk to the internet.
So you can only get a cheap front janny'd. If you have two or more of them, zero downtime.
This is the setup we run on an imageboard I do the tech for. Port 443 is only even opened up for the reverse proxies, *and* we require client certs for them. So you can't scan the (IPv6 good luck) internet for it.
No host on the planet is going to inspect your disks. They'd sooner just get rid of you, if someone told them something terrible was present.
@p @graf
@mint
Additional complexity. More things to go wrong. The actual owner of the imageboard is using it to learn hosting/IT stuff.
In theory we don't even need the client certs. If you're not coming from one of like 4 IPs, the firewall drops the traffic.
@p @NEETzsche @graf
@mint
Any reason why wireguard specifically? I'm an OpenVPN autist. My internal network uses OpenVPN for site-to-site links.
@p @NEETzsche @graf
@mint
>kernel level
@p @NEETzsche @graf