[Bug] AdGuard Home Crashes Immediately Due to Port Conflict with CasaOS #738
Description
Summary:
AdGuard Home, when installed from the CasaOS App Store, fails immediately after setup if CasaOS is using port 80 — which it usually is. This creates a silent conflict where AdGuard can't bind to port 80, crashes or exits silently, and provides no warning or fallback.
Steps to Reproduce:
Fresh install of CasaOS
Go to App Store → Install AdGuard Home
Proceed through the setup wizard
As soon as AdGuard launches, it exits/crashes
Expected Behavior:
CasaOS should detect port 80 is in use and either:
Suggest an alternate port (e.g., 8080)
Automatically configure AdGuard to bind to an unused port
Warn the user clearly in the App description or setup wizard
Actual Behavior:
AdGuard attempts to bind to port 80, fails silently, and the UI breaks
Users are left confused and may assume AdGuard is broken
No warning is given during install, and no CasaOS-level port conflict management occurs
Suggested Fixes:
Preconfigure the App Store version of AdGuard Home to bind to port 8080 by default
Add a UI warning when adding any app that requests port 80 or 53 if they are already in use
Add a “Port Conflict Checker” to the App Store for all apps that bind externally
Or allow custom port mapping during install (like Portainer does)
Why This Matters:
AdGuard is the second app listed in the App Store, yet conflicts with CasaOS’s own default port. This causes unnecessary frustration and undermines confidence in the system for new users.
Environment Info:
CasaOS version: v0.4.15
AdGuard Home version: v0.107.55
OS: Ubuntu Server 24.04 (bare-metal)
Docker backend