[Support] Linuxserver.io - Unifi


Recommended Posts

3 minutes ago, H2O_King89 said:


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

 

I am hosting a UniFi device from another site but that's connected via VPN.  I will deal with that one later once I get my local devices working.

 

I had the over-ride unchecked but it is correct and I have a DNS record on my network for that FQDN.  I've since tried checking it and re-provisioning my devices to no avail.

Link to comment
 
I am hosting a UniFi device from another site but that's connected via VPN.  I will deal with that one later once I get my local devices working.
 
I had the over-ride unchecked but it is correct and I have a DNS record on my network for that FQDN.  I've since tried checking it and re-provisioning my devices to no avail.

Try checking host override and put in the local ip of the controller and then provision.

Mine is override with an external FQDN that points to my public ip.


Sent from my iPhone using Tapatalk
Link to comment
6 minutes ago, H2O_King89 said:


Try checking host override and put in the local ip of the controller and then provision.

Mine is override with an external FQDN that points to my public ip.


Sent from my iPhone using Tapatalk

 

Ok so I set the override to my controller's IP and re-provisioned the AP I have connected from a different site via VPN since this will allow me to monitor the connections in my Firewall.  The only connection between the AP and controller during reprovision is 8080.  Never tried to connect via 3478.

Edited by IamSpartacus
Link to comment
39 minutes ago, IamSpartacus said:

Solved the issue by specifying the port as UDP with -p 3478:3478/udp.  Never had to specify udp/tcp before so that was a first.

I have a USG and am suffering the same issue. I have a few sites connected to my Controller on my Unraid and only after this last update has this Stun server port issue arrised.

 

I have the following ports open in my USG forwarded to the Unraid on both TCP and UDP

 

8443,8081,8880,27117,3478,8080

 

They are just listed out as above in the USG, are you saying I should swap this to 

 

8443,8081,8880,27117,-p 3478:3478/udp,8443,8081,8080

 

Will that work?

Link to comment
12 minutes ago, rhinoman said:

I have a USG and am suffering the same issue. I have a few sites connected to my Controller on my Unraid and only after this last update has this Stun server port issue arrised.

 

I have the following ports open in my USG forwarded to the Unraid on both TCP and UDP

 

8443,8081,8880,27117,3478,8080

 

They are just listed out as above in the USG, are you saying I should swap this to 

 

8443,8081,8880,27117,-p 3478:3478/udp,8443,8081,8080

 

Will that work?

 

No the -p 3478:3478/udp is how you map the port to the docker using the docker create command (ie. when creating a docker via CLI in Linux not through the UnRAID GUI).  I don't have any experience with USG so I can't really speak to how that needs to be configured.

Link to comment

I just updated to the latest and the webUI takes me through the configuration wizard. I just finished setting this up last night so im not sure if I'm doing something wrong.

 

Edit: Do I need to manually configure a host path?

Edited by Nimitz
Link to comment
I just updated to the latest and the webUI takes me through the configuration wizard. I just finished setting this up last night so im not sure if I'm doing something wrong.
 
Edit: Do I need to manually configure a host path?

Don’t understand your question. Are you having a stun issue? Then yes you have to add a port to the docker as I showed above


Sent from my iPhone using Tapatalk
Link to comment
8 minutes ago, H2O_King89 said:


Don’t understand your question. Are you having a stun issue? Then yes you have to add a port to the docker as I showed above


Sent from my iPhone using Tapatalk

No I updated the docker to the newest release and I have to set up my controller again.

Link to comment
I don't know if this was because of my firewall setup, but the Stun message was removed for me when I assigned an IP address to my docker using the 6.4+ feature

They just push an update with the port now map in the template. Did you have the port map before changing the ip?


Sent from my iPhone using Tapatalk
Link to comment
9 minutes ago, H2O_King89 said:


They just push an update with the port now map in the template. Did you have the port map before changing the ip?


Sent from my iPhone using Tapatalk

I tried manually mapping the port which didn't work for me, so I removed it, and while I was doing some other docker changes (was adding VLANs to my network and assigning dockers to the VLANs) I changed the IP for the docker and the error went.  

 

I haven't got the new update with the new port yet

Link to comment
10 hours ago, rhinoman said:

I already had the port forwarded and was still getting the error. I just swapped my Docker from bridge to host mode and it now seems to have gone.

 

You need to add a port mapping in the container template also. It's not enough to port forward to unraid. When you change to host, all ports are available to the container. 

Link to comment
11 hours ago, DZMM said:

I don't know if this was because of my firewall setup, but the Stun message was removed for me when I assigned an IP address to my docker using the 6.4+ feature

 

If you assign an IP to the container you don't need port mapping as all is open. 

Link to comment

Hi all,

 

Running this container in 6.3.5. Get to the setup in the webUI, but can't detect any devices. All settings are default, no ports changed. Server is static 1.100 address. 

Installing controller software on a Windows machine on 1.8 works as expected. USG, AP and switch are all seen on the configuration wizard.

 

Any ideas?

Link to comment
2 hours ago, -Daedalus said:

Hi all,

 

Running this container in 6.3.5. Get to the setup in the webUI, but can't detect any devices. All settings are default, no ports changed. Server is static 1.100 address. 

Installing controller software on a Windows machine on 1.8 works as expected. USG, AP and switch are all seen on the configuration wizard.

 

Any ideas?

 

Did you follow the Readme in the github link in the first post? 

Link to comment
7 hours ago, -Daedalus said:

Hi all,

 

Running this container in 6.3.5. Get to the setup in the webUI, but can't detect any devices. All settings are default, no ports changed. Server is static 1.100 address. 

Installing controller software on a Windows machine on 1.8 works as expected. USG, AP and switch are all seen on the configuration wizard.

 

Any ideas?

 

As was suggested earlier in this thread, setting the UniFi docker to host instead of bridge network type allowed the controller to detect the devices in my case.  Once detected, updated, adopted and configured, the container can, supposedly (I haven't verified as I am still provisioning a couple of devices), be set back to bridge mode.

 

In bridge mode, the docker did not detect any of my devices even though they did all show up in the UniFi controller on my iPhone.  I do not want to install it on a Windows PC because I do not want to install 64-bit Java just for the controller.

Edited by Hoopster
  • Like 1
Link to comment
  • 2 weeks later...

I had the STUN problem which wasn't obvious until now as a new version of the Controller software highlights this on the main Devices page.  I assume that has been fixed now in the template?

 

I wait impatiently for 6.4 to be released so that I can use a separate IP for each Docker, just as saarg does,  so that issues like this become history.

Link to comment
  • 3 weeks later...

Hi, i need help, can't add my UniFi AP-AC-Pro to the controller

I added the Unifi docker to my unraid server, I see my AP but when I try to addopt it says Adopting failed, I try to add it into my old windows controller and it works, I also upgraded my ap to the lastest version 3.9.15.8011

 

I also tried to reset my ap to default factory 2-3 time, someone can help me !

 

I have no error im my log:

Quote

-------------------------------------
_ _ _
| |___| (_) ___
| / __| | |/ _ \
| \__ \ | | (_) |
|_|___/ |_|\___/
|_|

Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
User gid: 100
-------------------------------------

[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...
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

 

Unifi.PNG

Edited by nicecube
Link to comment
1 hour ago, nicecube said:

i need help, can't add my UniFi AP-AC-Pro to the controller

 

Have you tried setting the docker to Host mode instead of Bridge mode until devices are adopted?  You can then set it back to Bridge after all devices are adopted.  That's what enabled me to be able to adopt new devices with this docker.

Link to comment

A colegue of work told me to add the ip address of my controller in my unified router into the DHCP. Otherwise I do not have port 8080 by default which can cause a problem. Also I could connect in the terminal in ssh and make the command

 

set-inform http: //172.16.82.5: 8084

 

I will try when I'm at home

Link to comment
  • trurl locked this topic
Guest
This topic is now closed to further replies.