The server was restarted on the evening of the griefing, 27 October 2021, and kept off the internet afterwards (Aftermath of the 2021-10-27 Grief). A status printout posted the next morning showed the Minecraft service up and running since 19:55 UTC the night before 1.
That did not stop the questions. kira, who was hosting, grew tired of repeating himself: “how many fking times do I have to say that server is not connected to the internet” 2.
The second chapter came on 7 November, the day the old backup returned. prop asked, apologetically, whether the IP could be forced to change, “because they have already logged that this ip has a server” 3. A reboot did not change it. On 3 December prop could finally report: “the ip finnally changed” 4. The new address was 223.178.80.58.
Primary sources
-
● mc-server.service - Minecraft Server manager Loaded: loaded (/etc/systemd/system/mc-server.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-10-27 19:55:48 UTC; 7h ago Process: 11519 Ex…
-
how many fking times do I have to say that server is not connected to the internet
-
bro im sorry if im disturbing you again but is there a way to force change in ip because they have already logged that this ip has a server
-
the ip finnally changed
