Solved Ubiquiti STUN Communication
-
Recently I have seen the STUN Communication error on my Unifi controller. I have read the documentation on this:
https://help.ubnt.com/hc/en-us/articles/115015457668-UniFi-Troubleshooting-STUN-Communication-Errors
Made sure the UDP port 3478 on Vultr allowed:
Yet the AP are showing not communication on it
So I am wondering if you have seen this issue before.
-
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@mike-davis said in Ubiquiti STUN Communication:
I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.
So you didn't open any of those ports I listed?
You do not normally need them.
What don't you normally need them? 8080 and 8443 at a minimum correct?
Correct.
But I opened the 8880 and 8843 for HTTP and HTTPS for Guest Hotspot portal. Usually not needed for others but in this case it was needed.
https://help.ubnt.com/hc/en-us/articles/115000871247-UniFi-Social-Media-Guest-Authentication#controller setupWith regards to STUN though, you believe is not needed then?
Should not be as your controller is not behind NAT. There is not point to STUN unless NAT is involved.
https://en.wikipedia.org/wiki/STUN -
Yes I have, and a reboot typically fixes it.
-
@dashrender said in Ubiquiti STUN Communication:
Yes I have, and a reboot typically fixes it.
I have already done that multiple times for all he APs and the Unifi Controller.
-
I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.
-
@mike-davis said in Ubiquiti STUN Communication:
I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.
So you didn't open any of those ports I listed?
-
@mike-davis said in Ubiquiti STUN Communication:
I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.
Did you enable the Vultr Firewall?
Did you adjust the Debian/Ubuntu Firewall to allow the traffic?
Way too much not said here.
-
@dbeato said in Ubiquiti STUN Communication:
@mike-davis said in Ubiquiti STUN Communication:
I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.
So you didn't open any of those ports I listed?
You do not normally need them.
-
@jaredbusch said in Ubiquiti STUN Communication:
@mike-davis said in Ubiquiti STUN Communication:
I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.
Did you enable the Vultr Firewall?
Did you adjust the Debian/Ubuntu Firewall to allow the traffic?
Way too much not said here.
Yes, Vultr Firewall is enabled and Debian Firewall is adjusted. What are you missing?
-
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@mike-davis said in Ubiquiti STUN Communication:
I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.
So you didn't open any of those ports I listed?
You do not normally need them.
What don't you normally need them? 8080 and 8443 at a minimum correct?
-
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@mike-davis said in Ubiquiti STUN Communication:
I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.
So you didn't open any of those ports I listed?
You do not normally need them.
What don't you normally need them? 8080 and 8443 at a minimum correct?
Correct.
-
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@mike-davis said in Ubiquiti STUN Communication:
I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.
So you didn't open any of those ports I listed?
You do not normally need them.
What don't you normally need them? 8080 and 8443 at a minimum correct?
Correct.
But I opened the 8880 and 8843 for HTTP and HTTPS for Guest Hotspot portal. Usually not needed for others but in this case it was needed.
https://help.ubnt.com/hc/en-us/articles/115000871247-UniFi-Social-Media-Guest-Authentication#controller setupWith regards to STUN though, you believe is not needed then?
-
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@mike-davis said in Ubiquiti STUN Communication:
I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.
So you didn't open any of those ports I listed?
You do not normally need them.
What don't you normally need them? 8080 and 8443 at a minimum correct?
Correct.
But I opened the 8880 and 8843 for HTTP and HTTPS for Guest Hotspot portal. Usually not needed for others but in this case it was needed.
https://help.ubnt.com/hc/en-us/articles/115000871247-UniFi-Social-Media-Guest-Authentication#controller setupWith regards to STUN though, you believe is not needed then?
Should not be as your controller is not behind NAT. There is not point to STUN unless NAT is involved.
https://en.wikipedia.org/wiki/STUN -
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@mike-davis said in Ubiquiti STUN Communication:
I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.
So you didn't open any of those ports I listed?
You do not normally need them.
What don't you normally need them? 8080 and 8443 at a minimum correct?
Correct.
But I opened the 8880 and 8843 for HTTP and HTTPS for Guest Hotspot portal. Usually not needed for others but in this case it was needed.
https://help.ubnt.com/hc/en-us/articles/115000871247-UniFi-Social-Media-Guest-Authentication#controller setupWith regards to STUN though, you believe is not needed then?
Should not be as your controller is not behind NAT. There is not point to STUN unless NAT is involved.
https://en.wikipedia.org/wiki/STUNSo that's the way I am going to approach it.
-
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@mike-davis said in Ubiquiti STUN Communication:
I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.
So you didn't open any of those ports I listed?
You do not normally need them.
What don't you normally need them? 8080 and 8443 at a minimum correct?
Correct.
But I opened the 8880 and 8843 for HTTP and HTTPS for Guest Hotspot portal. Usually not needed for others but in this case it was needed.
https://help.ubnt.com/hc/en-us/articles/115000871247-UniFi-Social-Media-Guest-Authentication#controller setupWith regards to STUN though, you believe is not needed then?
Should not be as your controller is not behind NAT. There is not point to STUN unless NAT is involved.
https://en.wikipedia.org/wiki/STUNHow can it mark your post as the solution?
-
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@mike-davis said in Ubiquiti STUN Communication:
I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.
So you didn't open any of those ports I listed?
You do not normally need them.
What don't you normally need them? 8080 and 8443 at a minimum correct?
Correct.
But I opened the 8880 and 8843 for HTTP and HTTPS for Guest Hotspot portal. Usually not needed for others but in this case it was needed.
https://help.ubnt.com/hc/en-us/articles/115000871247-UniFi-Social-Media-Guest-Authentication#controller setupWith regards to STUN though, you believe is not needed then?
Should not be as your controller is not behind NAT. There is not point to STUN unless NAT is involved.
https://en.wikipedia.org/wiki/STUNHow can it mark your post as the solution?
Tell @scottalanmiller to do it because that is a glaring whole in this plugin. Has been reported, but unactioned for years now.
-
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@jaredbusch said in Ubiquiti STUN Communication:
@dbeato said in Ubiquiti STUN Communication:
@mike-davis said in Ubiquiti STUN Communication:
I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.
So you didn't open any of those ports I listed?
You do not normally need them.
What don't you normally need them? 8080 and 8443 at a minimum correct?
Correct.
But I opened the 8880 and 8843 for HTTP and HTTPS for Guest Hotspot portal. Usually not needed for others but in this case it was needed.
https://help.ubnt.com/hc/en-us/articles/115000871247-UniFi-Social-Media-Guest-Authentication#controller setupWith regards to STUN though, you believe is not needed then?
Should not be as your controller is not behind NAT. There is not point to STUN unless NAT is involved.
https://en.wikipedia.org/wiki/STUNHow can it mark your post as the solution?
Tell @scottalanmiller to do it because that is a glaring whole in this plugin. Has been reported, but unactioned for years now.
Hey @scottalanmiller can you mark Jared's post with Wikipedia on it for the solution. I cannot for the life of me mark it as a solution.
