August 2025: SteamCMD servers unresponsive due to IPv6: Difference between revisions
m Sirdog moved page 2025-08-14: Arma server unresponsive to 2025-08-14: SteamCMD servers become unresponsive without leaving a redirect |
ce |
||
| Line 6: | Line 6: | ||
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. | ||
On August 18th Sirdog requested Sushiloid's assistance in voice chat | On August 18th Sirdog requested Sushiloid's assistance in voice chat. After reviewing relevant error logs Sushiloid hypothesized that the error may be due to STEAM IPv6 traffic being rejected by Pterodactyl. Sushiloid executed command <code>sysctl -w net.ipv6.conf.all.disable_ipv6=1</code> on the machine and rebooted it. | ||
''Arma 3'' and ''Abiotic Factor'' started up without issue. | |||
== Footnotes == | == Footnotes == | ||
{{Reflist}} | {{Reflist}} | ||