Unable to fully access AgentDVR UI through cloud server and Traefik

[black-fake]

Description

I am running AgentDVR on my homelab and have set up a cloud server with Traefik to make the service accessible through a domain. The cloud server is connected to the homelab via a mesh VPN. The UI loads and prompts for login, but after logging in, it gets stuck on the loading screen with a message to try another browser. This occurs regardless of the browser used.

Dev Console Error

The developer console indicates an ICE connection failure. My research suggests this is due to port 3478 not being correctly accessible. I'm unable to establish a UDP connection to port 3478 on the original host.

Steps to Reproduce

1. Set up AgentDVR on a homelab server.
2. Use a cloud server with Traefik, connected via Tailscale, to access AgentDVR through a domain.
3. Attempt to log in to the AgentDVR UI.

Expected Behavior

After logging in, the AgentDVR UI should load successfully.

Actual Behavior

The UI remains stuck on the loading screen with a message to try another browser.

Additional Information

• The issue persists across different browsers.
• The suspected cause is the inaccessibility of port 3478 for UDP connections.
• Cloud server and homelab are connected via Tailscale (mesh VPN).
• Traefik is used as reverse proxy and it's the only way routed to the service.

Any assistance in resolving this issue would be greatly appreciated.

[vasquezmi]

I wanted to inquire if you ever got this fixed.
I had the same issue and I am working through it now.
You can modify the config.xml file which is located in \AgentDVR\Media\XML and update the TURN SERVER value.
I am using 53478.
If you are using any Unifi products or others that use adoption for APs this could be causing your issue or another web service that is on the same network segment.

[duncanch89]

I have a similar issue, going back to version 5.7.3.0 is my solution for now

[black-fake]

Update on the Issue
I've tried to look into this again and figured out that part of my issue was actually an interference of two authentications:

• Basic authentication on my proxy
• Integrated user authentication of AgentDVR

Removing the basic authentication from the proxy and keeping the integrated authentication allowed everything to work as expected. If I had done the opposite, keeping the basic authentication and removing the integrated authentication, the issue would have persisted. Fortunately, removing the basic authentication was the solution, and it worked smoothly.

Additional Notes
I also noticed that the message prompting me to use a different browser has disappeared. It's likely that this was fixed by someone responsible for the software, and I appreciate their efforts in resolving this issue. Thank you for your time and assistance.