I have got the exact same message, but controller is not starting anymore and keeps offline
I have got the exact same message, but the controller is not starting anymore
I did the update about 15 minutes ago, and the controller is starting OK but the Access Point is showing as disconnected. I had to pull the power (ethernet cable) to the AP and then it reconnected a minute later. Odd.
Add-on version: 6d21410
You are running the latest version of this add-on.
System: Debian GNU/Linux 10 (buster) (amd64 / qemux86-64)
Home Assistant Core: 2021.4.6
Home Assistant Supervisor: 2021.04.0
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executingâŠ
Log level is set to DEBUG
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] unifi.sh: executingâŠ
/var/run/s6/etc/cont-init.d/unifi.sh: line 63: ROOT_CHAIN: readonly variable
[cont-init.d] unifi.sh: exited 1.
[cont-finish.d] executing container finish scriptsâŠ
[cont-finish.d] 99-message.sh: executingâŠ
Oops! Something went wrong.
We are so sorry, but something went terribly wrong when
starting or running this add-on.
Be sure to check the log above, line by line, for hints.
Something wrong with Unifi controller?
Add-on version: 0.21.0
You are running the latest version of this add-on.
System: Home Assistant OS 5.13 (armv7 / raspberrypi4)
Home Assistant Core: 2021.4.6
Home Assistant Supervisor: 2021.04.3
Looks like its starting, but cannot access the web ui. With or without SSL
[16:49:16] INFO: Starting the UniFi ControllerâŠ
2021-05-01 16:49:18,347 main ERROR Error processing element InMemoryAppender ([Appenders: null]): CLASS_NOT_FOUND
2021-05-01 16:49:19,581 main ERROR Unable to locate appender âInMemoryAppenderâ for logger config ârootâ
Does anyone know how you add ssl certs which are managed by caddy and it just wont start , same error as above.
[s6-init] making user provided files available at /var/run/s6/etcâŠexited 0.
[s6-init] ensuring user provided files have correct permsâŠexited 0.
[fix-attrs.d] applying ownership & permissions fixesâŠ
[fix-attrs.d] done.
[cont-init.d] executing container initialization scriptsâŠ
[cont-init.d] 00-banner.sh: executingâŠAdd-on: UniFi Controller
Manage your UniFi network using a web browserAdd-on version: 0.21.0
You are running the latest version of this add-on.
System: Home Assistant OS 5.13 (armv7 / raspberrypi4)
Home Assistant Core: 2021.4.6
Home Assistant Supervisor: 2021.04.0Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executingâŠ
Log level is set to DEBUG
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] unifi.sh: executingâŠ
[22:26:38] DEBUG: Intializing keystoreâŠ
Warning:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using âkeytool -importkeystore -srckeystore /usr/lib/unifi/data/keystore -destkeystore /usr/lib/unifi/data/keystore -deststoretype pkcs12â.
[22:28:35] DEBUG: Injecting SSL certificate into the controllerâŠ
[22:28:35] DEBUG: Preparing certificate in a format UniFi acceptsâŠ
[22:28:35] DEBUG: Removing existing certificate from UniFi protected keystoreâŠ
[22:28:36] DEBUG: Inserting certificate into UniFi keystoreâŠ
Importing keystore /tmp/tmp.hhCClNV9mm to /usr/lib/unifi/data/keystoreâŠ
Warning:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using âkeytool -importkeystore -srckeystore /usr/lib/unifi/data/keystore -destkeystore /usr/lib/unifi/data/keystore -deststoretype pkcs12â.
[cont-init.d] unifi.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[22:28:37] INFO: Starting the UniFi ControllerâŠ
> 2021-05-02 22:28:39,168 main ERROR Error processing element InMemoryAppender ([Appenders: null]): CLASS_NOT_FOUND
> 2021-05-02 22:28:40,430 main ERROR Unable to locate appender âInMemoryAppenderâ for logger config ârootâ
reported an issue in a separate thread, similar to what others have seen. Didnât want to hijack this thread, but helpful if someone can have a look and share ideas:
It seems the situation is getting worse ? Is Frenck aware of the situation ? Is there an issue raised ?For the time beeing I stick to the working version
I havenât been able to access the webui since 0.21.0. Was hoping that 0.22.0 would fix that, but itâs the same. I can uninstall/reinstall the plugin, then it is accessible but as soon as I do a restore from the auto-backup list I canât access it anymore
I have the same issue and error. Jumped back to a previous version but still no access to the web-ui. Removing and Re-adding the Add-on gives me a starting point but when I try loading the backup settings it cuts out again.
thatâs exactly what I found. Shame to loose the history and all the settings indeed, but I think it is the only way.
is it possible to read the AP the device is connected to?
i.e. Iphone 12 Pro - connected to Wifi-Garden
Yes. In topology a.o.
1 Like
FYI, I received a 404 Page not found after upgrading to 0.23 on my RasPi4 with:
Home Assistant OS 5.13
supervisor-2021.04.3
core-2021.5.4
Rolled back using a snapshot. I feel no need or have the time to investigate the situation, so therefor itâs just a FYI 
Nevertheless a big thanks to Fr(e|a)nck for offering this add-on 
1 Like
Hi
Strange issue. I install UniFi Controller add-on version 0.23.0 today.
After installation all works fantastic. I was able to set it up, add network devices etc⊠no issues at all.
But when i reboot host, i am not able to open UniFi web based GUI - âpage not foundâ issue
I am using:
- Debian 9.13 (stretch)
- Docker 19.03.15, build 99e3ed8919
- supervisor-2021.04.3
- core-2021.5.4
I can see in home assistant interface that add-on is up and running. No useful informations in add-on log, last line says â[16:05:41] INFO: Starting the UniFi ControllerâŠâ
Also in docker ps command i can see it:
docker ps | grep unifi
a1469b97cab3 ghcr.io/hassio-addons/unifi/armv7:0.23.0 â/initâ About an hour ago Up About an hour 0.0.0.0:3478->3478/udp, 0.0.0.0:6789->6789/tcp, 0.0.0.0:8080->8080/tcp, 0.0.0.0:8443->8443/tcp, 0.0.0.0:8843->8843/tcp, 0.0.0.0:5514->5514/udp, 0.0.0.0:10001->10001/udp, 0.0.0.0:8880->8880/tcp addon_a0d7b954_unifi
but i donât have access to UniFi web based GUI
I received the same error. From the log file:
System: Home Assistant OS 5.13 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2021.5.4
Home Assistant Supervisor: 2021.04.3
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] unifi.sh: executing...
[cont-init.d] unifi.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[13:47:21] INFO: Starting the UniFi Controller...
Exception in thread "launcher" java.lang.IllegalStateException: Tomcat failed to start up
at com.ubnt.net.B.ö00000(Unknown Source)
at com.ubnt.service.C.Ăo0000(Unknown Source)
at com.ubnt.ace.Launcher.main(Unknown Source)
Caused by: java.lang.RuntimeException: Web context failed to initialize
... 3 more
For anyone who is unable to access the Unifi WebUI, try restarting the core (not the host, ie no reboot) in HA Supervisor. After I do that I can suddenly access the WebUI, any version.
1 Like
I can asscess it
I can see my USG gateway but it wont adopt it
but if i install the Unifi Controller on my windows 10 machine i can get everything to work
This does work when HA isnât able to read device_tracker/presence info in earlier versions (ex. v0.22) but unfortunately didnât solve the 404 on v0.23.
Do I understand it correctly that with 2021.6 I can now configure Unifi to use a different VLAN (the Unifi management VLAN), than the rest of HASS (IoT VLAN)?
I still need to migrate from a docker setup to a Home Assistant Blue Odroid setup, so I cannot check myself yet.