October 14, 20232 yr Hi, On my old server/network setup I had a VM with Home Assistant running Frigate NVR Proxy addon connecting to another separate server that had Frigate and wyze-cam-bridge installed and I was able to view my IP cams in Home Assistant and was able to use the the addons for motion detection, automations, etc. I have been working today on moving all my old, slower desktop servers into one dual CPU desktop and I have the VM running with Home Assistant perfect and even using the same IP address as before but now when attempting to view my cameras in Frigate NVR; I get nothing but a blank screen and no errors in the logs. The cameras (frigate and the bridge) are working correctly because if I go into the webui for those containers; I can see everything but the NVR proxy app that is meant to connect the two in HA won't work; and I feel it us due to the VM not being able to communicate with the docker container but i'm not sure why or how to fix this. I have tried putting in my server IP address/port that is assigned to the docker container as well as trying the docker 172.x.x.x ip address but neither will work. Can someone please help me? Is there somewhere I need to enable something for these two to talk to each other; or because they are now on the same server this is not possible?
October 14, 20232 yr Solution Have you enabled "host access to custom networks" in docker settings? Edit: I'd do it this way rather than enabling bridging in network setting. If you enable bridging unraid will use macvlan and probably start randomly crashing. By keeping bridging off and "host access to custom networks" on it should use macvtap and avoid the instability. Edited October 14, 20232 yr by L0k1
October 14, 20232 yr Author 1 hour ago, L0k1 said: Have you enabled "host access to custom networks" in docker settings? Edit: I'd do it this way rather than enabling bridging in network setting. If you enable bridging unraid will use macvlan and probably start randomly crashing. By keeping bridging off and "host access to custom networks" on it should use macvtap and avoid the instability. That was it; never knew that existed. I had myself to dead set focused on Network Settings being the answer. Enabled and everything is working great; thank you!
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.