NPM on macvlan Unreachable from Homepage - NPM & Homepage on Unraid

[Postman67]

Description

I've been having an issue with the NPM (NGINX Proxy Manager) erroring out. Both NPM & Homepage are running on the same Unraid machine in Docker containers. However, Homepage is utilizing a bridge while NPM is using a br0 on the same interface, therefore giving just NPM a different IP from Unraid.

Unraid + Homepage IP: 192.168.1.57
NPM IP: 192.168.1.81

It's possible that this could just be a flaw with my Unraid container network config, as my other Bridge containers also fail to curl NPM.

homepage version

v1.1.1

Installation method

Unraid

Configuration

- Services:
    - Unique Services:
        - NGINX Proxy Manager:
            icon: nginx-proxy-manager
            href: http://192.168.1.81:81/login
            description: NGINX Proxy Manager - WIDGET BROKEN
            widget:
                type: npm
                url: http://192.168.1.81:81
                username: {my-user}
                password: {my-pass}

Container Logs

[2025-04-05T07:50:19.001Z] error: Error calling http://192.168.1.81:81/api/tokens...
[2025-04-05T07:50:19.002Z] error: [
500,
Error: connect EHOSTUNREACH 192.168.1.81:81
at (Error: connect EHOSTUNREACH 192.168.1.81:81) {
errno: -113,
code: 'EHOSTUNREACH',
syscall: 'connect',
address: '192.168.1.81',
port: 81
}
]
[2025-04-05T07:50:19.003Z] error: Error 500 logging into npm {"error":{"message":"Unknown error","url":"http://192.168.1.81:81/api/tokens","rawError":[500,{"errno":-113,"code":"EHOSTUNREACH","syscall":"connect","address":"192.168.1.81","port":81}]}}

Browser Logs

http://192.168.1.57:3000/api/services/proxy?group=Unique+Services&service=NGINX+Proxy+Manager&index=0&endpoint=hosts 500 (Internal Server Error)

Troubleshooting

Top CLI is from the Homepage Container
Bottom CLI (Command Prompt) is from a Windows machine

All of them are on the same network 192.168.1.0/24

[shamoon]

Yea as you posted in the other thread and the error here / the tests confirm, this is a networking issue. If homepage can’t reach npm, the widget won’t work. I don’t know off the top of my head but I think you can’t add a docker container to multiple networks if it’s using macvlan (in general that’s the solution, make two containers share a network so they can ‘see’ each other).

Anyway the point is you will need to change something about your setup to make this work

[masterteel]

Hi, I just solved the same issue myself. I created a new bridge network and added that network to both my homepage container, as a second network and to my nginx as a second network. I then used the local IP from that new network on my nginx to finally get my widget working for the first time ever. I'm using macvlan to have nginx on a separate IP as well. Here's my config, I hope this helps anyone else like me that may come by this:

- Nginx Proxy:
    href: https://192.168.50.35/
    icon: si-nginxproxymanager-#F15833
    description: Proxy Manager for my domain
    ping: 192.168.50.35
    container: npm
    widget:
        type: npm
        url: http://172.22.0.2:81
        username: some_guy@gmail.com
        password: something_stupid_long

Cheers!