[Docker] AGH wizard interface cannot open on custom ports although container running #1900

New issue

Closed

opened 2026-03-04 01:37:31 -05:00 by deekerman · 1 comment

deekerman commented

2026-03-04 01:37:31 -05:00

Owner

Originally created by @ghost on GitHub (Aug 25, 2020).

I cannot use port 3000 (it used by another instance) so i'm trying to use port like 3005, 3058. it doesn't work (connection refused).

docker run --name adguardhome -v /my/own/workdir:/opt/adguardhome/work -v /my/own/confdir:/opt/adguardhome/conf -p 53:53/tcp -p 53:53/udp -p 67:67/udp -p 68:68/tcp -p 68:68/udp -p 4050:4050/tcp -p 443:443/tcp -p 853:853/tcp -p 3005:3005/tcp -d adguard/adguardhome:edge

That works if i replace 3005 with default 3000
After completed wizard and restart instance, why docker ps -a still shows 80/tcp (note: if ran with port 4050(instead 80) and 3000) (80, 3000 ports written in dockerfile, it might be the reason)

Expected Behavior

Works for any port.

Actual Behavior

Doesn't work and only support for port 3000

Originally created by @ghost on GitHub (Aug 25, 2020). I cannot use port 3000 (it used by another instance) so i'm trying to use port like 3005, 3058. it doesn't work (connection refused). `docker run --name adguardhome -v /my/own/workdir:/opt/adguardhome/work -v /my/own/confdir:/opt/adguardhome/conf -p 53:53/tcp -p 53:53/udp -p 67:67/udp -p 68:68/tcp -p 68:68/udp -p 4050:4050/tcp -p 443:443/tcp -p 853:853/tcp -p 3005:3005/tcp -d adguard/adguardhome:edge` 1. That works if i replace 3005 with default 3000 2. After completed wizard and restart instance, why docker ps -a still shows `80/tcp` (note: if ran with port 4050(instead 80) and 3000) (80, 3000 ports written in dockerfile, it might be the reason) ### Expected Behavior Works for any port. ### Actual Behavior Doesn't work and only support for port 3000

deekerman closed this issue

2026-03-04 01:37:33 -05:00

deekerman commented

2026-03-04 01:37:35 -05:00

Author

Owner

@ameshkov commented on GitHub (Aug 28, 2020):

Docker file has nothing to do with this.

You see, exposed ports just signal about which ports you can map and make available on your host machine, but there's no way we can restrict anything from inside the docker file.

That works if i replace 3005 with default 3000

Maybe it's occupied on your host machine?

@ameshkov commented on GitHub (Aug 28, 2020): Docker file has nothing to do with this. You see, exposed ports just signal about which ports you can map and make available on your host machine, but there's no way we can restrict anything from inside the docker file. > That works if i replace 3005 with default 3000 Maybe it's occupied on your host machine?

deekerman referenced this issue

2026-03-04 02:10:23 -05:00

Inability to search the query log by type and protocol #2640

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/AdGuardHome#1900

No description provided.

Rows
Columns