August 2025: SteamCMD servers unresponsive due to IPv6: Difference between revisions
m Sirdog moved page August 2025: SteamCMD servers become unresponsive to August 2025: SteamCMD servers unresponsive due to IPv6 without leaving a redirect |
ce |
||
| Line 2: | Line 2: | ||
== Narrative == | == Narrative == | ||
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. | 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 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. | 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. | ||