October 21, 20178 yr Ensure you have the correct credentials that you set during the setup phase and that you don't have capslock on/off or numlock on/off whichever is appropriate to your chosen password,, and or clear browser cache / cookies etc. Spun up new instance of this image and set a password and logged in with no problems whatsoeverAlso, be aware that the user name is case sensitive. I went through several re-installs with the same login problem before realizing what was happening. Sent from my iPhone using Tapatalk
October 24, 20178 yr FYI - https://community.ubnt.com/t5/UniFi-Routing-Switching/NOTICE-Oracle-Java-8-update-151-and-the-UniFi-Controller/m-p/2110937#M62663
October 27, 20178 yr Is it possible to install a 5.6.X beta in this docker? I need some of the new features to setup my network properly. FYI My instance is discovering hardware also only in Host mode.
October 27, 20178 yr Is it possible to install a 5.6.X beta in this docker? I need some of the new features to setup my network properly. FYI My instance is discovering hardware also only in Host mode.Stable 5.6.19 went out yesterday. Repo is Monday so should be here next Friday for this docker Sent from my iPhone using Tapatalk
October 27, 20178 yr Jeah thats great, is there a way to perform the update right away? e.g. via dpkg directly on the container? I already replaced my whole network with unifi equipment and need to place some custom DNS entries and NAT rules.
October 27, 20178 yr https://community.ubnt.com/t5/UniFi-Updates-Blog/UniFi-5-6-19-Stable-has-been-released/ba-p/2109621 mayor changes https://community.ubnt.com/t5/UniFi-Updates-Blog/UniFi-5-6-16-Stable-Candidate-has-been-released/ba-p/2056618 https://community.ubnt.com/t5/UniFi-Updates-Blog/UniFi-5-6-18-Stable-Candidate-has-been-released/ba-p/2081597 New Feaures Add AirView for UAP-SHD. Add AirTime for UAP-SHD. Add Switch Port Profiles. Add RADIUS-based authorization in Hotspot. Add new type of map with predictive coverage. Add Ubiquiti store (buy devices directly from the controller). Add EDU SIP settings. Add Facebook Wi-Fi Authentication (Beta). Add DPI blocking per categories. Add LLDP-MED configuration. Allow configure 8 SSIDs per radio (on supported devices). Add Insights / Controller Logs page. Add USG Performance Graphs. Add temperatures to USG-Pro properties window. Add LAN traffic statistics for client in Property Panel. Add Debug Dashboard to Statistics section. Batch add and remove device tags. Add permissions options when inviting a site admin (device adoption, etc.). Add Outdoor / Indoor Switch. Add NTP server fields. Add batch device provision. Add DB migration page and show upgrade progress. Add date header to email notifications. Install and run service as `unifi` user instead of as root on Debian/Ubuntu. Add Logging settings. Add batch edit switches. Add UPnP service (moved from config.properties). Add Multicast DNS Service (moved from config.properties). Add RADIUS MAC Authentication. Add Firmware Manager to cache locally firmwares.
October 27, 20178 yr Thanks - The post I had showed the release notes for all the 5.6.x releases which was a very hard read
November 6, 20178 yr 5 minutes ago, boxland said: I tried to update but the docker is still on 5.5.24. At the time of this post 5.5.24 is the latest stable version 5.6x is not a stable release at this time and we won't be switching to it until it is. 5.6.20 is "allegedly" due for stable release today. https://community.ubnt.com/t5/UniFi-Updates-Blog/UniFi-5-6-x-Release-Schedule-Update/ba-p/2116513
November 6, 20178 yr Update on 5.6.20 stable release It will be available on unifi download link and repo on the 11th of november, providing this schedule is maintained we will make provisions to update at that time https://community.ubnt.com/t5/UniFi-Updates-Blog/UniFi-5-6-20-Stable-has-been-released/ba-p/2119397
November 8, 20178 yr On 11/6/2017 at 4:05 AM, sparklyballs said: At the time of this post 5.5.24 is the latest stable version 5.6x is not a stable release at this time and we won't be switching to it until it is. 5.6.20 is "allegedly" due for stable release today. https://community.ubnt.com/t5/UniFi-Updates-Blog/UniFi-5-6-x-Release-Schedule-Update/ba-p/2116513 Nice to see the update! I was coming to ask a question if there was a way for the user to update things themselves like to any of the betas?
November 8, 20178 yr Nice to see the update! I was coming to ask a question if there was a way for the user to update things themselves like to any of the betas?What I had to was download a backup then installed brettm357 unifi docker and imported. I’ll switch back to this one once stable repo is out. Sent from my iPhone using Tapatalk
November 10, 20178 yr According to this post yesterday, 5.6.22 is the latest stable release. https://community.ubnt.com/t5/UniFi-Updates-Blog/UniFi-5-6-22-Stable-has-been-released/ba-p/2131913 It looks there have been a few "stable" 5.6.x releases in the last couple of weeks to fix several bugs. Maybe 5.6.xx is not so "stable." I also ran across this tantalizing post by a UBNT employee in a blog: "We're making USG's DNS much more configurable in 5.7.x controller, so you'll be seeing some improvements there soon to greatly expand its UI-configurable capabilities." Bring on the "greatly-expanded UI-configurable capabilities." I am not sure if that refers solely to DNS configuration or other features as well. So, now, they have some pining for the 5.7.x controller as well.
November 13, 20178 yr Anyone getting "STUN Communication Failed" on their devices since upgrading from 5.5.x to 5.6.x? I have port 3478 mapped in my docker but that doesn't seem to solve the issue. Edited November 13, 20178 yr by IamSpartacus
November 13, 20178 yr 3 hours ago, IamSpartacus said: Anyone getting "STUN Communication Failed" on their devices since upgrading from 5.5.x to 5.6.x? I was just on my usg and fix it. Is this a local site or remote site having issue? My issue was only on the usg and local site. I use a unifi.domain.com and had "Override inform host with controller hostname/IP" check and I guess the the local usg did not resolve unifi.domain.com, but yet my switches and APs had no issue. If it's a remote site make sure you are passing port 3478 udp. also is this docker up to 5.6 yet? ____________________________________________________ I just switch back to this docker and it's updated to 5.6.22 **********UPDATE********** For Stun issue this docker template does not have the port neededs Port 3478. Also for speedtest for mobile apps Port 6789 needs pass. You can add these your self, Maybe add them to the template later? Edited November 13, 20178 yr by H2O_King89
November 13, 20178 yr 13 hours ago, H2O_King89 said: I was just on my usg and fix it. Is this a local site or remote site having issue? My issue was only on the usg and local site. I use a unifi.domain.com and had "Override inform host with controller hostname/IP" check and I guess the the local usg did not resolve unifi.domain.com, but yet my switches and APs had no issue. If it's a remote site make sure you are passing port 3478 udp. also is this docker up to 5.6 yet? ____________________________________________________ I just switch back to this docker and it's updated to 5.6.22 **********UPDATE********** For Stun issue this docker template does not have the port neededs Port 3478. Also for speedtest for mobile apps Port 6789 needs pass. You can add these your self, Maybe add them to the template later? My docker is on 5.6.22. I don't have a USG only a UniFi switch and 2 AP's. I have mapped port 3478 in the docker config but no dice.
November 13, 20178 yr My docker is on 5.6.22. I don't have a USG only a UniFi switch and 2 AP's. I have mapped port 3478 in the docker config but no dice.Is it map udp? Maybe try port forwarding 3478 udp on the firewall to the controller? They have a few topics about this on the unifi forums Sent from my iPhone using Tapatalk
November 13, 20178 yr I added 3478 on the container and the STUN error has gone. But when I start the unifi webgui I get 2 websocket connection errors. This was before and after the port mapping.
November 13, 20178 yr I added 3478 on the container and the STUN error has gone. But when I start the unifi webgui I get 2 websocket connection errors. This was before and after the port mapping. Tried clearing browser cache? Could try backup unifi then nuke the docker and appdata and rebuild. I moved over from another docker with no issue. Sent from my iPhone using Tapatalk
November 13, 20178 yr 1 hour ago, H2O_King89 said: Is it map udp? Maybe try port forwarding 3478 udp on the firewall to the controller? They have a few topics about this on the unifi forums Sent from my iPhone using Tapatalk How you specifically map a port as UDP/TCP? I can't do any port forwarding on the controller because I don't have USG.
November 13, 20178 yr How you specifically map a port as UDP/TCP? I can't do any port forwarding on the controller because I don't have USG. Port forward on your router “don’t know if this is needed but wouldn’t hurt” Sent from my iPhone using Tapatalk
November 13, 20178 yr 2 minutes ago, H2O_King89 said: Port forward on your router “don’t know if this is needed but wouldn’t hurt” Sent from my iPhone using Tapatalk Oh I see. I'm not actually running this docker on my UnRAID server but instead on a Linux Ubuntu 16.04 server so I just use docker create and map the ports like so: Quote -p 3478:3478 \ On a related note though, this STUN communication happens between an external source (UniFi's servers?) and my local controller? If so I do not want that at all.
November 13, 20178 yr On a related note though, this STUN communication happens between an external source (UniFi's servers?) and my local controller? If so I do not want that at all.It’s for your unifi Devices to talk to your unifi controller to get the public IP. Do you have in settings> controller>host name over ride check? That will mess up the stun address if not set right. Best to leave uncheck and Re-provision. I have the port open on my router because I host for other unifi sites Sent from my iPhone using Tapatalk
Archived
This topic is now archived and is closed to further replies.