8 minutes ago, PeteAsking said:

Unraid is not compatible with this type of image which is why they were never brought over, and they dont work. We tried to get them working but was impossible due to how unraid dockers work.

So I shouldn't be running the adguard home image I got working? lol

1 minute ago, RobertCajun said:

So I shouldn't be running the adguard home image I got working? lol

Feel free to get them working on unraid if you want. Then explain how you did it. The images are there for you to use.

Edited July 8, 20251 yr by PeteAsking

I'm on 7.2.92, no issue setting up as a fresh install. I cannot get the GUI to load for the life of me.

19 minutes ago, tristanhill85 said:

I'm on 7.2.92, no issue setting up as a fresh install. I cannot get the GUI to load for the life of me.

I mean I know Im pretty good. But Im not that good. you have to actually tell me something about your setup.

Like have you checked its in bridge mode and if your unraid server ip was 192.168.56.4 (example) can you open a browser and access https://192.168.56.4:8443/

As an example?

Try in a private browser window and the usual stuff. Also that version would not be a fresh install as its not the tag selected when installing fresh right now. I just checked.

Edited July 11, 20251 yr by PeteAsking

Hi @PeteAsking ,

I am using your docker for about a month now. Simply amazing, thanks! Going further I want to try out API integrations and therefore wanted to create an API key. Reading the UI documentation about that, this should be done via Settings -> Advanced -> Control plane -> Integrations.

But I simply do not have the option "Integrations". For me, I do have Settings -> System and the Control plane only shows "General" and "Backups". No "Integrations" tab.

Am I blind or am I missing something? Could you help?

Thanks & Regards,

Stefan

1 hour ago, JayDee73 said:

Hi @PeteAsking ,

I am using your docker for about a month now. Simply amazing, thanks! Going further I want to try out API integrations and therefore wanted to create an API key. Reading the UI documentation about that, this should be done via Settings -> Advanced -> Control plane -> Integrations.

But I simply do not have the option "Integrations". For me, I do have Settings -> System and the Control plane only shows "General" and "Backups". No "Integrations" tab.

Am I blind or am I missing something? Could you help?

Thanks & Regards,

Stefan

The API does not talk to your docker container directly. It requires you to create a link to allow unifi direct control over your self hosted container using the remote management option and signing up on and doing all the linking with their website. Once you can remotely access your container via https://unifi.ui.com and control your unifi docker remotely,as they have a link and can control it, then the api is https://unifi.ui.com/api

Most of us do not use this feature as the entire point of self hosting is to control things yourself and not give a 3rd party keys to your box, however its totally up to you. I cant really help much since I dont use that feature myself and have zero interest in it.

• P

On 7/11/2025 at 7:00 PM, PeteAsking said:

I mean I know Im pretty good. But Im not that good. you have to actually tell me something about your setup.

Like have you checked its in bridge mode and if your unraid server ip was 192.168.56.4 (example) can you open a browser and access https://192.168.56.4:8443/

As an example?

Try in a private browser window and the usual stuff. Also that version would not be a fresh install as its not the tag selected when installing fresh right now. I just checked.

I cannot access at https://x.x.x.216:8443/ in bridge mode via browser including private.

I do get this error on start.

WARN Unable to load properties from '/usr/lib/unifi/data/system.properties' - /usr/lib/unifi/data/system.properties (No such file or directory)

As for the fresh install, as opposed to importing my settings from a very old docker, I was just going to readopt these APs and configure without backup. Unless you suggest otherwise. I'm coming from brettm357 docker running 7.2.92 in host mode.

14 minutes ago, tristanhill85 said:

I cannot access at https://x.x.x.216:8443/ in bridge mode via browser including private.

I do get this error on start.

WARN Unable to load properties from '/usr/lib/unifi/data/system.properties' - /usr/lib/unifi/data/system.properties (No such file or directory)

As for the fresh install, as opposed to importing my settings from a very old docker, I was just going to readopt these APs and configure without backup. Unless you suggest otherwise. I'm coming from brettm357 docker running 7.2.92 in host mode.

Can you explain why you have blanked out your internal ip address? Does unraid run internally on x.x.x.216 or is this some sort of public ip?

11 minutes ago, PeteAsking said:

Can you explain why you have blanked out your internal ip address? Does unraid run internally on x.x.x.216 or is this some sort of public ip?

Ok, nevermind, after searching the forums I believe I had to just remove the appdata folder and reinstall fresh. All working as intended now. Thank you for this docker!

Does this docker container support tailscale integration? It seems to not have the correct privileges but instructions say to stay away from the UID and GID.

I disabled unifi remote management, accessed via tailscale subnet, and manually configured the iOS app with IP and U/P.

Edited July 14, 20251 yr by tristanhill85

26 minutes ago, tristanhill85 said:

Does this docker container support tailscale integration? It seems to not have the correct privileges but instructions say to stay away from the UID and GID.

I disabled unifi remote management, accessed via tailscale subnet, and manually configured the iOS app with IP and U/P.

If you are an expert you can change whatever you want. I just dont provide any help or assistance since its beyond the scope of basic support and setup. If you want to fiddle around with settings that change how it works thats fine because you = the support at that point.

9.3.43 Dropped

https://community.ui.com/releases/UniFi-Network-Application-9-3-43/498d71da-c9e9-47d7-8d15-a6d1472239e1

ninja edit: this isn't me demanding an update, just alerting to the update

Edited July 15, 20251 yr by RobertCajun

5 hours ago, RobertCajun said:

9.3.43 Dropped

https://community.ui.com/releases/UniFi-Network-Application-9-3-43/498d71da-c9e9-47d7-8d15-a6d1472239e1

ninja edit: this isn't me demanding an update, just alerting to the update

Alpha testers on tag unifi:9-unraid will have already been pushed an update for them to test/break their install.

Upgraded from 9.2-unraid tag to 9.3-unraid no issues so far, all UniFi devices connected. The updated Client Devices page is nice.

Interesting development from UI to release UniFi OS Server gives more features than regular self hosted controller

https://community.ui.com/releases/UniFi-OS-Server-4-2-23/21df94e9-55d6-4298-b849-fbef3e3b1dd6

UniFi OS Server allows users to run the full UniFi OS experience on their own Windows, macOS, or Linux hardware. Initially, it will support the UniFi Network and InnerSpace application.

 

Benefits of UniFi OS Server (Compared to Self-Hosting Only the Network Application)

Opting for a UniFi OS Server provides several advantages over simply running the standalone UniFi Network application:

• Full UniFi OS Experience: Enjoy the comprehensive and unified UniFi OS interface, providing a consistent management experience similar to that found on official UniFi Consoles.

• Future-Proof Platform: Built on the UniFi OS foundation, this self-hosted solution is better positioned to support new features, updates, and upcoming UniFi applications, offering greater extensibility.

• Unified Updates: Manage updates for the underlying UniFi OS and its applications through a more integrated process

Great. I cant wait to be required to stand up and run an entire server just to setup a few access points and some switches.

31 minutes ago, PeteAsking said:

Great. I cant wait to be required to stand up and run an entire server just to setup a few access points and some switches.

Hopefully it can be run in docker which is what many are calling for on the forum. If that is the case it could replace the current controller and give a more feature rich experience without too much hassle it would be good

Unrelated I run the Unraid 9 tag and have just updated. Everything has been running fine for around 30 minutes at this stage

Tried updating my image to the latest stable per the OP, 9.2.87-unraid but I kept getting an error that the image was not available. For some reason unraid was appending :latest to the end of the image tag string even though that wasn't listed in my repository string (I tried it again after double checking). Was coming from 9.1.120-unraid.

In any case, I updated to 9.3.43-unraid instead just fine. No complaint just an FYI in case someone else runs into it.

5 hours ago, rgreen83 said:

Tried updating my image to the latest stable per the OP, 9.2.87-unraid but I kept getting an error that the image was not available. For some reason unraid was appending :latest to the end of the image tag string even though that wasn't listed in my repository string (I tried it again after double checking). Was coming from 9.1.120-unraid.

In any case, I updated to 9.3.43-unraid instead just fine. No complaint just an FYI in case someone else runs into it.

Interesting. Unsure why unraid would do that. At any rate that tag is about to be the latest stable so it wont matter in your case.

Upgrade to 9.3.43-unraid is now supported for all users.

Hi guys,

I am using 9.3.43 of this controller, so it's the newest version. Although the same happens with older versions. I'm not even sure it's related to the container and/or version at all.

My "remember me" Login-Cookie simply doesn't work. I've tried multiple browser (Brave, Chrome, Safari), so I don't think it's browser-related. I am login into the Controller with Checkbox "remember me" activated. But as soon as I close the browser and re-launch it, I have to login again.

Is this expected? A "remember me" should at least save my login credentials for several hours, if not days, right? Is this something Container related?

Regards,

JD

@PeteAsking - Just wanted to say thanks for creating this docker app. So much easier to setup compared to others and I was able to restore the backup from my failing physical cloud key G2 to this image and it just worked.
Remembering my user ID & password was a different issue, but I got there in the end.

On 7/27/2025 at 5:02 AM, JayDee73 said:

Hi guys,

I am using 9.3.43 of this controller, so it's the newest version. Although the same happens with older versions. I'm not even sure it's related to the container and/or version at all.

My "remember me" Login-Cookie simply doesn't work. I've tried multiple browser (Brave, Chrome, Safari), so I don't think it's browser-related. I am login into the Controller with Checkbox "remember me" activated. But as soon as I close the browser and re-launch it, I have to login again.

Is this expected? A "remember me" should at least save my login credentials for several hours, if not days, right? Is this something Container related?

Regards,

JD

Unable to recreate issue. Works for me. Assuming it is specific to you and no longer investigating. Create a new VM and install a browser like edge/firefox without changing any settings at all and retest if you want to investigate further.

23 hours ago, PeteAsking said:

Unable to recreate issue. Works for me. Assuming it is specific to you and no longer investigating. Create a new VM and install a browser like edge/firefox without changing any settings at all and retest if you want to investigate further.

Thanks for testing it yourself, PeteAsking. I really appreciate that!

I've digged a little deeper into this. Turns out, my Nginx Proxy Manager settings for the Controller domain were responsible for not saving the cookie. I am not finally sure which setting it was, but now it seems to work as expected.

Thanks again!

14 hours ago, JayDee73 said:

Thanks for testing it yourself, PeteAsking. I really appreciate that!

I've digged a little deeper into this. Turns out, my Nginx Proxy Manager settings for the Controller domain were responsible for not saving the cookie. I am not finally sure which setting it was, but now it seems to work as expected.

Thanks again!

How does you settings look like now? I'm having the same issue and also uses NPM...