August 2025: SteamCMD servers unresponsive due to IPv6: Difference between revisions

@@ 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>}}
+{{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=STEAM defaulted to using IPv6 for network traffic.|resolution=Machine configuration changed to reject IPv6 traffic, forcing all inbound connections to use IPv4.}}
 === Narrative ===
@@ Line 7: / Line 7: @@
 On August 18th Sirdog requested Sushiloid's assistance in voice chat, and after some time investigating relevant error logs Sushiloid comes to the conclusion that the error may be due to IPv6 traffic being rejected due to Pterodactyl's desire for IPv4. Sushiloid executes command <code>sysctl -w net.ipv6.conf.all.disable_ipv6=1</code> on the system and reboots it. On the panel, the ''Arma 3'' and ''Abiotic Servers'' boot up without issue.
-Relevant panel users notified of the correction.
 === Footnotes ===
 {{Reflist}}