Need help getting Unifi Controller widget to work - API Error

[Tyree]

I feel like I'm missing something simple here and I hope one of you smart folks can point it out.

Running homepage on unRAID in a docker network.
Unifi Controller is also on unRAID docker, but on br0 with its own IP.
I also have the Unifi Controller container connected to the same docker network as homepage.

Trying to set up the widget, I'm getting this:

API Error: Unknown error
URL: https://192.168.75.13:8443/api/stat/sites
Raw Error:
{
    "errno": -113,
    "code": "EHOSTUNREACH",
    "syscall": "connect",
    "address": "192.168.75.13",
    "port": 8443
}

Says host unreachable. But that is definitely the correct IP and port.

My first thought is homepage can't communicate to the container on the br0 network, which is why I also joined the controller to the container network. Still no luck, though.

Any help is appreciated!
Thanks!

[jwfox5150]

This is due to unRAID's default network security settings. I ran into the same thing. unRAID does not allow bridged docker containers to access br0 networked containers. Your best option is to also put homepage on br0, so it can see other containers on the br0 network. Note that THIS will break connectivity to your unRAID IP (again, for security), so you'd need every container homepage is trying to access also on the br0 network and not in bridge mode.

[Tyree]

Right. I figured that's what was causing my issue. So, what I did was set a host override alias on the pfSense DNS Resolver, then pointed homepage to that and let that loop back to my SWAG unRAID container which then points to Unifi. A few jumps, but this seems to make homepage happy and now I can see the Unifi widget properly.
Thanks!

[jwfox5150]

Mind sharing your config? I'm in the middle of setting mine up and this seems like it would be the best solution for my usecase.

[Tyree]

The homepage config? It's pretty much exactly like the docs, but I used the host alias (https://unifi.domain.net) instead of the IP for the docker container (192.168.75.13).

widget:
            type: unifi
            url: https://unifi.domain.net
            username: email addy 
            password: *********

https://unifi.domain.net -- or whatever you set up that SWAG is looking for -- is an alias for my local unRAID server hostname (unraid.tyree.local), which just points to the unRAID server IP.

I have all my reverse-proxied hostnames set up as aliases for my unRAID server on my local DNS Resolver (pfSense) so that when I request a site, it doesn't have to go out to the net and come back for no reason.
If you're using SWAG, Traefik, NPM, or any other reverse proxy, you can then set that up to listen on port 443 so that you don't have to specify ports on your url. It'll grab the incoming request and route it to the actual IP:Port of the Unifi container.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.