lrx345 Posted February 1, 2019 Share Posted February 1, 2019 5 minutes ago, Hoopster said: Yes, you should enable that. I guess I thought you already had it enabled so I referenced the other option. Sent from my iPhone using Tapatalk So the L2 setting doesn't seem to do much for me, but the "Override inform host with controller hostname/IP" does. Wish I knew why I suddenly need that setting. The only thing I've changed was adding a Unifi Switch instead of a dumb switch. Link to comment
Hoopster Posted February 1, 2019 Share Posted February 1, 2019 8 minutes ago, lrx345 said: So the L2 setting doesn't seem to do much for me, but the "Override inform host with controller hostname/IP" does. Wish I knew why I suddenly need that setting. The only thing I've changed was adding a Unifi Switch instead of a dumb switch. My network works fine with just L2 discovery, but, the override option is there because, sometimes, it is needed. My network is a USG, UniFi switches and UniFi access points and I have never needed the override, but, if it works for you, just set it and forget it. It certainly wont cause any harm. Link to comment
CorneliousJD Posted February 1, 2019 Share Posted February 1, 2019 19 hours ago, lrx345 said: This one? Sorry, maybe I didn't post what I thought I did, but I fixed it with this. The IP is my unraid IP. Before I put this checkbox in to override, it would re-adopt over and over. Link to comment
musicking Posted February 6, 2019 Share Posted February 6, 2019 Hey, Will 5.10.12 be the latest "unstable" release as it is now in stable build? I'm hoping to switch to the linux server docker from another docker image but I can't restore my backup until a build greater than 5.9.32 comes out. Thank you Link to comment
Hoopster Posted February 7, 2019 Share Posted February 7, 2019 37 minutes ago, musicking said: Will 5.10.12 be the latest "unstable" release as it is now in stable build? Not until it hits the official public download page. As long as it is only available through other means, it will not be the 'unstable' release. That is LSIO policy on both the 'latest' (currently LTS 5.6.40) and 'unstable' (currently 5.9.29) builds. Link to comment
musicking Posted February 7, 2019 Share Posted February 7, 2019 2 hours ago, Hoopster said: Not until it hits the official public download page. As long as it is only available through other means, it will not be the 'unstable' release. That is LSIO policy on both the 'latest' (currently LTS 5.6.40) and 'unstable' (currently 5.9.29) builds. Excellent, I don't think this will take long for them to make this release official Link to comment
Tyler Posted February 7, 2019 Share Posted February 7, 2019 4 hours ago, musicking said: Excellent, I don't think this will take long for them to make this release official If they follow their stated schedule it’ll take a week. Full details here, with the relevant part of the post in this case being... Quote One week from the time a release goes stable, it will be pushed to the download site, Debian/Ubuntu/Cloud Key repos, etc. Link to comment
dbknightx Posted February 7, 2019 Share Posted February 7, 2019 Hi guys, I have been using this docker container with 3 UAP-AC-LR access points for the past couple of years and have been EXTREMELY happy. I am about to venture into uncharted territory by adding a UAP-AC-M-US to my network in mesh mode (no hardwired ethernet) - this will be used in my back yard to extend my signal. My usual steps for adding a new access point are to plug it into a hardwired ethernet cable, ssh to the device, mca-cli, set-inform, etc. so it can show up in the controller. I was planning on doing those same steps for this new device to get it registered, and then unplug the hardwired ethernet permanently to move it to its final location outside. is there any problem with this approach? Is configuring it in a wired manner going to give me problems when I want to switch it to mesh mode? Thanks in advance for any advice. Much appreciated! -David Link to comment
Hoopster Posted February 7, 2019 Share Posted February 7, 2019 1 hour ago, dbknightx said: Hi guys, I have been using this docker container with 3 UAP-AC-LR access points for the past couple of years and have been EXTREMELY happy. I am about to venture into uncharted territory by adding a UAP-AC-M-US to my network in mesh mode (no hardwired ethernet) - this will be used in my back yard to extend my signal. My usual steps for adding a new access point are to plug it into a hardwired ethernet cable, ssh to the device, mca-cli, set-inform, etc. so it can show up in the controller. I was planning on doing those same steps for this new device to get it registered, and then unplug the hardwired ethernet permanently to move it to its final location outside. is there any problem with this approach? Is configuring it in a wired manner going to give me problems when I want to switch it to mesh mode? Thanks in advance for any advice. Much appreciated! -David My UAP-AC-LR and UAP-IW-ACs are all hardwired, but, I know they support wireless uplink (even though I have none configured that way). Reading the Ubiquiti blurb below leads me to believe that if one of your wired APs is configured for wireless uplink, other APs can connect to it for wireless adoption, etc. No need to hardwire it for adoption. It is going to need to be connected wirelessly anyway for operation in your network. "Wireless Uplink functionality enables wireless connectivity between APs for extended range. One wired UniFi AP uplink supports up to four wireless downlinks on a single operating band, allowing wireless adoption of devices in their default state and real-time changes to network topology. For devices that support Plug & Play Mesh, this functionality is extended to allow multi-hop wireless uplink – so wirelessly uplinked APs can support uplink to other wirelessly uplinked APs." Link to comment
dbknightx Posted February 7, 2019 Share Posted February 7, 2019 Thanks, Hoopster. I've enabled the "Allow meshing to another access point" check box for all of my UAP-AC-LR devices and will just try powering up the UAP-AC-M when I get it to see if that will be enough for it to show up in the controller for adoption. Will give it a shot when the new device arrives on Monday and give an update on how it works. Link to comment
jedimstr Posted February 9, 2019 Share Posted February 9, 2019 On 2/6/2019 at 7:03 PM, Hoopster said: Not until it hits the official public download page. As long as it is only available through other means, it will not be the 'unstable' release. That is LSIO policy on both the 'latest' (currently LTS 5.6.40) and 'unstable' (currently 5.9.29) builds. Well now that 5.10.12 is on the download page: https://www.ui.com/download/unifi/ I was expecting the latest "unstable" tag to get it, especially since I saw there was an update last night. But no, the Unstable tag does not have the fully released version yet. Can you guys push one out instead of waiting another week since it WAS on the download page before the latest Unstable tag was updated last night? Link to comment
ytwytw Posted February 9, 2019 Share Posted February 9, 2019 Hey guys I’m new to UnRAID and I just installed this UniFi controller docker on my unraid. it starts but I cannot get into setup wizard. Tried reinstall, change from bridge to host, change port, delete appdata and still no luck any ideas? I was using the same docker on my raspberry pi and all works okay Link to comment
skank Posted February 9, 2019 Share Posted February 9, 2019 Installed this one but when i click WebUI i get an error: This site is unreachable Port 8443 Its not used by another one Network type is bridge (should it be host?) Also whats the difference between the two anyway? When i do set the docker as host and when as bridge? I used the controller on my laptop till now, but now i want it on unraid Can i use my settings from laptop or do i have to start over? Once on unraid, can i switch back at laptop anytime or do i have to chose? Link to comment
Bydgoszcz Posted February 9, 2019 Share Posted February 9, 2019 I've been running into memory issues on my system and I couldn't figure out what was eating it. Today I updated the Unifi docker and my memory usage dropped by 35% so now I'm wondering if something within Unifi is slowly bloating until my system crashes. Any thoughts? What would I need to share for analysis? Link to comment
skank Posted February 9, 2019 Share Posted February 9, 2019 4 hours ago, ytwytw said: Hey guys I’m new to UnRAID and I just installed this UniFi controller docker on my unraid. it starts but I cannot get into setup wizard. Tried reinstall, change from bridge to host, change port, delete appdata and still no luck any ideas? I was using the same docker on my raspberry pi and all works okay i got the same problem Link to comment
H2O_King89 Posted February 9, 2019 Share Posted February 9, 2019 I run mine in host so there is no problem. Sent from my iPhone using Tapatalk Pro Link to comment
zimmertr Posted February 10, 2019 Share Posted February 10, 2019 (edited) So I've managed to get the Unifi Controller image working with an external database however the Unifi Controller never actually starts up. Using MongoDB 3.4.19. The Server.log stops adding entries after it connects to the database and the mongod.log is never created. [2019-02-10 18:37:32,771] <launcher> INFO system - *** Running for the first time, creating identity *** [2019-02-10 18:37:32,779] <launcher> INFO system - UUID: bf5e13cf-3c84-476b-aaa3-e9feb51ae995 [2019-02-10 18:37:32,820] <launcher> INFO system - ====================================================================== [2019-02-10 18:37:32,821] <launcher> INFO system - UniFi 5.6.40 (build atag_5.6.40_10370 - release) is started [2019-02-10 18:37:32,821] <launcher> INFO system - ====================================================================== [2019-02-10 18:37:32,828] <launcher> INFO system - BASE dir:/usr/lib/unifi [2019-02-10 18:37:32,848] <launcher> INFO system - Current System IP: 192.168.0.1 [2019-02-10 18:37:32,848] <launcher> INFO system - Hostname: unifi-controller-5bb95c7688-xj99j [2019-02-10 18:37:36,202] <launcher> INFO db - waiting for db connection... [2019-02-10 18:37:36,722] <launcher> INFO db - Connecting to mongodb://ubnt:PASSWORD@unifi-controller-mongodb:27017/unifi [2019-02-10 18:37:51,296] <launcher> INFO db - Connecting to mongodb://ubnt:PASSWORD@unifi-controller-mongodb:27017/unifi_stat [2019-02-10 18:37:54,295] <launcher> INFO webrtc - WebRTC library version: EvoStream Media Server (www.evostream.com) build v1.0.31 - Gladiator - (built for Debian-7.0.5-x86_64 on 2018-02-01T22:48:38.000) OpenSSL version: 1.0.2l usrsctp version: 6d79bcc19755bc08 compiled on machine: Linux debian-7-0-5-64 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u6 x86_64 GNU/Linux [2019-02-10 18:38:56,232] <autoupdate-check> INFO system - firmware[U7E] new version (3.8.17.6789) is available [2019-02-10 18:38:56,233] <autoupdate-check> INFO system - firmware[U7MP] new version (4.0.21.9965) is available [2019-02-10 18:38:56,233] <autoupdate-check> INFO system - firmware[U7SHD] new version (4.0.21.9965) is available [2019-02-10 18:38:56,233] <autoupdate-check> INFO system - firmware[US48] new version (4.0.21.9965) is available [2019-02-10 18:38:56,233] <autoupdate-check> INFO system - firmware[U7O] new version (3.8.17.6789) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[U7P] new version (4.0.15.9872) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[U7PG2] new version (4.0.21.9965) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[U7EDU] new version (4.0.21.9965) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[U7IW] new version (4.0.21.9965) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[US48P500] new version (4.0.21.9965) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[USXG] new version (4.0.21.9965) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[S216150] new version (4.0.21.9965) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[BZ2LR] new version (4.0.15.9872) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[U7LT] new version (4.0.21.9965) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[U7LR] new version (4.0.21.9965) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[UHDIW] new version (4.0.21.9965) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[U2Sv2] new version (4.0.15.9872) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[US24P500] new version (4.0.21.9965) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[US24PL2] new version (4.0.21.9965) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[US48P750] new version (4.0.21.9965) is available [2019-02-10 18:38:56,234] <autoupdate-check> INFO system - firmware[S224250] new version (4.0.21.9965) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[S248750] new version (4.0.21.9965) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[S224500] new version (4.0.21.9965) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[US24] new version (4.0.21.9965) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[US8P60] new version (4.0.21.9965) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[U2IW] new version (4.0.15.9872) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[U5O] new version (4.0.15.9872) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[U2HSR] new version (4.0.15.9872) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[U7NHD] new version (4.0.21.9965) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[USC8] new version (4.0.21.9965) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[US8P150] new version (4.0.21.9965) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[U7HD] new version (4.0.21.9965) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[US16P150] new version (4.0.21.9965) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[BZ2] new version (4.0.15.9872) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[US8] new version (4.0.21.9965) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[US48PL2] new version (4.0.21.9965) is available [2019-02-10 18:38:56,235] <autoupdate-check> INFO system - firmware[US24P250] new version (4.0.21.9965) is available [2019-02-10 18:38:56,236] <autoupdate-check> INFO system - firmware[U7MSH] new version (4.0.21.9965) is available [2019-02-10 18:38:56,236] <autoupdate-check> INFO system - firmware[U7IWP] new version (4.0.21.9965) is available [2019-02-10 18:38:56,236] <autoupdate-check> INFO system - firmware[UGW4] new version (4.4.29.5124212) is available [2019-02-10 18:38:56,236] <autoupdate-check> INFO system - firmware[UGW3] new version (4.4.29.5124210) is available [2019-02-10 18:38:56,240] <autoupdate-check> INFO system - firmware[S28150] new version (4.0.21.9965) is available [2019-02-10 18:38:56,240] <autoupdate-check> INFO system - firmware[U2Lv2] new version (4.0.15.9872) is available [2019-02-10 18:38:56,240] <autoupdate-check> INFO system - firmware[U2O] new version (4.0.15.9872) is available [2019-02-10 18:38:56,240] <autoupdate-check> INFO system - firmware[U7Ev2] new version (3.8.17.6789) is available [2019-02-10 18:38:56,240] <autoupdate-check> INFO system - firmware[UGWXG] new version (4.4.29.5124239) is available [2019-02-10 18:38:56,240] <autoupdate-check> INFO system - firmware[S248500] new version (4.0.21.9965) is available If I manually connect to the database and run a show collections I can see that the controller has talked to the database as there are many new collections obviously created by the controller. EG: firewallgroup, broadcastgroup, networkconf, etc. $> mongo -host mongodb://ubnt:PASSWORD@unifi-controller-mongodb:27017/unifi MongoDB shell version v3.4.19 connecting to: mongodb://ubnt:PASSWORD@unifi-controller-mongodb:27017/unifi MongoDB server version: 3.4.19 Welcome to the MongoDB shell. For interactive help, type "help". For more comprehensive documentation, see http://docs.mongodb.org/ Questions? Try the support group http://groups.google.com/group/mongodb-user > show collections account admin alarm broadcastgroup device dpiapp dpigroup dynamicdns event extension firewallgroup firewallrule guest heatmap heatmappoint hotspot2conf hotspotop hotspotpackage map mediafile networkconf payment portalfile portconf portforward privilege radiusprofile rogue rogueknown routing scheduletask setting site stat tag task user usergroup verification voucher wall wlanconf wlangroup Here are the logs from STDOUT: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 1002 User gid: 1007 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... Warning: The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore /config/data/keystore -destkeystore /config/data/keystore -deststoretype pkcs12". [cont-init.d] 30-keygen: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. And lastly a lame attempt at starting the service manually: root@unifi-controller-c76f46bcc-nnrhh:/usr/lib/unifi# service unifi status * unifi is not running root@unifi-controller-c76f46bcc-nnrhh:/usr/lib/unifi# service unifi start * Starting Ubiquiti UniFi Controller unifi [fail] root@unifi-controller-c76f46bcc-nnrhh:/usr/lib/unifi# service unifi stop * Stopping Ubiquiti UniFi Controller unifi [ OK ] root@unifi-controller-c76f46bcc-nnrhh:/usr/lib/unifi# service unifi start * Starting Ubiquiti UniFi Controller unifi [fail] Any idea how I can continue troubleshooting from here? I'm at my witts end unfortunately after 2 days of work. Edited February 10, 2019 by zimmertr Link to comment
skank Posted February 10, 2019 Share Posted February 10, 2019 15 hours ago, skank said: Installed this one but when i click WebUI i get an error: This site is unreachable Port 8443 Its not used by another one Network type is bridge (should it be host?) Also whats the difference between the two anyway? When i do set the docker as host and when as bridge? I used the controller on my laptop till now, but now i want it on unraid Can i use my settings from laptop or do i have to start over? Once on unraid, can i switch back at laptop anytime or do i have to chose? Anyone? I want to get this running Link to comment
CHBMB Posted February 10, 2019 Share Posted February 10, 2019 Hey guys I’m new to UnRAID and I just installed this UniFi controller docker on my unraid. it starts but I cannot get into setup wizard. Tried reinstall, change from bridge to host, change port, delete appdata and still no luck any ideas? I was using the same docker on my raspberry pi and all works okayNo ideas with the lack of info you've posted. All you've said is "It doesn't work" which isn't really anything to go on.Sent from my Mi A1 using Tapatalk Link to comment
skank Posted February 10, 2019 Share Posted February 10, 2019 4 minutes ago, CHBMB said: No ideas with the lack of info you've posted. All you've said is "It doesn't work" which isn't really anything to go on. Sent from my Mi A1 using Tapatalk What do you need, cause i have the same problem.. it starts, but when i click webui, a browser opens but the page doesnt load Link to comment
CHBMB Posted February 10, 2019 Share Posted February 10, 2019 What do you need, cause i have the same problem.. it starts, but when i click webui, a browser opens but the page doesnt load Docker run command, and docker logs at the very least and copy the link you're visiting to load the webuiSent from my Mi A1 using Tapatalk Link to comment
skank Posted February 10, 2019 Share Posted February 10, 2019 5 minutes ago, CHBMB said: Docker run command, and docker logs at the very least and copy the link you're visiting to load the webui Sent from my Mi A1 using Tapatalk run command, i click webui then it goes to https://192.168.99.117:8443/ Log attached Link to comment
CHBMB Posted February 10, 2019 Share Posted February 10, 2019 12 minutes ago, skank said: run command, i click webui then it goes to https://192.168.99.117:8443/ Log attached Need the docker run command. Links to get it from my signature, you may need to switch on sigs in the forum settings to see it. Link to comment
skank Posted February 10, 2019 Share Posted February 10, 2019 its fixed ! lol I deleted everything App was gone but there was still something on cache, deleted that too and reinstalled now it works anyway the run command attached Link to comment
skank Posted February 10, 2019 Share Posted February 10, 2019 Question, i did a backup of my controller and tried to install the backup using docker on unraid, but it says the unraid controller is a lower version.. Isnt it the latest one? Link to comment
Recommended Posts