Been watching this for a couple months. Switched off linuxserver.io image after backup, followed directions and started this one up and restored image, had to manually reboot once more and then everything was and has been good since. Thanks!!

I've been meaning to migrate my controller from windows to unraid for awhile now and this couldn't have made it any easier.  Probably like others, I saw that the previous one was being deprecated and replaced by unifi-network-application.  I wasn't very thrilled to piece it together with mongo but was about to give it a go and then I found this.  After changing the tag to my version (8.0.26), setting my IP, and uploading my backup, it was running within minutes!  Thank you, much appreciate the hard work.  

I just found this awesome UniFi version, everything worked like a charm!

 

I have a (maybe stupid) question though:

 

I am using the "11notes/unifi:8.0.26-unraid" tag but i'm wondering; what happens when a new version arrives? I am used to using the "latest" tag so that it updates to the latest version automatically. 

 

Also, is there a way to change the icon of UniFi Reborn in the docker overview?

Just now, EmilioValentino said:

I just found this awesome UniFi version, everything worked like a charm!

 

I have a (maybe stupid) question though:

 

I am using the "11notes/unifi:8.0.26-unraid" tag but i'm wondering; what happens when a new version arrives? I am used to using the "latest" tag so that it updates to the latest version automatically. 

 

Also, is there a way to change the icon of UniFi Reborn in the docker overview?

Ubiquity releases a new update once a month on average. You can come back periodically to this thread and check what tag is safe to upgrade to. Its not automatic and you will have to check it every so often. If desired, simply use one of the less updated tags and come back twice a year if you prefer. 
 

No clue about changing the icon. Sounds unimportant and not an issue. 

43 minutes ago, EmilioValentino said:

Also, is there a way to change the icon of UniFi Reborn in the docker overview?

You mean like this?

 

 

I got the image from Google images (it is a .png) and uploaded it on an image hosting site.  I then edited the Docker container and switched to Advanced view and changed the Icon URL to the icon on the image hosting site.

Edited January 19, 20242 yr by Hoopster

56 minutes ago, PeteAsking said:

Ubiquity releases a new update once a month on average. You can come back periodically to this thread and check what tag is safe to upgrade to. Its not automatic and you will have to check it every so often. If desired, simply use one of the less updated tags and come back twice a year if you prefer. 
 

No clue about changing the icon. Sounds unimportant and not an issue. 

Ok thanks!

18 minutes ago, Hoopster said:

You mean like this?

 

 

I got the image from Google images (it is a .png) and uploaded it on an image hosting site.  I then edited the Docker container and switched to Advanced view and changed the Icon URL to the icon on the image hosting site.

Worked like a charm, thanks!

 

Just wanted to say thanks for creating this!  My UDM (base) died 2 days ago (the classic no lights, full fan death) and needed to get something up quick.  This worked out great and is running really fast on my hardware, much better than the UDM.

I have the UXG-Lite in transit and will be adding that shortly.  For now I'm up on my old Asus RT-AC86U for the router function, and managing my 2x NanoHD's and 1 U6 Pro with this container.

Edited January 27, 20242 yr by cscoppa

23 minutes ago, cscoppa said:

I have the UXG-Lite in transit and will be adding that shortly.

This controller container will come in handy for managing the UXG-Lite as well as it has no built-in controller like the Dream Machine. 

 

Frankly, I would rather have a separate controller rather than a built-in controller like on some Ubiquiti hardware.  As you noted, performance is much better this way and you don't have the limitations of some of the hardware with built-in controllers.

1 hour ago, Hoopster said:

This controller container will come in handy for managing the UXG-Lite as well as it has no built-in controller like the Dream Machine. 

 

Frankly, I would rather have a separate controller rather than a built-in controller like on some Ubiquiti hardware.  As you noted, performance is much better this way and you don't have the limitations of some of the hardware with built-in controllers.

 

I 100% agree with you.  Years ago I was self-hosted because I started with the Access Points.  When I got the Dream Machine I was disappointed in the speed compared to what I had before.  I also like the MANY options I have for backups.
 

8.0.28 has failed testing and will not be promoted to an unraid tag and will be skipped.

Are there any plans to upgrade the base image from 7.5.187 to 8.0.24?  I was on linuxservers image, downloaded a backup of the configuration but can't restore it into 7.5

 

Thx

4 hours ago, Dr_Noonia_Soong said:

Are there any plans to upgrade the base image from 7.5.187 to 8.0.24?  I was on linuxservers image, downloaded a backup of the configuration but can't restore it into 7.5

 

Thx

 

Hi,

 

Template has by default the tag "11notes/unifi:7.5.187-unraid" but you can change it.

 

You need to go to docker Hub and choose your own adventure tag: https://hub.docker.com/r/11notes/unifi/tags

 

I did the same as you last week and I'm using the tag "11notes/unifi:8.0.26-unraid"

Cheers!

3 hours ago, Carlos Dias said:

 

Hi,

 

Template has by default the tag "11notes/unifi:7.5.187-unraid" but you can change it.

 

You need to go to docker Hub and choose your own adventure tag: https://hub.docker.com/r/11notes/unifi/tags

 

I did the same as you last week and I'm using the tag "11notes/unifi:8.0.26-unraid"

Cheers!

If you use the supported images on page 1 of this forum post we can try to assist you with issues as they have been tested. 

6 hours ago, Carlos Dias said:

 

Hi,

 

Template has by default the tag "11notes/unifi:7.5.187-unraid" but you can change it.

 

You need to go to docker Hub and choose your own adventure tag: https://hub.docker.com/r/11notes/unifi/tags

 

I did the same as you last week and I'm using the tag "11notes/unifi:8.0.26-unraid"

Cheers!

Thank you, that worked, completely missed the templates.

 

Cheers

On 11/16/2023 at 9:08 PM, ssjucrono said:

I am using the official PMS Docker?

 

Here is the Unifi Reborn error 

Hey,
I have the same issue did you end up solving this? If so, hot did you fix it?

Thanks!

21 minutes ago, yverde said:

Hey,
I have the same issue did you end up solving this? If so, hot did you fix it?

Thanks!

Yes he did. He turned off the docker that was already using that port. You cannot have 2 dockers using the same port (in bridge mode). 

Edited February 11, 20242 yr by PeteAsking

44 minutes ago, PeteAsking said:

Yes he did. He turned off the docker that was already using that port. You cannot have 2 dockers using the same port (in bridge mode). 

 

I found one that was using port 1900 but was not showing in the port mapping of the docker page.
Turning this off didn't work at first, but then I turned everything off one by one and it ended up working when I also turned off Jellyfin. Now I'm not sure if Jellyfin is really related because it is in host mode, not using port 1900 and now both are runing at the same time. 

anyways, turning off some dockers did end up making it work!

Thanks!

 

EDIT: Somehow it really looks related to jellyfin, I am onle able to start it if jellyfin is not running, but once it's started I can start jellyfin after without any issues.

Edited February 11, 20242 yr by yverde

55 minutes ago, yverde said:

 

I found one that was using port 1900 but was not showing in the port mapping of the docker page.
Turning this off didn't work at first, but then I turned everything off one by one and it ended up working when I also turned off Jellyfin. Now I'm not sure if Jellyfin is really related because it is in host mode, not using port 1900 and now both are runing at the same time. 

anyways, turning off some dockers did end up making it work!

Thanks!

 

EDIT: Somehow it really looks related to jellyfin, I am onle able to start it if jellyfin is not running, but once it's started I can start jellyfin after without any issues.

Sounds related. Maybe ask on the jellyfin support thread. 

3 hours ago, yverde said:

EDIT: Somehow it really looks related to jellyfin, I am onle able to start it if jellyfin is not running, but once it's started I can start jellyfin after without any issues.

Yes, the culprit is Jellyfin. Port 1900 UDP is used by Jellyfin and cannot be changed.

 

From the Jellyfin Networking page:

Just do something like this, I don't even have that L2 Discovery option turned on, and I can manage my devices just fine.  (and Adopt)

 

Edited February 11, 20242 yr by cscoppa

5 hours ago, cscoppa said:

Just do something like this, I don't even have that L2 Discovery option turned on, and I can manage my devices just fine.  (and Adopt)

 

 

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!

Edited February 12, 20242 yr by yverde

5 minutes ago, 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!

You will have to wait for the next version to come out in a couple weeks. The .28 version was not accepted for deployment. 

Hi all,

Okay, so I'm totally lost here...

I'm trying to get this up and running from scratch, not restoring from any sort of prior Unifi system.  The initial instructions on page 1 all seem to relate to migrating from a previous install.

I can install and run the docker, and I can even log into the WebUI, but it tells me I have no access to a gateway, so most everything it grayed-out.

I suspect it may be because I have 2 ports that I was forced to change (I know!); ports 8080 and 6789 are used by other dockers on my system, and can't be removed.  Is this a dealbreaker?  I edited them in the Unifi template, which I know was noted as a very bad idea.  Is there any hope for me? lol

Assuming that this isn't the cause of all my woes, what's my next step?  How do I connect to a "gateway"?

 

I'm using a pfsense box as my router/firewall, and it's an external machine, not hosted in unraid.  I'm sure that matters.

I watched a video by Lawrence systems about setting up Unifi with pfsense, and that's actually what got me thinking about self-hosting the controller software, as he didn't seem to like the UDM Pro very much.  I have one here, but I'll probably just sell it if I can get this working.  However, Tom was talking about having to have 2 networks for the UDM Pro to work correctly, is that also the case when using this docker?  As you can tell, I'm rather confuzzled...

5 minutes ago, Elmojo said:

Hi all,

Okay, so I'm totally lost here...

I'm trying to get this up and running from scratch, not restoring from any sort of prior Unifi system.  The initial instructions on page 1 all seem to relate to migrating from a previous install.

I can install and run the docker, and I can even log into the WebUI, but it tells me I have no access to a gateway, so most everything it grayed-out.

I suspect it may be because I have 2 ports that I was forced to change (I know!); ports 8080 and 6789 are used by other dockers on my system, and can't be removed.  Is this a dealbreaker?  I edited them in the Unifi template, which I know was noted as a very bad idea.  Is there any hope for me? lol

Assuming that this isn't the cause of all my woes, what's my next step?  How do I connect to a "gateway"?

 

I'm using a pfsense box as my router/firewall, and it's an external machine, not hosted in unraid.  I'm sure that matters.

I watched a video by Lawrence systems about setting up Unifi with pfsense, and that's actually what got me thinking about self-hosting the controller software, as he didn't seem to like the UDM Pro very much.  I have one here, but I'll probably just sell it if I can get this working.  However, Tom was talking about having to have 2 networks for the UDM Pro to work correctly, is that also the case when using this docker?  As you can tell, I'm rather confuzzled...

unifi requires these ports so instead of changing the ports, set them back and try changing your network to a custom one like br0 and setting a manual static IP. I haven’t actually tested this but maybe you can tell us if that works for you. Then you wont get a port conflict. 

Edited February 17, 20242 yr by PeteAsking