What should I do if I cannot start the Omada Controller in windows system (Controller 4.1.5 or above)
Suitable for Omada Controller V4.1.5 or above.
Sometimes we may face the issue that the Controller start page will not pop up automatically when double click the start icon, and we can’t start the Omada Controller successfully.
Generally speaking, a high java version (we should use java 8 to run the Controller) or the wrong java start path in windows REGEDIT may cause this issue, since we need to use the java runtime environment to start the Omada Controller. Here are some solutions to fixed this issue.
- Start the Omada Controller via “start.bat”
Go to the “bin” folder of the Omada Controller installation path and double click the “start.bat”, check if we can start the Controller successfully. The default path of “start.bat” is C:\Users\Administrator\Omada Controller\bin\start.bat.
- Start the Omada Controller via the CLI command.
- Open the CMD in windows system, use the cd command to log in to the “lib” folder of Omada Controller, such as cd C:\Users\Administrator\Omada Controller\lib.
- Use command java –jar “omada-start.jar” to start the Omada Controller.
- Modify the running path of java in registry editor of windows.
- Enter “win+R” to open the run shell. Input “regedit” to open the registry editor.
- Go to HKEY_CLASSES_ROOT\jarfile\shell\open\command to check the running data of the java running environment.
- We should use the java 8 (jre 1.8.0) to run the Omada Controller.
- Please make sure the jre version in the Value data is 1.8.0. If not, please install the java8 at first or change the value to the actual path of the java8 in your PC, such as “C:\Program Files\Java\jre1.8.0_271\bin\javaw.exe”.
- Please make sure it has –jar in the value data, or it will also cause the unsuccessful starting issue of Controller. (Sometimes the abnormal PC environment, such as abnormal file binding relationship may cause the regidit lack of the –jar command.)