• [6.8.0-rc3] Can't enter the Adguardhome docker webpage if vm is on


    xxsxx47
    • Closed Minor

    Hi There

    I can't enter the Adguardhome docker webpage if vm on and even tho the docker page it says it working it doesn't the network doesn't work but if turn the vm off everything is working , is because of the Network type br0 ?

    tower-diagnostics-20191018-1409.zip




    User Feedback

    Recommended Comments

    Error starting userland proxy: listen tcp 0.0.0.0:53: bind: address already in use"

    This is the reason it won't start.  Port 53 is already in use.

    • Like 1
    Link to comment
    15 minutes ago, Squid said:
    
    Error starting userland proxy: listen tcp 0.0.0.0:53: bind: address already in use"

    This is the reason it won't start.  Port 53 is already in use.

    but it works if the vm down and maybe the error appeared because i changed the network type to bridge and that error appeared in the diagnoses file

    Edited by xxsxx47
    adding another thing
    Link to comment

    I have the same issue. The docker works fine until I start the VM. After that the web page is not accessible and I can't even ping it. I have to stop the VM and then the docker start working again and responding to pings. Docker is configured to use Custom : br0 with a unique IP and the VM is using a different fixed IP.

    Before updating to 6.8.0 -rcX was working fine.

    unraid-diagnostics-20191019-0131.zip

    Edited by thomas
    Link to comment

    Same here with PiHole when VM is on too. Webpage is unaccesible until I shutdown any VM that is running.

    Not even able to ping the IP of pihole docker.

    Edit: Just noticed that after 30 seconds i disabled Wireguard plugin everything started to work. Can someone confirm same behaviour?

    Edited by Nephilgrim
    • Like 1
    Link to comment
    1 hour ago, Nephilgrim said:

    Same here with PiHole when VM is on too. Webpage is unaccesible until I shutdown any VM that is running.

    Not even able to ping the IP of pihole docker.

    Edit: Just noticed that after 30 seconds i disabled Wireguard plugin everything started to work. Can someone confirm same behaviour?

    Indeed, if you stop the wireguard you can access the webpage of the Adguard docker.

    Link to comment

    After more testing it seems the option "Local gateway uses NAT: Yes" is the problem. If you choose "No" the docker works properly and it seems that I can still connect through Wireguard to my server

    • Like 1
    • Thanks 1
    Link to comment

    Indeed, disabling NAT option (and because of this: upnp too) fixes the issue for any docker in bridge mode.

    Edited by Nephilgrim
    • Thanks 1
    Link to comment

    can confirm that disabling the wireguard i can access the adguard webpage

    or just leave the wireguard on and turn off the "Local gateway uses NAT"

     

    Thank you very much every thing is working .

    • Like 1
    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.