February 13, 20251 yr ok for migration and restore purposes, that is partial contained within the unifi backup: https://help.ui.com/hc/en-us/articles/360008976393-UniFi-Backups-and-Migration The reason I mentioned lets encrypt as you will need to re-use and inform unifi to use the certs if you try to reuse the old certs / keys: https://community.ui.com/questions/Unifi-Migration-Best-Practices-related-to-Portal-and-SSL/c8b93a8b-8e5f-441c-a868-2cc2067b1ea6 Can it be done yes, but its easeier and better to resign new certs... As I believe, you are trying to suppress cert warning such as theses: on chrome going to the top: you can export the cert the new docker is using.. with the export you can import the cert into pfsense to re-register the website. review: https://www.ssldragon.com/how-to/install-ssl-certificate/pfsense/ This May also be of some assistance: unifi commands per video: https://docs.google.com/document/d/1pxq99pqZl0dC_j0AJIGu4cNWGfbSlYPMHdXuNZJLCjg/edit?tab=t.0 per unfi form you can use a script to backup your old containers certs.. # backup original keystore mv /var/lib/unifi/keystore /var/lib/unifi/keystore.`date "+%Y%m%d-%H%m%S"` # get the full cert chain cat /tmp/root.crt /tmp/Unifi.crt > /tmp/fullchain.crt # convert chain to appropriate format openssl pkcs12 -export -inkey /tmp/Unifi.key -in /tmp/fullchain.crt -out /tmp/cert.p12 -name unifi -password pass:temppass # import chain keytool -importkeystore -deststorepass aircontrolenterprise -destkeypass aircontrolenterprise -destkeystore /var/lib/unifi/keystore -srckeystore /tmp/cert.p12 -srcstoretype PKCS12 -srcstorepass temppass -alias unifi -noprompt # cleanup rm /tmp/root.crt /tmp/Unifi.crt /tmp/Unifi.key /tmp/fullchain.crt /tmp/cert.p12 But I'm not aware of a way to repoint and reuse docker in this way without having to pull data from the continer first to replace the /var/lib/unifi pathing... Thus I recomend using the LXC as you would have more granular control.
February 13, 20251 yr 6 hours ago, PeteAsking said: @beanmeister you realise you can just import a certificate to a machine right? ... Yes I did know you can import a certificate to a client browser. What I did not realize was that the Unifi controller, by default, comes with a certificate to allow you to just import and trust it. At least that is my understanding from your response. I just remember when the Unifi controller stopped supporting regular http, there were instructions for using LetsEncrypt which was more hassle then just issuing my own using pfSense. So I got the impression that I needed to configure the controller with a certificate to access the new https admin page. Anyway, I will give your import suggestion a try when I install the reborn docker, after migrating all my drives off reiserfs (yes, another long over due task that I have procrastinated from doing). Edited February 13, 20251 yr by beanmeister
February 13, 20251 yr Again, thank you @bmartino1 for all the links. I do believe from all your links, I will figure out the commands to get the Unifi controller to use my own certificates. I think the trick is to run those commands within the docker container since the Unifi controller is running inside the docker container. I can attest that the configuration backup file does not contain certificates information. I will definitely have to set up the Unifi reborn controller docker container with my certificates again. Kind of like moving the controller from one server machine to another. If I can't get it to work, then I will just fallback to importing the default certificate that comes with the Unifi controller like @PeteAsking suggested.
February 13, 20251 yr Hmm.. According to the Unifi GPT, the Unifi Console has a SSL certificate import in Settings->System. My current running version doesn't have this option. Can anyone running a recent version check if the option to import the SSL certificate is available in the Settings->System section of the console?
February 13, 20251 yr 2 hours ago, beanmeister said: Hmm.. According to the Unifi GPT, the Unifi Console has a SSL certificate import in Settings->System. My current running version doesn't have this option. Can anyone running a recent version check if the option to import the SSL certificate is available in the Settings->System section of the console? This is added in v4.1.9 of the unfi OS ... not unfi network application/server stack... The docker only runs the unifi network application which is what runs in the docker is different from the unifi consol os option you are looking for that runs on unifi hardware... Again I recommend you use the LXC as its is one time edits and I can guarantee updates and upgrade as the keystore doesn't change between releases... as the ssl certs and data runs within /var/lib/unifi/keystore I can't gurantee mainting old ssl certs within a docker upgrade path with the unifi reborn without making a docker path that may not survive tag version changes... (untested... I see no reason to implement the ssl certs here... unifi default docker and network generated are fine...) review: https://community.ui.com/questions/UniFi-Console-SSL-Certificate-Management/bec51e7c-6625-44e0-85b5-150f7026e75b Navigate to UniFi OS > Console Settings > SSL Certificate to check the status of your SSL certificate. AS the docker runs the network application only not unifi os... As Unifi themselves have yet to release there unifi os outside of there own arm hardware... There are no plans. Similar to some rewrites and api changes to unifi video to unifi protect, there are no plans for that software to leave unifi hardware... (this has caused isseus recenlty with older unfii hardware and how unifi security is running there network stack with EOL OS systems and databases...) You have to clarify that your are using the unifi network application only to get info only specfic data even on the unifi forum/ chatgpt ai etc...
February 13, 20251 yr Author 5 hours ago, beanmeister said: Yes I did know you can import a certificate to a client browser. What I did not realize was that the Unifi controller, by default, comes with a certificate to allow you to just import and trust it. At least that is my understanding from your response. Yes thats right, if it didnt used to come long ago with one, it was probably before my time. Good luck which ever direction you choose to go. Good luck with the reiserfs move. Just ask again if you are still stuck somewhere with something.
February 13, 20251 yr Yoo hoo! I am now reborn and running my own certificate! I just had to copy over my P12 certificate file and run the keytool command within the docker container to import it into the keystore. Thanks for the help everyone. I am still using the 7.5.187 version, but I did not wanted to migrate and upgrade the version at the same time. Will let this new container run for a week or so before upgrading the version. Now back to reiserfs migration.
March 2, 20251 yr maybe i missed it, but just in case i found a bug, none of the version 9 install from scratch. This includes the recommended home version of 9.0.114-unraid through 9.0.108-unraid. All of them do not create any files in their respective appdata folder, and give the same error (version is different of course): WARN Unable to load properties from '/usr/lib/unifi/data/system.properties' - /usr/lib/unifi/data/system.properties (No such file or directory) {"time":"2025-03-02T00:31:32.000Z","type":"INF","msg":"starting unifi (9.0.114)"} However, installing 8.5.6-unraid first and then changing the tag to 9.0.114-unraid, upgrades just fine.
March 2, 20251 yr Author 2 hours ago, rukiftw said: maybe i missed it, but just in case i found a bug, none of the version 9 install from scratch. This includes the recommended home version of 9.0.114-unraid through 9.0.108-unraid. All of them do not create any files in their respective appdata folder, and give the same error (version is different of course): WARN Unable to load properties from '/usr/lib/unifi/data/system.properties' - /usr/lib/unifi/data/system.properties (No such file or directory) {"time":"2025-03-02T00:31:32.000Z","type":"INF","msg":"starting unifi (9.0.114)"} However, installing 8.5.6-unraid first and then changing the tag to 9.0.114-unraid, upgrades just fine. I will double check tomorrow but I did test these versions from scratch and had no issues first time around. I will check again however.
March 3, 20251 yr Author On 3/1/2025 at 7:39 PM, rukiftw said: maybe i missed it, but just in case i found a bug, none of the version 9 install from scratch. This includes the recommended home version of 9.0.114-unraid through 9.0.108-unraid. All of them do not create any files in their respective appdata folder, and give the same error (version is different of course): WARN Unable to load properties from '/usr/lib/unifi/data/system.properties' - /usr/lib/unifi/data/system.properties (No such file or directory) {"time":"2025-03-02T00:31:32.000Z","type":"INF","msg":"starting unifi (9.0.114)"} However, installing 8.5.6-unraid first and then changing the tag to 9.0.114-unraid, upgrades just fine. I installed 9.0.108-unraid and saw the error but could not detect anything wrong with the image. It seemed to work correctly andhad no issues. I will ask what this error means but was there some sort of actual problem?
March 3, 20251 yr Author I also tested 9.0.114-unraid this morning and see the same error. However this only happens on first start, when there is no system.properties during the initial run. Making changes, stopping the docker and starting it again means the system.properties file is found and the error does not reoccur. Changes are saved and remembered normally. Can you clarify if there is an actual problem? This could just be how the unifi docker now works. I was unable to find an issue of any kind during testing (beyond the error on first run only that seems to resolve itself). I have tested multiple times and could not determine an issue. Kind regards P Edited March 3, 20251 yr by PeteAsking
March 3, 20251 yr 17 hours ago, PeteAsking said: I installed 9.0.108-unraid and saw the error but could not detect anything wrong with the image. It seemed to work correctly andhad no issues. I will ask what this error means but was there some sort of actual problem? unifi made some changes with old variables that get self corrected during the first time creation and/or a upgrade as older version had a different setting variable. You can see this error during first run of a unfi self test to rewrite and reload from a backup config or when unifi need to create a new file and settings for permission on read/wrtie have discrete access for the unifi settings/properties... This is a known error earlier since v5 and is apart of a standard unifi upgrade / reload of previous settings... https://community.ui.com/questions/system-properties-java-nio-file-FileSystemException-warning/5113fa8a-e61a-47aa-b15f-34fca9d7e89e https://community.ui.com/questions/cant-create-system-properties-file/4728cdd1-5ba9-4ab0-8ac2-7f0fe6a1d9e1 as the file may not exist yet and unifi is regenerating/ making new configs. it can safely be ignored IF THE APPLICATION IS FUNCTIONING! That said. It is still best to make and maintain a backup, as this can cause non saved options/settings at reboot...
March 3, 20251 yr Author Thanks. I believe its a non issue as I could detect no problems but will be happy for anyone to correct and let me know what isnt working.
March 17, 20251 yr Hi All, Just recently started to use this unifi controller. Since it uses so many common ports on my unraid, I thought I'd try to create an extra ip on my unraid br0 to run the controller from. It worked great, but has recently stopped working. The UI isn't responding. we had a power outage that briefly impacted the access points but not the controller server. The only error in the log: Quote Exception in thread "Thread-37" com.ui.analytics.ooOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO.C.OoOO: Failed to send crash reports or parse response at com.ui.analytics.ooOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO.C.super.A.o00000(HttpAnalyticsTransport.java:63) at com.ui.analytics.B.A.J.Ô00000(CrashReportBatchingClient.java:72) at java.base/java.lang.Thread.run(Thread.java:840) Caused by: java.net.SocketTimeoutException: Connect timed out at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:551) at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:602) at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327) at java.base/java.net.Socket.connect(Socket.java:633) at java.base/sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:304) at java.base/sun.net.NetworkClient.doConnect(NetworkClient.java:178) at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:533) at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:638) at java.base/sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:266) at java.base/sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:380) at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:193) at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1257) at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1143) at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:179) at java.base/sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1466) at java.base/sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1437) at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:220) at com.ui.analytics.ooOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO.C.super.new.o00000(HttpSender.java:47) at com.ui.analytics.ooOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO.C.super.new.Ó00000(HttpSender.java:34) at com.ui.analytics.ooOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO.C.super.A.o00000(HttpAnalyticsTransport.java:56) ... 2 more
March 17, 20251 yr 15 minutes ago, DizRD said: Hi All, Just recently started to use this unifi controller. Since it uses so many common ports on my unraid, I thought I'd try to create an extra ip on my unraid br0 to run the controller from. It worked great, but has recently stopped working. The UI isn't responding. we had a power outage that briefly impacted the access points but not the controller server. The only error in the log: did you edit or change the memory limits for the unifi docker. this is a java error OOM and a Thread memory leak... note teh extra parm should not go lower then 4G this application requires a min of 4 GB of ram... and did you change: as these are already at the min... reading the error more there seems to be a issue with your docker network and network communication: Quote Caused by: java.net.SocketTimeoutException: Connect timed out Possible Causes & Fixes Here’s what could be causing this and how to fix it: 1. Network Connectivity Issues The Unifi controller is trying to send crash reports or analytics data to an external server, but it cannot establish a connection. This could be due to: Internet connectivity issues on the host running Unifi. DNS issues preventing name resolution. Firewall or network rules blocking outgoing traffic. If using tailscale double check your ability to dns resolve inside a docker and on the host...
March 18, 20251 yr I have the Extra Param as 8G and the other mem settings at their default. I have alot of ram so I'm happy to increase it if you think that will help. when I start the container, there is a brief moment it will show the login in the webui before it crashes, so I think the networking is alright. It isn't using any VPN. I do use Adguard home for DNS resolution and block all attempts to talk to DNS servers on the internet. but that hasn't changed since it was working so I'm unsure.
March 18, 20251 yr Author 37 minutes ago, DizRD said: I have the Extra Param as 8G and the other mem settings at their default. I have alot of ram so I'm happy to increase it if you think that will help. when I start the container, there is a brief moment it will show the login in the webui before it crashes, so I think the networking is alright. It isn't using any VPN. I do use Adguard home for DNS resolution and block all attempts to talk to DNS servers on the internet. but that hasn't changed since it was working so I'm unsure. It sounds maybe like something corrupted somehow but I cant explain why. Are there any backups at all? If you dont take manual backups there might be some under appdata/unifi-controller-reborn/backup/autobackup can you check? @bmartino1do you know how to use these backups? They are .unf files. Edited March 18, 20251 yr by PeteAsking
March 18, 20251 yr 11 minutes ago, PeteAsking said: It sounds maybe like something corrupted somehow but I cant explain why. Are there any backups at all? If you dont take manual backups there might be some under appdata/unifi-controller-reborn/backup/autobackup can you check? @bmartino1do you know how to use these backups? They are .unf files. with unifi os yes not with the docker app: https://community.ui.com/questions/unf-controller-backup-file-format/3086d8d7-6be8-428f-8462-512179e53c39 https://community.ui.com/questions/how-to-open-see-unf-file/d60b4da3-f749-4636-9934-a76a6cd04045 could be ad guard blocking ubiquity and ui and unfi traffic.... the auto backup files can be used at the restore when controller first starts. https://community.ui.com/questions/restore-backups-from-unf-file/bbf49f4c-7a27-4eb3-b6a1-79074c3846cd Edited March 18, 20251 yr by bmartino1 typo - Data
March 18, 20251 yr Author Ok so maybe he can use this backup file if he makes a new container altogether. @DizRD can you check if you have any backups and then make a copy of a few of them. You may have to start again and restore from one of them if its broken. P
March 18, 20251 yr I didn't have a chance to make any backups, but I do see -rw-r--r-- 1 docker docker 26688 Mar 17 17:10 8.5.6.unf -rw-r--r-- 1 docker docker 4256 Feb 26 17:34 8.5.6_default.unf in var/backup of the volume path, but I haven't be able to access the ui since Feb 26, so I have no idea if either is valid, I'm tempted to just wipe and try again. I May try to restore that "8.5.6.unf" to a new install unless someone says not to. Edited March 18, 20251 yr by DizRD
March 19, 20251 yr Author 41 minutes ago, DizRD said: I didn't have a chance to make any backups, but I do see -rw-r--r-- 1 docker docker 26688 Mar 17 17:10 8.5.6.unf -rw-r--r-- 1 docker docker 4256 Feb 26 17:34 8.5.6_default.unf in var/backup of the volume path, but I haven't be able to access the ui since Feb 26, so I have no idea if either is valid, I'm tempted to just wipe and try again. I May try to restore that "8.5.6.unf" to a new install unless someone says not to. Can you send me a copy of this backup file for me to try work with and restore and or can you try restore from it? did you look under the autobackup folder? like if you do an ‘ls’ in that folder what was in there? I mean are you ssh into your unraid and going to the appdata location and the docker folder to check this? Edited March 19, 20251 yr by PeteAsking
March 19, 20251 yr I can try to share the file, but It since I only have 3 aps, it might be just better to start over and hope the same thing doesn't happen until I can get it backed up. I copied that unf file out, there were none in the autobackup folder. What's the best way to reset it to scratch so I can start over through unraid?
March 19, 20251 yr Author 34 minutes ago, DizRD said: I can try to share the file, but It since I only have 3 aps, it might be just better to start over and hope the same thing doesn't happen until I can get it backed up. I copied that unf file out, there were none in the autobackup folder. What's the best way to reset it to scratch so I can start over through unraid? You can delete the docker then delete anything left behind in the appdata folder on unraid and then create a new docker image. I would try restore with that file though. No harm and if it works at least you know its fixable. when its working, whatever you choose, stop the docker and start it a few times to make sure its running stable. Edited March 19, 20251 yr by PeteAsking
March 21, 20251 yr Did anyone face the issue that the Controller does not find firmware updates for devices? I have multiple Unifi 6 APs and a USW Flex Switch which all are running with an old firmware. When clicking "Check for Updates" for in Settings -> Device Firmware I get the result no updates avilable, my controller is able to reach the internet and correctly resolves a DNS entry to fw-update.ubnt.com. I don't get the issue.
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.