15 hours ago, PeteAsking said:

You already have a different docker using port 1900 as the error says.

I did check that and there is nothing else showing as using that port except this container (container shows in Docker installed even though this error but if I start it then execution error)

Note if I manually clear/delete the container and manually change this port when installing (example 1922) the message then changes to the same error except with the new port instead (example 1922)

54 minutes ago, gacpac said:

i want to add that my docker run is the below and that i see a message that i'm not sure if could be the root cause. Take a look

docker run
  -d
  --name='unifi-controller-reborn'
  --net='bridge'
  --pids-limit 2048
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="unifi-controller-reborn"
  -e 'MEM_LIMIT'='4096'
  -e 'MEM_STARTUP'='2048'
  -e 'UMASK'='002'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='https://[IP]:[PORT:8443]'
  -l net.unraid.docker.icon='icon'
  -p '8443:8443/tcp'
  -p '3478:3478/udp'
  -p '10001:10001/udp'
  -p '8080:8080/tcp'
  -p '1900:1900/udp'
  -p '8843:8843/tcp'
  -p '8880:8880/tcp'
  -p '6789:6789/tcp'
  -p '5514:5514/udp'
  -v '/mnt/user/appdata/unifi-controller-reborn':'/unifi/var':'rw'
  --memory=8G
  --tmpfs /unifi/log:exec,uid=99,gid=100
  --tmpfs /unifi/run:exec,uid=99,gid=100
  --tmpfs /tmp:exec,uid=99,gid=100 '11notes/unifi:10.0-unraid-amd64'

WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
2d91679d0812c351a8d4a9720c62722384293d3191b8be270d55d9b94e62db1f

The command finished successfully!

you know i want to add i was able to move to the lsio container and well it works right, interesting enough i got the same errors but in this case the container started with no issues. happy to test out and share in case anyone has issues. Pete we can collaborate if needed

2 hours ago, gacpac said:

i want to add that my docker run is the below and that i see a message that i'm not sure if could be the root cause. Take a look

docker run
  -d
  --name='unifi-controller-reborn'
  --net='bridge'
  --pids-limit 2048
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="unifi-controller-reborn"
  -e 'MEM_LIMIT'='4096'
  -e 'MEM_STARTUP'='2048'
  -e 'UMASK'='002'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='https://[IP]:[PORT:8443]'
  -l net.unraid.docker.icon='icon'
  -p '8443:8443/tcp'
  -p '3478:3478/udp'
  -p '10001:10001/udp'
  -p '8080:8080/tcp'
  -p '1900:1900/udp'
  -p '8843:8843/tcp'
  -p '8880:8880/tcp'
  -p '6789:6789/tcp'
  -p '5514:5514/udp'
  -v '/mnt/user/appdata/unifi-controller-reborn':'/unifi/var':'rw'
  --memory=8G
  --tmpfs /unifi/log:exec,uid=99,gid=100
  --tmpfs /unifi/run:exec,uid=99,gid=100
  --tmpfs /tmp:exec,uid=99,gid=100 '11notes/unifi:10.0-unraid-amd64'

WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
2d91679d0812c351a8d4a9720c62722384293d3191b8be270d55d9b94e62db1f

The command finished successfully!

Something has gone wrong with your local template. It has not pulled the latest template. Can you remove this broken one and also delete the local template from your /boot/config/plugins/dockerMan/templates-user directory so it is forced to download a new template?

1 hour ago, egtrev said:

I did check that and there is nothing else showing as using that port except this container (container shows in Docker installed even though this error but if I start it then execution error)

Note if I manually clear/delete the container and manually change this port when installing (example 1922) the message then changes to the same error except with the new port instead (example 1922)

This is an unraid issue. I cannot fix it. Stop all dockers and start only this unifi one. If it starts then you have a port conflict. There is nothing I can do about that.

22 minutes ago, PeteAsking said:

This is an unraid issue. I cannot fix it. Stop all dockers and start only this unifi one. If it starts then you have a port conflict. There is nothing I can do about that.

There are no other Docker containers running when I get the error (I have others dockers installed but stopped)

10 minutes ago, egtrev said:

There are no other Docker containers running when I get the error (I have others dockers installed but stopped)

Reboot unraid I guess. Unraid issue, complain to unraid devs, I cannot prevent a port becoming locked. You have to get rid of this error:

docker: Error response from daemon: driver failed programming external connectivity on endpoint unifi-controller-reborn (0d11e26333500a88b486606d2a5d74e83bb5cf93f5597734a8aadf6549d73b7d): failed to bind port 0.0.0.0:1900/udp: Error starting userland proxy: listen udp4 0.0.0.0:1900: bind: address already in use.

Edited March 10Mar 10 by PeteAsking

3 minutes ago, PeteAsking said:

Reboot unraid I guess. Unraid issue, complain to unraid devs, I cannot prevent a port becoming locked.

I've disabled Docker completely and enabled it again on Unraid and everything seems to be working now, just restored my backup from old Unifi container and all seems to be working great, devices all showing online.

Thanks for your help with this.

2 minutes ago, egtrev said:

I've disabled Docker completely and enabled it again on Unraid and everything seems to be working now, just restored my backup from old Unifi container and all seems to be working great, devices all showing online.

Thanks for your help with this.

No worries. You should open a bug regarding unraid port locking. Im not sure what causes it but I have seen other people have it before on plex dockers and similar.

Edited March 10Mar 10 by PeteAsking

I just want to say thanks to the dev! I used to run this on my Unraid box, but switched over to a separate debian + compose box a while ago and it has been working great. Even moving to 10.1.85-nobody has been a breeze. So thanks for maintaining this in both Unraid and generic images!

2 hours ago, PeteAsking said:

Something has gone wrong with your local template. It has not pulled the latest template. Can you remove this broken one and also delete the local template from your /boot/config/plugins/dockerMan/templates-user directory so it is forced to download a new template?

I did actually and got the same error. It's very odd

12 minutes ago, gacpac said:

I did actually and got the same error. It's very odd

Doesnt make sense because in your docker run ‘11notes/unifi:10.0-unraid-amd64' is different to what is specified in the xml template so its not pulling the template correctly.

What cpu do you have

Edited March 10Mar 10 by PeteAsking

10 hours ago, PeteAsking said:

No worries. You should open a bug regarding unraid port locking. Im not sure what causes it but I have seen other people have it before on plex dockers and similar.

If it's port locking, it's usually port 1900, the turn/stun port that is often found alongside media servers like Plex and Jellyfin.

unifi using port 1900 for it internal unifi talk structure...

I would make a new Docker network bridge and try it again... or move the reborn docker to its own custom ip

https://bmartino1.weebly.com/guide-dockernetworks.html

Edited March 11Mar 11 by bmartino1

@PeteAsking Some days ago, you wrote about a "possible solution" for "Unifi OS Server in a Docker" and that maybe (also) 11notes will go this way. Any news on that (as you clearly do not prefer the solution of bmartino ;-) )?

5 hours ago, JayDee73 said:

@PeteAsking Some days ago, you wrote about a "possible solution" for "Unifi OS Server in a Docker" and that maybe (also) 11notes will go this way. Any news on that (as you clearly do not prefer the solution of bmartino ;-) )?

It wont be soon, problem is to figure out how to make it secure as unifi dont themselves, so any solution 6+ months away probably.

Am a newbie to UnRaid am am stuck trying to use the Unifi server in a container. Did have V10 installed and running,( no previous versions had been used or installed). In trying to add Stirling PDF, communications to the Unifi server were lost. Have removed Stirling and its app data, as well as the Unifi re-born server. These issues all seem to happen about the time that the UnRaid update was applied as well as the Unifi update. Have been working to re-install the Unifi re-born server and be able to communicate with it,. The Unifi re-born server has been re-installed, and is running. However I am unable to connect to it. Welcome any help that will allow communications with the Unifi re-born server. Have tried to ONLY use the default settings, as recommended.

The diagnostics log file is attached.

Thank you

t340-diagnostics-20260318-0937.zip

38 minutes ago, oakley4404 said:

Am a newbie to UnRaid am am stuck trying to use the Unifi server in a container. Did have V10 installed and running,( no previous versions had been used or installed). In trying to add Stirling PDF, communications to the Unifi server were lost. Have removed Stirling and its app data, as well as the Unifi re-born server. These issues all seem to happen about the time that the UnRaid update was applied as well as the Unifi update. Have been working to re-install the Unifi re-born server and be able to communicate with it,. The Unifi re-born server has been re-installed, and is running. However I am unable to connect to it. Welcome any help that will allow communications with the Unifi re-born server. Have tried to ONLY use the default settings, as recommended.

The diagnostics log file is attached.

Thank you

t340-diagnostics-20260318-0937.zip

The logs you provided show no viability into docker or related settings so have no use. Can you tell me what tag you are using?

Can send additional logs or screen shots, please let me know what you need.

Thank you !!

2 hours ago, oakley4404 said:

Can send additional logs or screen shots, please let me know what you need.

Thank you !!

Still the tag you are using like I asked.

If I understand your question I believe the tag being used is br1.

43 minutes ago, oakley4404 said:

If I understand your question I believe the tag being used is br1.

If you click on the unifi docker the tag will look something like:

11notes/unifi:10.1.85-unraid

Thank you for your patience, Apologize still learning all the names of things.

11notes/unifi:10.1.85-unraid

24 minutes ago, oakley4404 said:

And this is a fresh install? Its not working if you browse https://10.0.0.249:8443 ?

Correct, it is a fresh install with ALL previous APP data and user data deleted (am fairly confident that the previous files were removed, but not 100% sure) .

Have tried to access the Unifi server from three different browsers all using https://10.0.0.249:8443/

This is the same IP address that was working in a previous installation.

Am able to Ping 10.0.0.249, but can not connect to the Unifi server

All browsers return the following:

1 hour ago, oakley4404 said:

Correct, it is a fresh install with ALL previous APP data and user data deleted (am fairly confident that the previous files were removed, but not 100% sure) .

Have tried to access the Unifi server from three different browsers all using https://10.0.0.249:8443/

This is the same IP address that was working in a previous installation.

Am able to Ping 10.0.0.249, but can not connect to the Unifi server

All browsers return the following:

Go into the unifi docker and change from basic view to advanced view and paste the extra parameters line here. Someone else had an issue there before maybe its the same for you.