AdGuard Port issue

Posted by Amilo21

Can setup AdGuard Home and it works, just the Dashboard keeps pointing at 3053, though it remains on 3054, as default like the set up wizard. Also I still had to copy and paste the issue, though I can see there is a new Sparkbox update I'm missing, so maybe its already fixed From TomAI: AdGuard restarted cleanly 4 minutes ago. The ADGUARDPORT variable just isn't what controls the dashboard launcher link — that's hardcoded in the dashboard config for AdGuard's module, and it's pointing at 3053 (port 80 path) instead of 3054 (port 3000 path). This is genuinely a SparkBox bug that needs Tom to fix in the dashboard code. Nothing you can change in .env will move that launcher link. For now, just bookmark http://192.168.1.3:3054 directly — that's your AdGuard admin UI and it works fine. Hit Share to demox so Tom sees this — the AdGuard launcher needs to point at 3054 not 3053.

1 replies

tomspark wrote:

Good news — nothing's actually broken, and you don't need to wait on an update for this one. Here's what's going on: AdGuard has two doors. Port 3054 is the first-time setup wizard, and 3053 is the normal admin page. The dashboard launcher button is built to open the normal one (3053) — but during setup, AdGuard left its admin page on the wizard's port instead of moving it over, so the button points at a door that's empty. Two ways to sort it: Easy: just bookmark http://your-server-ip:3054 and use that — it's your working AdGuard, nothing wrong with it. To make the launcher button work: open a terminal and edit AdGuard's config: sudo nano /opt/sparkbox/modules/adguard/config/conf/AdGuardHome.yaml Near the top find the line that looks like 'address: 0.0.0.0:3000' (under 'http:') and change the 3000 to 80, save (Ctrl+O, Enter, Ctrl+X), then: sudo sparkbox restart adguard After that the launcher button opens AdGuard correctly. Either path is fine — the bookmark is totally legit if you'd rather not touch the config.