Thanks man. I appreciate your video, quick and easy to understand and learn, just the essential and well documented. I was using the old unifi image and i just noticed by accident that was deprecated, and that the new one needed some external work to function, like mongo db. Your video save me a lot of times!
I have been in IT for over 20 years and sometimes it's just easier to follow somebodies guide then to try to figure it out. I am glad I was able to help somebody with the video! Thanks for the comment!
Nice video. Thanks! You can use the built in file manager to delete folders instead of using the terminal window. You can also create the Web GUI button in the advanced options that you toggled when setting up the container. It’s three down from the Repository field that you edited. You can also double click the port numbers and then CTRL + F to replace the search. No need to copy and paste every time. Edit: My search tip only works for Firefox.
Thanks for sharing those tips! I am familiar with cli so I never even realized there was a gui option to manage the files. The tip on the find feature is going to save me so much time! Thanks again for sharing!
Great vid thank you, though I have a weird issue. So my logs are coming up with Port 8080 not available on repeat, I changed that port the same as you did so not sure why it's still trying to use that port. any ideas?
I assume you checked to make sure that all of the other containers are not using port 8080, it is a popular port to be used. Have you tried connecting to ServerIP:8443 ?
Hi. Thank you so much for your guide. I'm having this exact same problem. I've changed my 8080 port to 8082 and it appears that it's not applying the change. The docker logs for show that port 8080 is still trying to be used.
@@AlienTech42 I believe this is happening because the network type is set to "Host" and changing the port mapping won't do anything while "Host" is selected..... If you set the network type back to bridge and use ServerIP:8443 it should work.
Exact same problem on unRAID 6.12.8. Got past that by manually editing /mnt/user/appdata/unifi-network-application/data/system.properties and adding unifi.http.port=9080 (or whatever non-conflicting port). The new port was picked up and moved on. Now I'm finding the mongodb wasn't initialised with the init-mongo.js script so the unifi credentials in that file weren't set up. Something screwy going on with unRAID's settings not "sticking".
For anyone else having troubles, when entering the init-mongo.js portion in the container and host path during mongo container setup, for me unraid is creating a folder called "init-mongo.js" in the folder with my file, instead of linking the file itself. So leaving off the "init-mongo.js" off the end of both the container path and host path will still link the folder your init file is in, and mongo will automatically look for a file called "init-mongo.js" in the "/docker-entrypoint-initdb.d/" folder. Separately: don't use a hyphen in your mongo database name in your init file, it will likely not work. That took me ages to figure out.
My question may be a layman's question, but what is the difference between this self-hosted interface and the interface provided by, for example, Unifi's Dream Machine Pro?
The self hosted option allows you to control multiple Unifi sites all from one interface. I support several clients that all use Unifi equipment so it gives me one point to manage all of them remotely.
Not sure if my last comment was removed or if I forgot to click on the comment button but here's my story and question. My Terramaster F4-423's CPU doesn't support AVX. I just recently transitioned from TrueNAS Scale to Unraid and so far, I'm loving it. When installing the Unifi app on TrueNAS, the app ran with no issues. I tried following your guide but I ran into the same AVX issue as you did. The Intel Celeron N5105, as stated previously, doesn't support AVX so am I out of luck or are there alternate methods of installing the Unraid Unifi docker app? Thanks in advance.
You could try the older version of the Unifi Controller. Go back to the apps tab and search for Unifi. You are looking for brettm357's Repository... It's an older version, but it should be enough to get you back in control of your devices.
I set this up shortly after your initial post. One issue that I am facing is that every time I reboot my server or update mongo db, the mongo db container ip changes which means I have to change my config to match that ip. Is there a way to prevent this from happening?
I ran into the same issue after recording the video. I wish I would have run into it earlier so that I could have shown how to prevent it from happening. The hard but preferred method is to set the MongoDB network type to a custom network and set to a Fixed IP address. However, this will require deleting the database and starting over. The much easier method is to change the start order of the MongoDB container. My Mongo was first assigned 172.17.0.2, so it was the first address to be given out. I just moved my MongoDB to the top of the docker list and with the autostart turned on, it always gets that address. You will have to look at the IP that it was first setup with and adjust your start order to make it match. Hope that helps.
@@AlienTech42 I thought so, too, but in the forum, they say you can update the Repository with a newer version. I try that and it worked. I'm currently on unifi:8.3.32-unraid
Thanks man. I appreciate your video, quick and easy to understand and learn, just the essential and well documented. I was using the old unifi image and i just noticed by accident that was deprecated, and that the new one needed some external work to function, like mongo db. Your video save me a lot of times!
I have been in IT for over 20 years and sometimes it's just easier to follow somebodies guide then to try to figure it out. I am glad I was able to help somebody with the video! Thanks for the comment!
Nice video. Thanks!
You can use the built in file manager to delete folders instead of using the terminal window.
You can also create the Web GUI button in the advanced options that you toggled when setting up the container. It’s three down from the Repository field that you edited.
You can also double click the port numbers and then CTRL + F to replace the search. No need to copy and paste every time.
Edit: My search tip only works for Firefox.
Thanks for sharing those tips! I am familiar with cli so I never even realized there was a gui option to manage the files.
The tip on the find feature is going to save me so much time!
Thanks again for sharing!
I'm not seeing the init script information in the description.
Thanks for letting me know. It's there now. Sorry about that.
at 11:15 you mentioned enable auto backup. Is that in the unifi app or in Unraid?
That was within the Unifi interface. Settings, Backups, Checkbox for Auto Backup.
Great vid thank you, though I have a weird issue. So my logs are coming up with Port 8080 not available on repeat, I changed that port the same as you did so not sure why it's still trying to use that port. any ideas?
I assume you checked to make sure that all of the other containers are not using port 8080, it is a popular port to be used. Have you tried connecting to ServerIP:8443 ?
Hi. Thank you so much for your guide. I'm having this exact same problem. I've changed my 8080 port to 8082 and it appears that it's not applying the change. The docker logs for show that port 8080 is still trying to be used.
@@FL34O I managed to fix mine by changing what was using port 8080 for (in my case qbittorrent) to something else and that seemed to solve the issue
@@AlienTech42 I believe this is happening because the network type is set to "Host" and changing the port mapping won't do anything while "Host" is selected..... If you set the network type back to bridge and use ServerIP:8443 it should work.
Exact same problem on unRAID 6.12.8. Got past that by manually editing /mnt/user/appdata/unifi-network-application/data/system.properties and adding unifi.http.port=9080 (or whatever non-conflicting port). The new port was picked up and moved on. Now I'm finding the mongodb wasn't initialised with the init-mongo.js script so the unifi credentials in that file weren't set up. Something screwy going on with unRAID's settings not "sticking".
For anyone else having troubles, when entering the init-mongo.js portion in the container and host path during mongo container setup, for me unraid is creating a folder called "init-mongo.js" in the folder with my file, instead of linking the file itself. So leaving off the "init-mongo.js" off the end of both the container path and host path will still link the folder your init file is in, and mongo will automatically look for a file called "init-mongo.js" in the "/docker-entrypoint-initdb.d/" folder.
Separately: don't use a hyphen in your mongo database name in your init file, it will likely not work. That took me ages to figure out.
Thanks for sharing your solutions. I find it strange that it didn't work for you, but I am glad you worked it out.
Thanks again!
I had the same error and this fixed it! thanks!
My question may be a layman's question, but what is the difference between this self-hosted interface and the interface provided by, for example, Unifi's Dream Machine Pro?
The self hosted option allows you to control multiple Unifi sites all from one interface. I support several clients that all use Unifi equipment so it gives me one point to manage all of them remotely.
Not sure if my last comment was removed or if I forgot to click on the comment button but here's my story and question.
My Terramaster F4-423's CPU doesn't support AVX. I just recently transitioned from TrueNAS Scale to Unraid and so far, I'm loving it. When installing the Unifi app on TrueNAS, the app ran with no issues. I tried following your guide but I ran into the same AVX issue as you did. The Intel Celeron N5105, as stated previously, doesn't support AVX so am I out of luck or are there alternate methods of installing the Unraid Unifi docker app?
Thanks in advance.
You could try the older version of the Unifi Controller. Go back to the apps tab and search for Unifi. You are looking for brettm357's Repository... It's an older version, but it should be enough to get you back in control of your devices.
Am I blind or missing something. at 5:57 for the container Path I do not see this in the description? Awesome video though! I love this channel
Thanks for pointing that out. I missed it too. It has been added to the description.
@@AlienTech42 thank you so much
I set this up shortly after your initial post. One issue that I am facing is that every time I reboot my server or update mongo db, the mongo db container ip changes which means I have to change my config to match that ip. Is there a way to prevent this from happening?
I ran into the same issue after recording the video. I wish I would have run into it earlier so that I could have shown how to prevent it from happening. The hard but preferred method is to set the MongoDB network type to a custom network and set to a Fixed IP address. However, this will require deleting the database and starting over. The much easier method is to change the start order of the MongoDB container. My Mongo was first assigned 172.17.0.2, so it was the first address to be given out. I just moved my MongoDB to the top of the docker list and with the autostart turned on, it always gets that address. You will have to look at the IP that it was first setup with and adjust your start order to make it match. Hope that helps.
Is this method any better than using the ready-made unifi-controller-reborn?
Yes, this version is up to date. The Reborn version is an older version of the controller software.
@@AlienTech42 I thought so, too, but in the forum, they say you can update the Repository with a newer version. I try that and it worked. I'm currently on unifi:8.3.32-unraid
super helpful video!!!!
Glad it was helpful for you!
Might get some unifi stuff someday but I just bought a 3d printer…..preoccupied for now
What printer did you get? I have an Ender 3 v2 with a mods. Love it.
@@AlienTech42 friend sold me a modded Voxelab Aqulia s2, but I dropped coin on a X1C w AMS.