03-09-2018 06:50 AM
@sanyo20 Did you try on a different computer on your network to see if it works? UBNT suggested also running the test on https://test.webrtc.org/ to see if you can connect that way to help eliminate potential issues with unopen ports etc.
Is this a machine at home or at a business? It's also possible that either your ISP or business are blocking certain ports.
If you haven't already I would recommend sending a support ticket to email@example.com and see if you can get direct help from UBNT.
Just a few thoughts.
03-09-2018 07:42 AM
@begunfx That is a great idea testing on a secondary computer. @sanyo20 I saw earlier you mentioned it not working on two separate computers after updating to the latest firmware. When you connect to the controller over the local IP does the controller timeout, or do functions that should be working outside of WebRTC also fail?
09-14-2018 09:45 AM
I was having the same problem as well in Chrome. When I tested in Firefox on the same computer, it worked. So there must be some plugin in Chrome that is causing it to fail.....
3 weeks ago
I had the same issue, there are two ways to resolve this, you can update Java and agree to the UniFi DB Server security prompts or update your firewall rules.
1. Updating to latest version of Java
2. Prompted to remove old version of Java - Removed old version(s)
3. Re-ran UniFi Controller
4. When Java Prompted, said yes to allow access to Private and Public
Open windows firewall - Advanced Security - inbound rules - allow "UniFi DB Server" UDP and TCP access:
This is my first post and first timer with Ubiquiti gear, so far I love the ecosystem.