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

From Endurance Coalition
Jump to navigation Jump to search
← Older editNewer edit →
VisualWikitext
No edit summary
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=STEAM defaulted to using IPv6 for network traffic.|resolution=Machine configuration changed to reject IPv6 traffic, forcing all inbound connections to use IPv4.}}
{{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 and force IPv4 traffic.}}


=== Narrative ===
== 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.   
On August 14th, 2025 BBM_Ping pinged<code>@SYS:OP</code> reporting that the Arma 3 server was broken, citing that it cannot connect to STEAM servers. Sirdog began investigation while at work, and observed the <code>ovh.main</code> Pterodactyl node health as red, indicating it is not working. Sirdog escalated to Sushiloid and reported that all services were impacted. BBM_Ping then clarified that the ''Vintage Story'' server was unaffected, and that the error is specific to STEAM based on the console error logs. Sirdog later discovered by accessing the panel on his phone that only ''Arma 3'' and ''Abiotic Factor'' were 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> Sirdog informed Comrade same-day to cancel an ''Abiotic Factor'' event as the server would not be functional in time for it.   


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 <code>0x2</code> appearing, which based on research showed that STEAM's content servers were at fault.   
In the early morning of August 15th Sirdog reported 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 <code>0x2</code> 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 <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.   
On August 18th Sirdog requested Sushiloid's assistance in voice chat, and after some time investigating relevant error logs Sushiloid hypothesized that the error may be due to IPv6 traffic being rejected because of Pterodactyl's desire for IPv4. Sushiloid executed command <code>sysctl -w net.ipv6.conf.all.disable_ipv6=1</code> on the system and rebooted it. ''Arma 3'' and ''Abiotic Servers'' booted up without issue.   


=== Footnotes ===
== Footnotes ==
{{Reflist}}
{{Reflist}}

Revision as of 18:56, 5 October 2025

Template:Sysop incident header

Narrative

On August 14th, 2025 BBM_Ping pinged@SYS:OP reporting that the Arma 3 server was broken, citing that it cannot connect to STEAM servers. Sirdog began investigation while at work, and observed the ovh.main Pterodactyl node health as red, indicating it is not working. Sirdog escalated to Sushiloid and reported that all services were impacted. BBM_Ping then clarified that the Vintage Story server was unaffected, and that the error is specific to STEAM based on the console error logs. Sirdog later discovered by accessing the panel on his phone that only Arma 3 and Abiotic Factor were affected.[1] Sirdog informed Comrade same-day to cancel an Abiotic Factor event as the server would not be functional in time for it.

In the early morning of August 15th Sirdog reported 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 hypothesized that the error may be due to IPv6 traffic being rejected because of Pterodactyl's desire for IPv4. Sushiloid executed command sysctl -w net.ipv6.conf.all.disable_ipv6=1 on the system and rebooted it. Arma 3 and Abiotic Servers booted up without issue.

Footnotes

  1. ↑ 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.
Retrieved from "https://wiki.edcgaming.org/index.php?title=August_2025:_SteamCMD_servers_unresponsive_due_to_IPv6&oldid=3121"