New UniFi OS Server Password Problem

Networking & Firewalls
1

Decided to install the new OS server. Created a list of instructions with links. Also decided not to rip out the Unifi Controller that’s located on a Debian 12 ssd. Installed it on another copy of Debian 12 ssd.

Got stuck trying to install the OS file. Found out that the instructions at Cross Talk Solutions had changed recently by UniFi. No longer required to add the word “install”. Then the installation finished with no problem.

Had an issue on the home page where it indicates to upload the backup unf file from my existing network controller. Clicked the link which changed pages and could not find a place to upload it.

Decided to just do it once the controller was loaded. No user name box. Just a password box. Indicated 12 character minimum. My current system has the usual username and password which is just 7 characters long. Entered a new password for the new OS and the home screen came right up.

Uploaded my unf backup. Within few minutes my single AP was discovered along with all mobile devices.

This is where everything went sideways. I logged out not knowing which password would get me back in. Turned out…neither. Spent an hour or more trying to uninstall the Unifi OS, container, and anything relevant to the new install. If anyone knows a procedure for doing a clean uninstall to start over please respond. I formatted the disk and installed Debian 13 for another try tomorrow.

Also what to do with the password situation. I’m thinking using the 12 character password they require, then uploading the backup, and finally changing the password from the uploaded one to the one used that got me logged in originally. By the way this is local…I’m not using an email address.

Thanks, Gerald

2

I know this is not answering your question directly but it seems to me there is a simpler way of approaching Unifi controller deployment instead of trying to install/uninstall the package on the host OS. Have you thought about using the docker version of unifi controller? It would make situations like this a lot easier.

This is the one I use:

3

Thanks for the response. I have had a Unifi network controller already on another ssd. I only recently found out about the OS version in a container while updating my current version. It appears to me Unifi is going to abandon the controller version eventually. So where is linuxserver/docker going to get updated controllers from when Unifi stops producing them?

I’ve been using unifi controller and their AP’s for 7 years with no problems at all. The updates are easy using Glenn R’s scripts. After the update I log out and shut down the OS. Move my cables back to one of 11 ssds until the next time. The single AP with its two wifi networks and vlan work perfectly following Tom’s YT videos. So the current system is stable and the new podman container version has some bugs.

4

You are right and it’s my fault for using the unifi controller and the unifi network application terms interchangeably which obviously they are not. The link I provided above is the docker container for Unifi’s network application so updates will follow the Unifi’s release cadence for their Unifi OS Network Application.