August 2025: SteamCMD servers unresponsive due to IPv6
Narrative
On August 14th, 2025 BBM_Ping pings @SYS:OP reporting that the Arma 3 server was broken. Sirdog begins investigation while at work, and observes Pterodactyl's ovh.main 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.[1] 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.
In the early morning of August 15th Sirdog reports that he was unable to make any ground after 1.5 hours of troubleshooting, believing at the time that STEAM was at fault due to Steam API hexidecimal code 0x2 appearing, which based on research showed that STEAM's content servers were at fault.
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 sysctl -w net.ipv6.conf.all.disable_ipv6=1 on the system and reboots it. On the panel, the Arma 3 and Abiotic Servers boot up without issue.
Footnotes
- ↑ Sirdog would later discover in September that his work's network blocks non-standard port
8080, hence Pterodactyl seemingly reporting the node is down, as the panel is just a GUI for an API Pterodactyl uses.