March 31, 20242 yr My apologies for necro-ing this post, but I had been following along and got it working; however, I am migrating from a backup and I am getting an error message that the backup is from a newer version that can't be used. I guess, I'm wondering, how often is the app/docker updated? I would like to move off of my actual VM and move it to unRAID.
March 31, 20242 yr Author 4 hours ago, CrippleZero said: My apologies for necro-ing this post, but I had been following along and got it working; however, I am migrating from a backup and I am getting an error message that the backup is from a newer version that can't be used. I guess, I'm wondering, how often is the app/docker updated? I would like to move off of my actual VM and move it to unRAID. Are you using the latest tag? It was made available just a few days ago.
April 7, 20242 yr On 2/11/2024 at 9:38 PM, yverde said: yes that totally worked for me so far thx! Other question, my backup was made on v8.0.28 but the latest docker is on 8.0.26 as I understand? Will it eventually be updated to 8.0.28 so I can restore my backup or am I better restart from scratch? Thanks! To fix my issue I used a custom:br0 so it has different IP so no more port conflict
April 16, 20242 yr Hi. Minor thing, but the first post refers to the container by the name "unraid-controller-reborn" rather than "unifi-controller-reborn"!
April 17, 20242 yr Author On 4/16/2024 at 5:11 AM, turnma said: Hi. Minor thing, but the first post refers to the container by the name "unraid-controller-reborn" rather than "unifi-controller-reborn"! Thanks. I have fixed this error now.
April 19, 20242 yr I'm trying to figure out why my container doesn't see the network traffic for the unraid server it is running on (192.168.1.111) i did not change anything in the docker template, running "11notes/unifi:8.1.113-unraid" I believe i set up the container without changing any settings other than disabling automatic updates.
April 19, 20242 yr Author 12 minutes ago, MammothJerk said: I'm trying to figure out why my container doesn't see the network traffic for the unraid server it is running on (192.168.1.111) i did not change anything in the docker template, running "11notes/unifi:8.1.113-unraid" I believe i set up the container without changing any settings other than disabling automatic updates. Not sure but there probably isnt much I can do to fix it. The software works however unifi code with all the bugs they insert into it and its a closed box.
April 23, 20242 yr On 2/22/2024 at 9:10 PM, yverde said: Hi, I'm trying to restore a backup from the official desktop controller app. When I use this container instead my AP shows as adopting then goes to Offline then back to adopting, but never succeed. The AP is not offline though as all my devices are not connected to it. I'm using the new version 8.0.28 Should I be able to restore from a backup made in the official controller? Thanks! I am actually having this same problem with 8.1.113. First time using this and everything during setup was just fine. Restored backup just fine. But my USG and my U6-Lite are stuck in an "Adopting" and "Offline" loop. Anyone else run into this with 8.1.113 or any suggestions? I've restarted the docker and power-cycled the devices. I didn't change anything during the docker setup. Followed the instructions.
April 23, 20242 yr Author 7 hours ago, pmeledeo said: I am actually having this same problem with 8.1.113. First time using this and everything during setup was just fine. Restored backup just fine. But my USG and my U6-Lite are stuck in an "Adopting" and "Offline" loop. Anyone else run into this with 8.1.113 or any suggestions? I've restarted the docker and power-cycled the devices. I didn't change anything during the docker setup. Followed the instructions. Is the inform ip in the settings set correctly still? (inform host override) Edited April 23, 20242 yr by PeteAsking
April 23, 20242 yr 12 hours ago, pmeledeo said: I am actually having this same problem with 8.1.113. First time using this and everything during setup was just fine. Restored backup just fine. But my USG and my U6-Lite are stuck in an "Adopting" and "Offline" loop. Anyone else run into this with 8.1.113 or any suggestions? I've restarted the docker and power-cycled the devices. I didn't change anything during the docker setup. Followed the instructions. when restoring a backup config, the devices in the netwrok are looking for the old unif devicve and the old ip of the previous controler. Did the ip address change? the newer hardware also looks for the controllers mac address to capture and sync. For this reason i would have you double check your docker settings: Option 1 confirm docker network is mac vlan, make sure ip address is same as controller from backup, add mac address. Option 2: Reset the devices to factory reset and readopt devices. They should resync and optain previous settings from your backup. On 3/7/2024 at 4:59 PM, bmartino1 said: Let's run through some basic networking and docker settings. What are your unraids network settings? I'm more interested in the setting for bridging and bonding... Then what are your docker settings? More interested in Docker custom network type: and host access. This is my configuration for a proper custom bridge IP settings for macvlan network access. Depending on how you want to use the docker network and how you want to access dockers from unraid we will need this information to know what type of network setup you are using. read about docker network types here: https://docs.docker.com/network/ and https://docs.docker.com/network/drivers/ Custom br0 is a type of bridge driver... By default, Unraid has bridging enabled and wants docker network to use ipvlan. This changes how docker setups and communicates network traffic to the docker network. If we run a docker image and set the network to host. The ip to access that docker if it has a webUI will be the same ip as the unraid system. Any ports the docker has will replace unraids ports and is more for items like clam av to scan itself or databases you want on the LAN to be accessible via your local network. Bridge network mode uses the Unraids Default 172.x.x.x dhcp server and creates a switch port bridge to communicate via sharing your unraids network adapter. your docker is asigned a 172.x.x.x address in bridge mode and how it communicates depends on unraid docker setting, ie macvlan or ipvlan. But more to do with host network access. Custom br0 means to bridge/bond the eth0 of your unraid and have it share a LAN ip address from your router. In my case my router dhcp is 192.168.1.x meaning the docker will get a 192.168.1.x unless I tell it otherwise. macvlan will make a random mac address to facilitate this, and some firewall/routers will see that your unriads ip is being duplicated or assigned to multiple devices sharing the same ip. (This is why the switch to ipvlan to fix layer 3 networking issues, buts only a problem with vlan network traffic controls... If I run a macvlan network I can add an extra option and set a custom mac address to help router traffic. (this was required in older settings before "private mac" and phones were connecting to the internet to guarantee a network path access. macvlan extra parm in docker : --mac-address 02:42:C0:A8:01:XX ->hexadecimal (0123456789abcdefgh) replace xx with a combination of a hexadecimal group... Then the router can static assign. Unfi has a host adopt feature that looks for a dns name unifi on the network you want the unfi network application to have a dns name set to unifi. So I also run macvlan to add hostname: extra parameters: --mac-address 02:42:C0:A8:01:0A --hostname unifi ^This now give me the ability to statically assign an ip address. Via dhcp on custom br0 network which is the LAN DHCP IP from my router... Unraid to use custom br0 it is recommended to static client asign an ip address. So custom br0 will be 192.168.1.x this mean I can access the unif application at 192.168.1.x Basic network that is dependent on what you run and how you run it. We need more info for troubleshooting network like these.
April 23, 20242 yr Hi guys, I have a trouble wit service stop at the end. The log shows the following: (...) :0 Permanent error code on channel bind request: 403 - Forbidden IP :0 All TURN channel bindings failed :0 Unable to read data from SCTP socket. Permanent error: (104) Connection reset by peer :0 SCTP ingest failed :0 SCTP ingest failed :0 Unable to do SSL I/O :0 webRtcId 1 terminated with code: (-2147090409) WebRTC connection interrupted from far side :0 TCP candidates not supported yet :0 TCP candidates not supported yet (...) :0 Permanent error code on channel bind request: 403 - Forbidden IP (...) :0 All TURN channel bindings failed :0 TCP candidates not supported yet :0 Permanent error code on channel bind request: 400 - Empty port number in channel bind request :0 All TURN channel bindings failed :0 STUN id: 4; fd: 194 172.17.0.5:32995 -> 92.249.173.32:52282 (eth0) DTLS id: 14 (92.249.173.32:32995) (PEER) timed out :0 webRtcId 3 terminated with code: (-2147090409) WebRTC connection interrupted from far side :0 STUN id: 4; fd: 191 172.17.0.5:51377 -> 192.168.178.185:54448 (eth0) DTLS id: 19 (192.168.178.10:51377) (PEER) timed out :0 webRtcId 2 terminated with code: (-2147090409) WebRTC connection interrupted from far side Can you give me some advice? Thanks a lot in advance Cheers Levente
April 23, 20242 yr Author 1 hour ago, levnetet said: Hi guys, I have a trouble wit service stop at the end. The log shows the following: (...) :0 Permanent error code on channel bind request: 403 - Forbidden IP :0 All TURN channel bindings failed :0 Unable to read data from SCTP socket. Permanent error: (104) Connection reset by peer :0 SCTP ingest failed :0 SCTP ingest failed :0 Unable to do SSL I/O :0 webRtcId 1 terminated with code: (-2147090409) WebRTC connection interrupted from far side :0 TCP candidates not supported yet :0 TCP candidates not supported yet (...) :0 Permanent error code on channel bind request: 403 - Forbidden IP (...) :0 All TURN channel bindings failed :0 TCP candidates not supported yet :0 Permanent error code on channel bind request: 400 - Empty port number in channel bind request :0 All TURN channel bindings failed :0 STUN id: 4; fd: 194 172.17.0.5:32995 -> 92.249.173.32:52282 (eth0) DTLS id: 14 (92.249.173.32:32995) (PEER) timed out :0 webRtcId 3 terminated with code: (-2147090409) WebRTC connection interrupted from far side :0 STUN id: 4; fd: 191 172.17.0.5:51377 -> 192.168.178.185:54448 (eth0) DTLS id: 19 (192.168.178.10:51377) (PEER) timed out :0 webRtcId 2 terminated with code: (-2147090409) WebRTC connection interrupted from far side Can you give me some advice? Thanks a lot in advance Cheers Levente Not sure what is wrong. Can you check no other dockers are running when you start it to rule out some sort of conflict and check you have enough disk space and so on. Also check your networking is logical. Seems like an error above the container.
April 25, 20242 yr On 4/23/2024 at 7:08 AM, PeteAsking said: Is the inform ip in the settings set correctly still? (inform host override) I am unfamiliar with this. Didn't see anything about setting this up in the install instructions for this. I will do some research on the topic to get myself up to speed. And to answer the other reply's question, nothing changed IP-wise. I went ahead and removed this docker container from Unraid and just went back and installed the Unifi Controller on my PC. That is still working for now. I'd love to get it running on my Unraid server so I don't have to keep my PC on and awake at all times. I'll do a bit more research on all of this before attempting again. Thank you for the replies and advice.
April 25, 20242 yr 6 minutes ago, pmeledeo said: I am unfamiliar with this Under network --> System -->Advanced Override IP address is IP address of Unraid server on which Unifi controller container is running. In my case, iIn the example above, it is the IP address of the Unifi device running the network controller software.
April 25, 20242 yr Author 10 minutes ago, pmeledeo said: I am unfamiliar with this. Didn't see anything about setting this up in the install instructions for this. I will do some research on the topic to get myself up to speed. And to answer the other reply's question, nothing changed IP-wise. I went ahead and removed this docker container from Unraid and just went back and installed the Unifi Controller on my PC. That is still working for now. I'd love to get it running on my Unraid server so I don't have to keep my PC on and awake at all times. I'll do a bit more research on all of this before attempting again. Thank you for the replies and advice. This basically confirms that the ip changed since the docker/unraid has a different ip to the pc it was on before. You need to set the inform ip and do what bmartino said
April 25, 20242 yr 15 minutes ago, Hoopster said: Under network --> System -->Advanced Override IP address is IP address of Unraid server on which Unifi controller container is running. In my case, iIn the example above, it is the IP address of the Unifi device running the network controller software. Thank you for the explanation. This seems to have fixed my problem. I put the IP of my Unraid server in that field and then everything adopted. Thank you all. I'm pretty new to this side of things so been trying to soak up as much knowledge as I can.
April 30, 20242 yr Hi, I have my repository/tag set to 11notes/unifi:8.1.113-unraid Noticed this morning that the container said it had an update available. Did the update and the version (specified in the container) updated to 8.1.127 yet my repository/tagtag is still set to 11notes/unifi:8.1.113-unraid Is this normal? Edit: everything seems to be working fine after the update Edited April 30, 20242 yr by ultimz Added more info
April 30, 20242 yr Author 7 hours ago, ultimz said: Hi, I have my repository/tag set to 11notes/unifi:8.1.113-unraid Noticed this morning that the container said it had an update available. Did the update and the version (specified in the container) updated to 8.1.127 yet my repository/tagtag is still set to 11notes/unifi:8.1.113-unraid Is this normal? Edit: everything seems to be working fine after the update What version are you running now? 8.1.127 is not supported at this time. Edited April 30, 20242 yr by PeteAsking
April 30, 20242 yr 1 hour ago, PeteAsking said: What version are you running now? 8.1.127 is not supported at this time. I am now running 8.1.127 Is that normal behavior for the container to show it has an update even though my tag is set to 11notes/unifi:8.1.113-unraid? Seems strange...
April 30, 20242 yr Just now, ultimz said: I am now running 8.1.127 Is that normal behavior for the container to show it has an update even though my tag is set to 11notes/unifi:8.1.113-unraid? Seems strange... Me too!
April 30, 20242 yr Chiming in too. I didn't notice the version change of I saw this post. Any way to downgrade back, since the tags are the same?
April 30, 20242 yr 2 hours ago, ultimz said: I am now running 8.1.127 Is that normal behavior for the container to show it has an update even though my tag is set to 11notes/unifi:8.1.113-unraid? Seems strange... It looks like tag 8.1.113-unraid was updated a day ago, according to Docker Hub. Perhaps this push was unintentional?
April 30, 20242 yr Author I will figure out what happened and come back to you. Edited April 30, 20242 yr by PeteAsking
April 30, 20242 yr Author I agree what appears to have happened is an inadvertent push has incorrectly updated tag 8.1.113 to version 8.1.127. I suggest moving to tag 8.1.127-unraid at this time for consistency and I will have to immediately support this tag due to the error. To track why or what happened you can use this link as I asked what happened on 11notes github (who runs the scripts that builds the images): https://github.com/11notes/docker-unifi/issues/16 Kind regards P
May 1, 20242 yr I jumped up to this later version also - not by accident but by design - changing tags to suit. Is there anything specific to look out for in the release ? As to why it was not yet supported ? All seems to be working for my limited stuff (USG, 2 x AP, 1 x 8port switch and 2 x flex).
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.