New pages
Jump to navigation
Jump to search
27 January 2026
- 14:3014:30, 27 January 2026 January 2026: Caddy unresponsive due to port conflict (hist | edit) [594 bytes] Sirdog (talk | contribs) (Created page with "{{Post mortem header|summary=Upon reboot of the entire EDC host, <code>caddy</code> would not start, resulting in all web services being down. |reporter=SierraKomodo |date-report=January 27, 2026 |date-resolved=January 27, 2026 (~5 minutes) |cause=<code>apache2</code> was renabled, resulting in it and <code>caddy</code> both attempting to send traffic on port 80. |resolution=<code>apache2</code> disabled via <code>sudo systemctl disable apache2</code>.}} == Narrative ==...")
10 January 2026
- 22:1422:14, 10 January 2026 January 2026: Vintage Story would not start due to wrong .NET version (hist | edit) [434 bytes] Sirdog (talk | contribs) (Created page with "{{Post mortem header |summary=''Vintage Story'' would not start after reinstallation. |reporter=Fleff |date-report=January 10, 2026 |date-resolved=January 10, 2026 (~12 minutes) |cause=Recent ''Vintage Story'' release required .NET 8 whereas Docker image used for server was .NET 7. |resolution=Docker image changed to <code>ghcr.io/parkervcp/yolks:dotnet_8</code>.}} == Narrative == ''No narrative is available for this post mortem.")
9 January 2026
- 22:5322:53, 9 January 2026 January 2026: Pterodactyl cron job would not run until pteroq restart (hist | edit) [503 bytes] Sirdog (talk | contribs) (Created page with "{{Post mortem header |summary=''Vintage Story's'' scheduled cron job to start and stop at a particular time would not run unless forced to do so by operator. |reporter=Fleff |date-report=January 9, 2026 |date-resolved=January 9, 2026 (~8 minutes) |cause=Not fully known at this time; suspect the Pterodactyl worker queue entered a hanged state. |resolution=Pterodactyl worker queue restarted via <code>systemctl restart pteroq</code>.}} == Narrative == ''No narrative is ava...")
28 December 2025
- 00:0700:07, 28 December 2025 December 2025: Pterodactyl reports cannot connect due to Wings being down (hist | edit) [386 bytes] Sirdog (talk | contribs) (Created page with "{{Post mortem header |summary=Pterodactyl reported that it was failing to connect to any EDC game instance. |reporter=SierraKomodo |date-report=December 28, 2025 |date-resolved=December 28, 2025 (~15 minutes) |cause=Wings service was down. |resolution=Wings service restarted via <code>systemctl restart wings</code>.}} == Narrative == ''No narrative is available for this post mortem.")
11 December 2025
- 17:2217:22, 11 December 2025 December 2025: MediaWiki backup scripts not running due to wrong PHP CLI version (hist | edit) [2,953 bytes] Sirdog (talk | contribs) (Created page with "{{Post mortem header |summary=Backup scripts written by Sirdog for the Endurance Coalition wiki will not run as MediaWiki's maintenance script <code>dumpBackup.php</code> reports that PHP modules <code>xml</code>, <code>intl</code>, and <code>mbstring</code> are missing. |reporter=Sirdog |date-report=December 6, 2025 |date-resolved=Not yet resolved |cause=Unknown |resolution=Unknown}}") originally created as "December 2025: MediaWiki backup scripts not running due to missing PHP modules"
23 October 2025
- 18:4218:42, 23 October 2025 EnduraBot (hist | edit) [2,013 bytes] Sirdog (talk | contribs) (Created page with "'''EnduraBot''' is a general purpose Discord bot for the Endurance Coalition Discord server. As a general purpose bot, it serves a variety of functions, it's aim being to provide entertainment and solutions to things which automation would make easier. It is written in [https://discordpy.readthedocs.io/en/stable/ Discord.py], a [https://www.python.org/ Python] library for Discord bot development, and is open source on [https://github.com/sirdog9...") Tag: Visual edit: Switched
22 October 2025
- 17:1117:11, 22 October 2025 October 2025: Mordhau unreachable due to port assignment (hist | edit) [383 bytes] Sirdog (talk | contribs) (Created page with "{{Construction}} {{Post mortem header |summary=''Mordhau'' could not be joined despite being visible in the server list. |reporter=Fleff |date-report=October 22, 2025 |date-resolved=October 22, 2025 (~35 minutes) |cause=Server did not have desired port <code>15000</code>. |resolution=Port <code>15000</code> allocated to server.}}") Tag: Visual edit: Switched
6 October 2025
- 12:3812:38, 6 October 2025 October 2025: TF2 server would not start due to IPv6 (hist | edit) [4,407 bytes] Sirdog (talk | contribs) (Created page with "{{Sysop incident header|summary=The ''Team Fortress 2'' server after installation would not start.|reporter=N/A|date-report=September 6th, 2025|date-resolved=N/A|cause=N/A|resolution=N/A}} == Narrative == At the request of Dusty The Lion, with Fleff's approval, Sirdog attempted to install ''Team Fortress 2'' as an available server. During installation, the following errors appeared:<syntaxhighlight lang="bash"> [Pterodactyl Daemon]: Checking server disk space usage, thi...") Tag: Visual edit originally created as "September 2025: TF2 server will not start"
- 03:4403:44, 6 October 2025 Pterodactyl access (hist | edit) [1,445 bytes] Sirdog (talk | contribs) (Created page with "For some reason, Pterodactyl does not provide an interface for easily seeing what users have access to what services. {| class="wikitable" |+ !User !''Arma 3'' !''TeamSpeak 3'' !''Vintage Story'' !''FoundryVTT'' !''Abiotic Factor'' |- |Fleff | colspan="5" |21x21px |- |Sirdog | colspan="5" |21x21px |- |SierraKomodo | colspan="5" |21x21px |- |Sushiloid | colspan="5" |File:Star...") Tag: Visual edit
5 October 2025
- 22:4222:42, 5 October 2025 Creating servers in Pterodactyl (hist | edit) [7,867 bytes] Sirdog (talk | contribs) (Created page with "{{Construction}} Category:Systems management")
- 22:0222:02, 5 October 2025 September 2025: Web services go down due to Caddy update (hist | edit) [973 bytes] Sirdog (talk | contribs) (Created page with "{{Sysop incident header|summary=Web services become unresponsive.|reporter=N/A|date-report=September 26th, 2025|date-resolved=September 26th, 2025 (~30 minutes)|cause=Caddy was reinstalled using it's generic package.|resolution=Custom Caddy binary re-installed.}} == Narrative == SierraKomodo, while attempting to resolve September 2025: Arma server becomes unresponsive, saw that there were 50 upgradeable packages on the machine. She then ran the update command with e...") Tag: Visual edit originally created as "September 2025: Web services go down temporarily"
- 19:1319:13, 5 October 2025 September 2025: Arma server unresponsive due to egg update (hist | edit) [1,395 bytes] Sirdog (talk | contribs) (Created page with "{{Sysop incident header|summary=''Arma 3'' server becomes unresponsive.|reporter=BBM_Ping|date-report=September 26th, 2025|date-resolved=October 2nd, 2025 (6 days)|cause=Pterodactyl egg for ''Arma 3'' updated by creator.|resolution=Egg updated, Arma 3 reinstalled with new egg, server periodically rebooted until functional.}} == Narrative == On September 26th, 2025 BBM_Ping pinged <code>@SYS:OP</code> reporting that the ''Arma 3'' server was broken, citing the egg as out...") Tag: Visual edit originally created as "2025-09-26:Arma server becomes unresponsive"
- 18:1218:12, 5 October 2025 August 2025: SteamCMD servers unresponsive due to IPv6 (hist | edit) [2,072 bytes] Sirdog (talk | contribs) (Created page with " Category:Sysop events") originally created as "2025-08-14: Arma server unresponsive"
27 August 2025
- 12:4412:44, 27 August 2025 Land navigation (hist | edit) [1,060 bytes] Sirdog (talk | contribs) (Create certification page with basic structure) Tag: Visual edit: Switched