Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] - Unifi-Controller: Unifi. Unraid. Reborn.

Featured Replies

  • Author
18 minutes ago, tehg said:

Made those changes and restarted the container. No issues so far. I see devices adopting again as they check in.

Sorry to keep bothering you for more testing, but I believe if you stop your container it will refuse to start up again and run the webui.

If that is the case can you edit the extra settings to :

--memory=8G --tmpfs /unifi/log:exec,uid=1000,gid=1000 --tmpfs /unifi/run:exec,uid=1000,gid=1000

and report back? I will update the guide above if that fixes it for you.

  • Replies 994
  • Views 185k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

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

  • PeteAsking
    PeteAsking

    8.3.32-unraid tag is tested and available for home users in production.

  • Yeah not sure what is happening with Linuxserver.io or their images. I switched to binhex for everything.   As he didnt have a unifi docker I had to make one with 11notes. 11notes has docker

Posted Images

2 minutes ago, PeteAsking said:

Sorry to keep bothering you for more testing, but I believe if you stop your container it will refuse to start up again and run the webui.

Looks like you're right. I see this in my docker logs after doing a stop/start:
> 12:21:46,686 |-ERROR in ch.qos.logback.core.FileAppender[sdwan_log] - openFile(logs/sdwan.log,true) call failed. java.io.FileNotFoundException: logs/sdwan.log (Permission denied)

After making the launch setting changes, it looks like the webUI launched. Devices are adopting as well.

No worries on doing more testing too!

  • Author
1 minute ago, tehg said:

Looks like you're right. I see this in my docker logs after doing a stop/start:
> 12:21:46,686 |-ERROR in ch.qos.logback.core.FileAppender[sdwan_log] - openFile(logs/sdwan.log,true) call failed. java.io.FileNotFoundException: logs/sdwan.log (Permission denied)

After making the launch setting changes, it looks like the webUI launched. Devices are adopting as well.

No worries on doing more testing too!

Pretty sure you will be fine now and back to normal. Just waiting for community apps to update so I can write up method 2 and let people test for a week or so.

-P

  • Author
29 minutes ago, tehg said:

Looks like you're right. I see this in my docker logs after doing a stop/start:
> 12:21:46,686 |-ERROR in ch.qos.logback.core.FileAppender[sdwan_log] - openFile(logs/sdwan.log,true) call failed. java.io.FileNotFoundException: logs/sdwan.log (Permission denied)

After making the launch setting changes, it looks like the webUI launched. Devices are adopting as well.

No worries on doing more testing too!

Hi I gave you the wrong values in error. This is not critical but when you get time can you change them to:

--memory=8G --tmpfs /unifi/log:exec,uid=99,gid=100 --tmpfs /unifi/run:exec,uid=99,gid=100

Thats what I will be using going forward. Reason is unraid does not support the nobody group for some reason.

Edited by PeteAsking

4 minutes ago, PeteAsking said:

Hi I gave you the wrong values in error. This is not critical but when you get time can you change them to:

Done. Looks good still!

Updated using method 1 and 10-unraid tag. Devices took a little longer to adopt than previous updates, but GUI is loading back up fine and everything seems to be working so far

  • Author

I have provided 2 methods to update to version 10 on page 32. If anyone testing has any issues just post here and I will assist. Both methods are tested by me, and fully supported. If anyone else can test that would help. Let me know what method you chose to test. Method 2 is advisable for anyone who cannot experience any downtime and needs to go back to an untouched docker running a previous version if anything fails during the update.

Edited by PeteAsking

Method 1 worked for me, everything is up and running.

Edited by Cambork

method 1 with --memory=8G --tmpfs /unifi/log:exec,uid=99,gid=100 --tmpfs /unifi/run:exec,uid=99,gid=100


from the start 2 devices adopted directly (1 was behind another switch, which seems funny), waiting for the rest as they popped up 1 by 1 was fun to see. )

no errors so far.

  • Author

Seems like everyone prefers method 1

2 minutes ago, RobertCajun said:

I know its the holidays and everyone is busy, but the Network Application has an update to 10.0.162

https://community.ui.com/releases/UniFi-Network-Application-10-0-162/2efd581a-3a55-4c36-80bf-1267dbfc2aee

(This is not a "WHERE IS MY UPDATE" post)

updates are followed via github 11 notes.

https://github.com/11notes/docker-unifi

a updated tag will become avilabe soon then theres testing.
also see docker tags as 11notes is failry fast to make updates but its slow to come to unriad due to testing and verfications.

https://hub.docker.com/r/11notes/unifi/tags

you can edit the tempatle and chagne the repo to the new tag to test:

example:
docker pull 11notes/unifi:10.0.160-unraid
change repo to 11notes/unifi:10.0.160-unraid

to test new version. bleeding edge...

6 minutes ago, bmartino1 said:

updates are followed via github 11 notes.

I'm aware, for some reason i thought 11notes was in this thread.

Apologies.

@PeteAsking

Just updated using method 1 but ran into a few issues. They were completely my own fault but could be avoided with a small edit.

When reconfiguring I copy/pasted the repo field shown below.

Screenshot 2025-12-25 at 11.40.50 AM.png

This resulted in some invalid spaces and several failed installs.

Perhaps you could edit the post to add a code line that will paste without errors?

  • Author
1 hour ago, wgstarks said:

@PeteAsking

Just updated using method 1 but ran into a few issues. They were completely my own fault but could be avoided with a small edit.

When reconfiguring I copy/pasted the repo field shown below.

Screenshot 2025-12-25 at 11.40.50 AM.png

This resulted in some invalid spaces and several failed installs.

Perhaps you could edit the post to add a code line that will paste without errors?

Ok! i just edited it for you.

  • 3 weeks later...

updated to 10 with method 1, no issues at all

I'm not sure this is the right place for this question, but maybe. I'm sick of getting invalid certificate warnings from my browser when connecting to the webui. My preference would be to access the ui via http since it's only exposed locally but that doesn't seem to be an option at all.☹️

I'm wondering if there is some way to make a self-signed certificate work???

2 hours ago, wgstarks said:

I'm not sure this is the right place for this question, but maybe. I'm sick of getting invalid certificate warnings from my browser when connecting to the webui. My preference would be to access the ui via http since it's only exposed locally but that doesn't seem to be an option at all.☹️

I'm wondering if there is some way to make a self-signed certificate work???

I made a custom DNS entry to point unifi:8443 to the web address of the user interface. I also uploaded the Unifi certificate to the windows certificate store and those errors have gone away for me

23 minutes ago, fat said:

I made a custom DNS entry to point unifi:8443 to the web address of the user interface. I also uploaded the Unifi certificate to the windows certificate store and those errors have gone away for me

Thanks. I don’t have any windows machines though so not sure that’ll do any good.

  • Author
2 minutes ago, wgstarks said:

So I can install a self-signed cert on the docker image?

No as mentioned you download the unifi cert to your local machine and install it an then create a dns entry like in the hosts file as was explained. Basically when you browse to the address the cert must match and also the pc you do this from must trust the cert. Thats about it.

6 minutes ago, PeteAsking said:

No as mentioned you download the unifi cert to your local machine and install it a then create a dns entry like in the hosts file as was explained. Basically when you browse to the address the cert must match and also the pc you do this from must trust the cert. Thats about it.

How would I download the cert from the unifi controller?

  • Author
5 minutes ago, wgstarks said:

How would I download the cert from the unifi controller?

I believe in your web browser you click on the security seal and there is a download certificate option in there somewhere. Maybe someone can confirm. I personally dont bother but pretty sure its something like that. Then install it and then add entry to hosts file so when you browse its address you go to matches the cert.

10 minutes ago, PeteAsking said:

I believe in your web browser you click on the security seal and there is a download certificate option in there somewhere. Maybe someone can confirm. I personally dont bother but pretty sure its something like that. Then install it and then add entry to hosts file so when you browse its address you go to matches the cert.

Thanks. I’m guessing this would need to be done for every machine on the LAN though. I might try adding a DNS A record for the unifi docker webUI to my DNS server and add the docker to my LetsEncrypt cert. I think I could use HA Proxy then and browsers would use the LE certificate.

I know its probably more complicated but would be network wide and a permanent solution if I can figure it out.

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.