January 2026: Caddy unresponsive due to port conflict

From Endurance Coalition
Revision as of 14:30, 27 January 2026 by 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 ==...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Summary: Upon reboot of the entire EDC host, caddy would not start, resulting in all web services being down.

Reported by: SierraKomodo

Date Reported: January 27, 2026

Date Resolved: January 27, 2026 (~5 minutes)

Root Cause: apache2 was renabled, resulting in it and caddy both attempting to send traffic on port 80.

Resolution: apache2 disabled via sudo systemctl disable apache2.

Narrative

No narrative is available for this post-mortem.

Retrieved from "https://wiki.edcgaming.org/index.php?title=January_2026:_Caddy_unresponsive_due_to_port_conflict&oldid=3265"