-
-
Notifications
You must be signed in to change notification settings - Fork 415
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
Comments
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 |
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
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:
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](https://private-user-images.githubusercontent.com/962530/300945958-c0cca4f3-90b0-4418-af67-6cdbc03a3011.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA2OTQ1NDQsIm5iZiI6MTcyMDY5NDI0NCwicGF0aCI6Ii85NjI1MzAvMzAwOTQ1OTU4LWMwY2NhNGYzLTkwYjAtNDQxOC1hZjY3LTZjZGJjMDNhMzAxMS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzExJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcxMVQxMDM3MjRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT02NDVkODczZmNiOWQ4OGNiNmVjMGUyY2M0YjdmZTVlMjgyOThhNDg2MzQ3YWE0YWRmMjZmZGUzZDc1NjU0YTIwJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.vbgxlHSS6FDZ98agYsK4FYmTAUIpRAblCV-9FJkvIsw)
I can get AdGuard Home working on any other port:
![image](https://private-user-images.githubusercontent.com/962530/300946688-5897b434-ad31-44eb-b1cd-5cf0c94716b7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA2OTQ1NDQsIm5iZiI6MTcyMDY5NDI0NCwicGF0aCI6Ii85NjI1MzAvMzAwOTQ2Njg4LTU4OTdiNDM0LWFkMzEtNDRlYi1iMWNkLTVjZjBjOTQ3MTZiNy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzExJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcxMVQxMDM3MjRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT01NmE2Y2RmY2E1ZjhiZjlhMzI2YmQ5MWNjNDY1ZjA2ZThmYWI2MzNiNzY0MTg2MzVlZTkyYTRiNGRiOWRlODQxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.zMOf0YszqVzMqAFBzUop3g1vFAf0mSvznezN3CzjBI0)
UDM Information
Additional context
None
The text was updated successfully, but these errors were encountered: