This article describes the possible causes and solutions for when the UniFi controller fails to start when opened. Use the table of contents below to navigate through the different causes.
Table of Contents
- Windows profile's username has special characters
- One or more ports needed by UniFi are being used by other programs
- Java incompatibility (Javaw.exe is missing)
- Java incompatibility with old firmware version (2.2.5 or earlier)
Windows profile's username has special characters
1. The controller's database (mongo) will not start because it cannot find a file.
2. The solution is to change the username and make sure it has no special characters (including accents, for example: á, ë, ì, ô, ç, ã).
One or more ports needed by UniFi are being used by other programs
1. Take a look at <unifi_base>/logs/server.log
The location <unifi_base> will vary depending on your operating system. See this article for more information.
2. Most likely, there will be an ERROR similar to this:
[2011-06-01 22:09:14,145] <UniFi> ERROR StandardServer - StandardServer.await: create: java.net.BindException: Address already in use: JVM_Bind at java.net.PlainSocketImpl.socketBind(Native Method) ...
3. Change the ports used by UniFi controller, as seen in this article: UniFi - Change Default Ports for Controller and UAPs
Java incompatibility (Javaw.exe is missing)
Ensure that the correct Java version is installed on the machine (32 / 64bits). Java version should correspond to browser (Chrome is 32-bit browser).
Java incompatibility with old firmware version (v2.2.5 or earlier)
- If using UniFi 2.2.5 or earlier, make sure that Java 6 is installed on your computer, since Java 7 is not compatible.
- Ensure that the correct Java version is installed on the machine (32 / 64bits).
- 64-bit based Windows 7 & 8 machines must use a 64-bit web browser and Java install.
It is recommended to always upgrade to the newest firmware release to prevent security issues.