Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AdGuard Home port 80 not working using nspawn container #591

Open
benjaminprojas opened this issue Jan 30, 2024 · 2 comments
Open

AdGuard Home port 80 not working using nspawn container #591

benjaminprojas opened this issue Jan 30, 2024 · 2 comments

Comments

@benjaminprojas
Copy link

Describe the bug
I've followed the very detailed instructions to create a custom container to use AdGuard Home on my UDM Pro from here: https://github.com/unifi-utilities/unifios-utilities/tree/main/nspawn-container

I've got everything working very well except for the fact that when I run the AdGuard install process, it won't let me choose port 80 as it's already in use. In fact when I go to Port 80 it redirects me to the login for the UDM pro.

I'd prefer to use port 80 for the AdGuard home setup, but am unsure on how to change this inside the UDM so it doesn't set up it's webserver on port 80 for the specific IP address I am using for AdGuard. Any thoughts or ideas on what I can do to fix this?

To Reproduce
Steps to reproduce the behavior:

  1. Follow steps here for simple networking: https://github.com/unifi-utilities/unifios-utilities/tree/main/nspawn-container
  2. Additionally, I combined some of the steps in the isolated VLAN section in order to give the AdGuard box an IP address.

Expected behavior
When I visit 192.168.2.4:80, I should see AdGuard Home, however it redirects to UDM Pro login screen.

Screenshots
image

I can get AdGuard Home working on any other port:
image

UDM Information

  • Variant: Dream Machine Pro
  • Firmware Version: 3.2.9
  • Controller Version: 8.0.28

Additional context
None

@FriendlyNGeeks
Copy link

so the host machine will not allow docker/podman to bind any port that is already in use ie controller uses port 80/443 for its UI

@EugenMayer
Copy link

I cannot reproduce this, working just fine for me on 3.x with nspawn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants