nric

Ok, found the answer: The VPN allowed IP range was set to local only (192.168.1.0/24). I set this because I didn't want to route all inter traffic though the VPN. However, AgnetDVR apparently need a few other connections. I don't know which, I tried to resolve the IP and add *.ispyconnect.com and *.azurewebsites.net but that was not enogh. However, it works for my purposes to have two VPN connections: One which routes all traffic (which is the default with WireguardEasy) for AgentDVR. And one for local only in all my other cases. Hope this helps someone. And if someone knows how to except the two specific websites, let me know Nric

Hi all, I'm not sure if this is more of a wireguard or a AgentDVR problem but I'm lost: Wireguard is working fine, I can connect to all my local resources (samba, webinterfaces, ect) except: AgentDVR which is important in my case. When I connect to it's webinterface 192.168.1.2:8090 I see the loading screen and then it says: "Try another browser or check firewall isn't blocking ports.". Obvisually, I tried different browsers but that doesn't change anything. Neither the log files of AgentDVR nor of WireGuard show anything when I fail to connect. Even more frustrating is, that it used to work fine and I don't even know what changed. On the AgentDVR site it says: "Can't connect?: In rare instances a connection may fail due to content filtering on a VPN connection. You'll need to add exceptions in your content filtering software for *.ispyconnect.com and *.azurewebsites.net". I don't know how and where to do this and I doubt it will solve the problem since it used to work just fine. Does anyone have any Idea what I could try? Kind regards, nric