April 8, 20251 yr Author In firefox isnt there a little shield icon on the left of the address bar where you can disable advanced protection or something? Have you tried turning that off? @MrTroll
April 8, 20251 yr 3 hours ago, PeteAsking said: In firefox isnt there a little shield icon on the left of the address bar where you can disable advanced protection or something? Have you tried turning that off? @MrTroll I said I turned off enhanced protection. Do you guys use Firefox? Have you guys got the orange icon in chrome? The globe in the top left.
April 8, 20251 yr Author I dont have firefox easily to test, but regardless lets stick with what is confirmed working 100% with no delays for me right now. Can you confirm that you are only using this method externally to the site - eg: you understand you cant use unifi.ui.com while at home at the same site as the controller? This method is for remote access while not at home or on the business site. If you are using this while at home, nat reflection will prevent this from working on your firewall. Please check you are on an different internet connection with no vpn while using the remote access method. This is working for me in chrome with no issues. I can show a video if you need confirmation of this. - Pete @MrTroll Edited April 8, 20251 yr by PeteAsking
April 8, 20251 yr 4 hours ago, MrTroll said: I said I turned off enhanced protection. Do you guys use Firefox? Have you guys got the orange icon in chrome? The globe in the top left. What version of firefox are you running. I use it from time to time. It my go to when i have issues in chrome and edge. I prefer brave. This sounds more like a unbquity api issue... Better asked on unifi support forum... https://community.ui.com/questions/Firefox-is-blocking-access-to-CloudKey/e8404743-1ea9-4582-bb59-ae5a87601d65
April 8, 20251 yr also Firefox has its own privatized adblock built in... (this said per redit. its only with the new ui interface... if you go to setting and use the old interface doe it work???Also, assuming pihole is your primary dns...if pihole is setup correctly you may still need to edit the pihole ftl config to prevent firefox dnsftlconfig... adding BLOCK_ICLOUD_PR=true MOZILLA_CANARY=trueWhich will stop apple and firefox privatized dns routes using pihole... Edited November 29, 2025Nov 29 by bmartino1
April 9, 20251 yr 16 hours ago, PeteAsking said: I dont have firefox easily to test, but regardless lets stick with what is confirmed working 100% with no delays for me right now. Can you confirm that you are only using this method externally to the site - eg: you understand you cant use unifi.ui.com while at home at the same site as the controller? This method is for remote access while not at home or on the business site. If you are using this while at home, nat reflection will prevent this from working on your firewall. Please check you are on an different internet connection with no vpn while using the remote access method. This is working for me in chrome with no issues. I can show a video if you need confirmation of this. - Pete @MrTroll 13 hours ago, bmartino1 said: What version of firefox are you running. I use it from time to time. It my go to when i have issues in chrome and edge. I prefer brave. This sounds more like a unbquity api issue... Better asked on unifi support forum... https://community.ui.com/questions/Firefox-is-blocking-access-to-CloudKey/e8404743-1ea9-4582-bb59-ae5a87601d65 I'm only trying to access unifi.ui externally, I don't ever use a vpn or anything of the sort. I am running whatever the the latest version of firefox is. I was considering asking on the unifi forum but I came here first cause I get the feeling they're gonna shift the blame onto the somewhat off textbook implementation. Bit of a wild card line of questioning but when you guys access your unifi network server remotely does the IP logged match the wan IP of that connection? Edited April 9, 20251 yr by MrTroll Clarity
April 9, 20251 yr hard to assit if you don't give use the data... realy need to know what firefox verion your runnign to test... that said windows firewall and firefox has stuff going on... firefox esr lattest version works fine... for the ip kinda.. its uses an api.. but yes the wan ip should show... unfi site magic is fickle... there was a major ISP outage for me ealrier a fiber line was cut... but yes this works fine in firefox...
April 9, 20251 yr Author I will install firefox somewhere and post a video of what happens for me from an external location later today so you can compare. can you not also check this from your phone on mobile data using safari and rule out this being your local pc or something Edited April 9, 20251 yr by PeteAsking
April 9, 20251 yr @bmartino1 Latest version It failing to load It failing to load with every extension disabled, enhanced security disabled, cache cleared. It loading with the globe icon on chrome. The source IP in my admin acitity log always resolves as coming from 104.30.144.186 or 104.30.144.187, no matter the actual WAN IP of the network i'm on. The logs from when Firefox attempts to load. I find it odd that the same IP addresses show up in the log. Edited April 9, 20251 yr by MrTroll
April 9, 20251 yr Author @MrTroll Ok so no video needed. I tested on a remote pc with firefox and it also had edge. on firefox it does not load. I get that same error in the logs from IP 104.30.148.xxx range. tried in edge on the same pc directly after and it worked and opened no issue. So what must I do about that? Unifi I guess dont make their site work with firefox.
April 9, 20251 yr 5 hours ago, bmartino1 said: I cant reproduce this with the lxc nor the unifi docker running 11notes/unifi:9.0.108-unraid while i have seen this error: this usuialy meant unif api is having a hard time talking back to your public ip. You may be on cgnat. also you are runnign the docker in docker bridge... 172.17.0.2 is most likly the unriad docker ip that is assigned via your docker bridge... docker network inspect bridge to check the default docker bridge you should see unifi reborn or the name of the docker under container... 104.30.144. 186-187 is either unifi or your public ip ... as stated in step 2 Please set it to a lan ip and test again... you should really have this in a macvlan lan subnet ip as you appear to be also fighting unriad docker network nat with the stun service... unraid docker doesn't forward all types of traffic... Your losing the multicast/broadcast that stun uses over the bridge interface... unfi need its own lan identity it is networking software... review this post on unraid and docker networks... while firefox is presenting your with problems and while it works on chrome... I believe you have a network misconfiguration at the docker level... https://en.m.wikipedia.org/wiki/STUN your stun error are a different issue from your unifi site magic api connection... also did you try going into unifi and change the setting to use the old User interface??? I am running the latest stable build 11notes/unifi:9.0.114-unraid. I am not on a cgnat, I have specifically asked my ISP to turn that off. I was previously running everything as you mentioned but changed it back after nothing improved. However just for you i'll do it again. Here is my docker network which I never swapped back because it meant taking down all of my containers. Here's the previously mentioned hostname I know what my public IP is 104.30.144.186-187 not my public IP and PeteAsking also has it show up in his logs. UniFi has no issues logging my LAN ip correctly from when i'm connecting within my network. I have set all the networking up the way you have asked for the second time. The only thing that changes is in the logs it reports the set IP. Setting unifi to the old interface forces me to load it via a different URL that takes some time to try and load then ultimately fail. I don't know if you missed it but the author of this thread has ran into the EXACT same issue upon doing his own testing with the same IP showing up in his logs also. Are you then not implying that hes doing it wrong? I don't know if you and him are a team or something maybe you already know this. I want to restate that UniFi loaded on firefox previously with all my default networking as per Pete's own recommendation. However this issue started quite some time ago so its hard for me to nail down what version it was on.
April 10, 20251 yr Author @MrTroll we are not a team. I made this docker for myself and to share with other people that have a similar need to me. I have no control over what other people post. They have a right to post whatever they want. I dont interfere with that. I only speak for myself. He is promoting you use his maintained lxc container instead of this docker container. Again, nothing to do with me and I cant comment. If it is a solution and it works better feel free to use it. I have never used it personally and wouldnt know. I do concede that multiple solutions can meet different needs of users so it is possible an alternative would work better for you. But I again stress this is nothing to do with me. I always answer your questions and anyone else's independently on my own. Regards when the issue started - this website is maintained by unifi. They could have changed something anytime and we would not know. I also cant control anything on unifis website or explain why they have issues with firefox. It seems to work fine with edge and chrome. Probably that accounts for 99% of their users and they only test with that. I suggest you just use chrome or edge if it works for you and not worry about it. Nobody except unifi can fix this. I cant change how unraids docker networking functions and I cant change how the software provided by unifi works. I can provide only the setup and install support of their image into an unraid format works. So I am quite limited in what I can do. Ultimately this problem does not seem to be one that I have control over as components being discussed I cant change. Edited April 10, 20251 yr by PeteAsking
April 10, 20251 yr 14 minutes ago, PeteAsking said: @MrTroll we are not a team. I made this docker for myself and to share with other people that have a similar need to me. I have no control over what other people post. They have a right to post whatever they want. I dont interfere with that. I only speak for myself. He is promoting you use his maintained lxc container instead of this docker container. Again, nothing to do with me and I cant comment. If it is a solution and it works better feel free to use it. I have never used it personally and wouldnt know. I do concede that multiple solutions can meet different needs of users so it is possible an alternative would work better for you. But I again stress this is nothing to do with me. I always answer your questions and anyone else's independently on my own. Regards when the issue started - this website is maintained by unifi. They could have changed something anytime and we would not know. I also cant control anything on unifis website or explain why they have issues with firefox. It seems to work fine with edge and chrome. Probably that accounts for 99% of their users and they only test with that. I suggest you just use chrome or edge if it works for you and not worry about it. Nobody except unifi can fix this. I cant change how unraids docker networking functions and I cant change how the software provided by unifi works. I can provide only the setup and install support of their image into an unraid format works. So I am quite limited in what I can do. Ultimately this problem does not seem to be one that I have control over as components being discussed I cant change. Oh yeah 100% man I know you've got no control over what other people post, unifi etc. I'm surprised that no one else has had this issue recently since I figure there's a pretty big overlap between Firefox users and UniFi users. I appreciate you testing the issue and ultimately sharing the same behaviour helps to make me feel not insane. I appreciate everyone's help here.
April 10, 20251 yr 2 hours ago, MrTroll said: I am running the latest stable build 11notes/unifi:9.0.114-unraid. I am not on a cgnat, I have specifically asked my ISP to turn that off. ... ... I don't know if you missed it but the author of this thread has ran into the EXACT same issue upon doing his own testing with the same IP showing up in his logs also. Are you then not implying that hes doing it wrong? I don't know if you and him are a team or something maybe you already know this. I want to restate that UniFi loaded on firefox previously with all my default networking as per Pete's own recommendation. However this issue started quite some time ago so its hard for me to nail down what version it was on. @MrTroll I can't help thoese who don't want help... nore how things are taken from others... Just because cgnat is not being applied (I'm on cgnat too and paying for a static IP) doesn't mean cgnat routeing on the ISP is not causing issues... An additional setting in docker may need enabled... "Host access to custom" This is need to allow additional network types that may be blocked by stun. Regarding the other post... No, I saw it... the post where he tested. We have widely different test and hardware requirements... I still have a unfi tech support access and can send thing to unifi via my work with other ISPs... This said. While I'm not afraid to making docker template edits to the template and test... From the forum 1st posts, to testing and moving on with its evolution.... as said on this forum... PeteAsking doesn't want to make some of the edits... (27 pages worth on this topic you want me to link them???)... as explained and pointed in other posts... Besides, I'm just posting unraid best practices via the docs... Using info obtained from the forum and tests myself... Theses are generic troubleshooting steps and settings. Also found In this forum topic, many other unifi users have had similar issues and solved them. Theses were the solutions... I acknowledge and 100% believe this is a ubiquity issues and possibly something to do with Firefox internal web behavior with the geko engine... Agreed, its strange that Chromium web engine works... Unifi had a major api website update that affected site magic and the transaction to network v9 problems have been on going before December of last year... Also why I pointed you to the ubiquity forum... @PeteAsking I was kinda forced to make and maintain a unraid lxc template... Per ICH777 as I could test with actual hardware and he didn't want to maintain it as he couldn't test it... Sometimes more granular control is needed, thus I mentioned the LXC version. Something else you could test... As I said I can't reproduce this. Even in bridge mode... Its also clear that @MrTroll is not following the information given, I can't help how you read interact of follow the posts... I'm not advocating anything. You don't want my help say something...
April 10, 20251 yr 3 minutes ago, bmartino1 said: @MrTroll I can't help thoese who don't want help... nore how things are taken from others... Just because cgnat is not being applied (I'm on cgnat too and paying for a static IP) doesn't mean cgnat routeing on the ISP is not causing issues... An additional setting in docker may need enabled... "Host access to custom" This is need to allow additional network types that may be blocked by stun. Regarding the other post... No, I saw it... the post where he tested. We have widely different test and hardware requirements... I still have a unfi tech support access and can send thing to unifi via my work with other ISPs... This said. While I'm not afraid to making docker template edits to the template and test... From the forum 1st posts, to testing and moving on with its evolution.... as said on this forum... PeteAsking doesn't want to make some of the edits... (27 pages worth on this topic you want me to link them???)... as explained and pointed in other posts... Besides, I'm just posting unraid best practices via the docs... Using info obtained from the forum and tests myself... Theses are generic troubleshooting steps and settings. Also found In this forum topic, many other unifi users have had similar issues and solved them. Theses were the solutions... I acknowledge and 100% believe this is a ubiquity issues and possibly something to do with Firefox internal web behavior with the geko engine... Agreed, its strange that Chromium web engine works... Unifi had a major api website update that affected site magic and the transaction to network v9 problems have been on going before December of last year... Also why I pointed you to the ubiquity forum... @PeteAsking I was kinda forced to make and maintain a unraid lxc template... Per ICH777 as I could test with actual hardware and he didn't want to maintain it as he couldn't test it... Sometimes more granular control is needed, thus I mentioned the LXC version. Something else you could test... As I said I can't reproduce this. Even in bridge mode... Its also clear that @MrTroll is not following the information given, I can't help how you read interact of follow the posts... I'm not advocating anything. You don't want my help say something... I have done everything you asked man multiple times. Here's it enabled as requested. Heres the logs after enabled the setting.
April 10, 20251 yr Author 1 hour ago, MrTroll said: Oh yeah 100% man I know you've got no control over what other people post, unifi etc. I'm surprised that no one else has had this issue recently since I figure there's a pretty big overlap between Firefox users and UniFi users. I appreciate you testing the issue and ultimately sharing the same behaviour helps to make me feel not insane. I appreciate everyone's help here. I think the main issue is nobody turns on remote management as it defeats the entire point of self hosting (you control everything) and there is zero reason to use it once you have wireguard in place. Its just easier to have wireguard and use the unifi app on my phone and nothing ever touches unifis servers. Remote management is your network is one breach away from being controlled and the security is all based on how much effort unifi put in. This is most likely why you dont find a lot of people in this situation - Its not because they dont use firefox. Its because you are like the 0.0001% of people using remote management. We are putting value on privacy and security over this unifi feature that isnt really necessary. Edited April 10, 20251 yr by PeteAsking
April 10, 20251 yr 7 minutes ago, PeteAsking said: I think the main issue is nobody turns on remote management as it defeats the entire point of self hosting (you control everything) and there is zero reason to use it once you have wireguard in place. Its just easier to have wireguard and use the unifi app on my phone and nothing ever touches unifis servers. Remote management is your network is one breach away from being controlled and the security is all based on how much effort unifi put in. When I first setup this container all I had was a switch and AP I also had a server running unraid so I figured hosting it on the computer thats on 24/7 was a solid idea. Later I bought a UXG Lite when it was on sale which I kinda regret cause ultimately for me i'd prefer the build in cloud stuff the more expensive routers have. But it still works out for me to be able to monitor my network remotely and with a really nice UI. So the data security standpoint of self hosting never really entered my calculus, its honestly a use case I hadn't thought of. It makes sense when I think about it, most people have way more baller hardware than me which all have build in cloud key hardware. So they would only seek something like this out to maintain better data hygienics.
April 19, 20251 yr currently using 11notes/unifi:8.5.6-unraid, if i move to unifi:9.0.114-unraid will it auto upgrade? or shall i backup my config and restore it?
April 19, 20251 yr 2 hours ago, bigup said: currently using 11notes/unifi:8.5.6-unraid, if i move to unifi:9.0.114-unraid will it auto upgrade? or shall i backup my config and restore it? Its always recommended to backup before any update. If the config isn't that important then you can wing it and just start from scratch if you loose anything but if you don't feel like doing that, make a backup.
April 19, 20251 yr 3 hours ago, bigup said: currently using 11notes/unifi:8.5.6-unraid, if i move to unifi:9.0.114-unraid will it auto upgrade? or shall i backup my config and restore it? it will not auto change tags. Changing a tag will install that unraid application version. While, I have not had a issue of changing tag with acts as a update. a Warning and caution... What happens is at the internal docker level, it will pull the underlying changes and updates. and it will reuse any files/configs that are already mapped via the volumes. Since this replaces and any all non mapped folders and files, any update that you don't have a backup of a file/config is corrupt after the new docker tag pull and underlying docker sub layer changed applies... If you have a missing config and changes... You will need to use the unfi restore to restore your configurations... *This is why we recommend running a unfi backup before implementing tag changes. In my experience, changing tags didn't result in a loss of data. I see no issues doing so. just be warned that it could happen...
April 19, 20251 yr Author Although upgrading is generally safe you should assume any time you upgrade you will lose everything and be required to restore from backup. If you are not in a position to be able to restore from backup then the official line from me as the maintainer is do not update. Simple as that.
April 24, 20251 yr Hi, First time posting in forums as I'm new unraid user having just built my first NAS server. Just wanted to say thanks and kudos to all involved for creating, maintaining and supporting this app, it's definitely appreciated as the unifi controller environment seems to be a moving target, made especially harder for those of us self-hosting! I was coming from a Raspberry Pi 5 instance of the unifi network app (jacobalberty/unifi:v9 at v9.0.108) and having spent a few hours in frustration trying to get the linuxserver version running with a separate mongo db, gave up and found this one, which worked straight away. However, being an older version meant my restore didn't work, but it was a simple enough task to update to the latest most recent 9.0.114 tag and the restore worked fine. Previously I'd always just used docker host mode networking out of laziness, but seeing the recommendation to stick with bridge mode and use inform host meant I was out of excuses and it was a two minute job to get this working. Thanks again! 🙇 Edited April 24, 20251 yr by si-fi
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.