Jacobalberty Unifi Download _TOP_
Lorie Silano
Ok. I was able to solve the immediate problem of accessing the unifi page. I deleted the keystore file from the unifi volume. the restarted. the setup page came up and i loaded a backup config file, and all is well.
The config.gateway.json should be placed in /unifi volume under /unifi/data/sites/[site name]/.
I have no idea how to show the running-config for the controller. For the access points and switches etc you can log in to SSH and use the CLI for this. For the controller, as far as I know, you can only check the settings in the GUI.
RUNAS_UID0 is set to false so the image will run as a special unifi user. Otherwise, it will run as root. The BIND_PRIV variable can be used to bind port below the 1024. But on some docker filesystems, this may not work.
Summary: I want to import my SSL Certificates generated with linuxserver/swag into UniFi controller on linuxserver/unifi-controller. However, it always uses the default self-signed root certificate instead of the ones that I save on the keystore.
And luckily the jacobalberty/unifi-docker docker images are appropriately taggedaccording to the Unifi Controller version, so we specify a particular versionfor the image. It gives you more control over your container then the Nginximage we use.
I found a pre-made container at linuxserver/unifi-controller. Running containers is simple on the Synology device, as I found out when I set up the Teslamate solution. This time, I could get the Unifi controller to run in a container, but it failed to store configuration data outside the container. Despite me following the guidance.
Then you need to specify a container definition. Provide a name, an image (I used jacobalberty/unifi:5.6.37 which was what I had running locally at the time). I provided the same Memory limits as I used for the task, because I planned to run only one container in this task.
1. start docker from within synology
2. go to register tab
3. in the search bar, i typed in jacobalberty and selected the Unifi (tag: latest)
4. next next next, waiting for the download to complete etc
5. go to Image tab, hit next and then apply (just leave everything as it is by default)
6. go to Container tab, i see that it is running.
Ok, so I get this thing running, then the Unifi releases an upgrade to the controller software and jacobalberty follows suit, what next? Mike would you consider a revisit to this article detailing the upgrade process?
These backup files are written to /unifi/data/backup within the container, and set to keep a fixed number of past backups. This location is bind mounted to a directory on the host filesystem to allow for them to be collected and published off device.
Open Docker Package. From the Docker Console, go to Registry and search unifi. Look for jacobalberty/unifi and select it, then click Download. You will be prompted to Choose Tag, select latest. Follow the instructions in the image below.
There is no official container image from Ubiquiti. But there are two popular unofficial images, one is from linuxserver.io (opens new window) and the other is from jacobalberty (opens new window).I have been using jacobalberty for years and never had issues with that one, so I'm sticking with that.
i seem to have run into an unclean shutdown after a power failure that I can't seem to recover from. I've tried running mongod --repair within my controller container but it doesn't seem to help. Any suggestions? I don't want to just blow away my unifi_mongo container, since I'm not sure if I'll lose all my configs.
It may seem backwards, but the deploy script needs to exist before obtaining the certificate. Read through this script carefully and adjust any domains and directories as needed. Create the file /opt/unifi/unifi-ssl-deploy.sh:
Go to the Image tab on the left side. Select jacobalberty/unifi. It may take a few minutes to download the image, you can see the progress on the right hand side. When the download is complete, select the image and click on Launch
I did try to run `keytool -v -list -keystore keystore -alias unifi` on the keystore file to check the content, but that results in some java error saying that the file has been tampered with or password is incorrect.
You try to verify this in Synology DSM? When you browse to your unifi controller you can click on the lock next to your address click on the certificate (valid) and verify the certificate expire date?
i get an error when exporting the cert
root@Nas:/usr/syno/etc/certificate/_archive/FuR4Fg# openssl pkcs12 -export -inkey privkey.pem -in fullchain.pem -out fullchain.p12 -name unifi -password pass:unifi
unable to load certificates
History: I fetched the unifi controller image from Docker Hub to my Synology Docker host. The container of the unifi controller runs properly if I attach it to the network of the host (not the default bridge). That blocks though multiple ports I need for other services (in the future). Thus it would be much easier to assign that unifi container with it's own designated IP --> 192.168.2.2 (than changing all the ports).
While you define the image (--name UnifiController jacobalberty/unifi) assign the freshly created macvlan (--network unifinet) to the container (UnifiController). It will grab the latest image respectively the latest Unifi Controller version available from Docker Hub.
I installed it using container station. If you download and run that and then search for UBNT containers you will find the jacobalberty/unifi:5.5.19 container. Install and run that and configure your ports and stuff. If you google search the container name you will find threads on the setup . It took several tries to get it running. But it has been stable since...
df19127ead