| OP Here. I have a single configured email address on which I received my welcome email on July 15 and "Server Locking" email today. Looking into Hetzner dashboard, it seems they did not delete my instance, just turned it off and banned my IP so I cannot ssh into it.
There is an option to request unblocking which I will request soon and which wants me to answer "What caused this problem?" and "How do you plan to correct this problem and prevent for the future?". This was a development instance: running docker, postgres, SchemaSpy, some service emulators, node, vscode and accessed the services through ssh port-forwarding. It seems there is an "Abuse" incident linked to the blocking of my IP but I only see the incident ID, no additional details. This was a dev instance, I did not think about making it airtight. I do not rule out that someone broke into it and violated their terms (this happens with production systems and I am definitely a worse engineer than people there). If this happened, I am happy they locked it down but I wish they informed their users in these cases: I had git ssh keys and other secrets there which I proactively revoked and more information on the incident would definitely have helped choose the right course of action. |
I have quite a bit of rep with Hetzner, so they didn't outright nuke me, but I once got an abuse email because I was running an IPFS daemon, and the reference IPFS implementation allows RFC1918 IPs and GCNAT on discovery announcements... so dialing into nowhere a lot upset the router.
With the new no-ip-at-all option you can set up a Network and set up an extra instance as NAT as you would with a home network. That should cut down on issues like that.