January 2026: Caddy unresponsive due to port conflict: Difference between revisions
Jump to navigation
Jump to search
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 ==..." |
No edit summary |
||
| Line 3: | Line 3: | ||
|date-report=January 27, 2026 | |date-report=January 27, 2026 | ||
|date-resolved=January 27, 2026 (~5 minutes) | |date-resolved=January 27, 2026 (~5 minutes) | ||
|cause=<code>apache2</code> was | |cause=<code>apache2</code> was re-enabled unintentionally during attempted resolution of unrelated problem, resulting in both it and <code>caddy</code> attempting to send traffic on port 80. | ||
|resolution=<code>apache2</code> disabled via <code>sudo systemctl disable apache2</code>.}} | |resolution=<code>apache2</code> disabled via <code>sudo systemctl disable apache2</code>.}} | ||
== Narrative == | == Narrative == | ||
''No narrative is available for this post-mortem.'' | ''No narrative is available for this post-mortem.'' | ||
Latest revision as of 15:31, 27 January 2026
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 re-enabled unintentionally during attempted resolution of unrelated problem, resulting in both it and caddy attempting to send traffic on port 80.
Resolution: apache2 disabled via sudo systemctl disable apache2.Narrative
No narrative is available for this post-mortem.