August 2025: SteamCMD servers unresponsive due to IPv6: Difference between revisions
Created page with " Category:Sysop events" |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Sysop incident header|summary=The ''Arma 3'' and ''Abiotic Factor'' servers would not start and became unresponsive.|reporter=BBM_Ping|date-report=August 14th, 2025|date-resolved=August 19th, 2025 (5 days)|cause=STEAMCMD defaulted to using IPv6 for network traffic.|resolution=IPv6 is disabled at the machine level by Sushiloid, forcing all traffic to revert to IPv4.<ref>Accomplished via: <code>sysctl -w net.ipv6.conf.all.disable_ipv6=1</code></ref>}} | |||
=== Narrative === | |||
On August 14th, 2025 BBM_Ping pings <code>@SYS:OP</code> reporting that the Arma 3 server was broken. Sirdog begins investigation while at work, and observes Pterodactyl's <code>ovh.main</code> node's health is red, indicating it is not working. He escalates to Sushiloid and reports that all services are impacted. BBM_Ping later reports that the ''Vintage Story'' server was unaffected, and that the error is specific to STEAM based on the console error logs. Sirdog later discovers by accessing the panel on his phone that only ''Arma 3'' and ''Abiotic Factor'' are affected.<ref>Sirdog would later discover in September that his work's network blocks non-standard port <code>8080</code>, hence Pterodactyl seemingly reporting the node is down, as the panel is just a GUI for an API Pterodactyl uses.</ref> He advises Comrade same-day to cancel an event for the server as, due to availability constraints of systems operators, that the server would not be functional for the event. | |||
=== Takeaways === | |||
- | |||
=== Footnotes === | |||
{{Reflist}} | |||