Hi,
I have been running the UNIFY controller for a good time now. First on an RPI3 and since 6 months or so on an RPI4 (Home Assistant operating System - prior Hassio) and the addon.
All was working fine. Could get to it through my local network on port 8443 as well as through the Unify app.
Last update a month ago of the controller gave an error but all still worked:
Today I performed the upgrade to version 0.22.0, got the same error as last month, but now I cannot not access the controller anymore. not through LAN or the Unify app on my mobile (nor local WIFI or mobile network). Thought that was strange, but now rollback to restore to the version of yesterday is giving the same issue…
Anyone has any clue what it could be or what I can try? I can SSL into HA through the addon, so it seems like something specific to this addon…
Thanks!
See Addon Debug level log:
[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 browser
-----------------------------------------------------------
Add-on version: 0.22.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
-----------------------------------------------------------
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...
[12:33:39] DEBUG: Injecting SSL certificate into the controller...
[12:33:39] DEBUG: Preparing certificate in a format UniFi accepts...
[12:33:39] DEBUG: Removing existing certificate from UniFi protected keystore...
[12:33:39] DEBUG: Inserting certificate into UniFi keystore...
Importing keystore /tmp/tmp.dmOOgvoKzr 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.
[12:33:40] INFO: Starting the UniFi Controller...
2021-05-05 12:33:42,603 main ERROR Error processing element InMemoryAppender ([Appenders: null]): CLASS_NOT_FOUND
2021-05-05 12:33:43,848 main ERROR Unable to locate appender "InMemoryAppender" for logger config "root"
What a nightmare. No fix so rolled it back up to the latest. Using https://unifi.ui.com/ I can at least log on and see what I should be able to see from inside my own house!?!
Yes, it’s working. Have to press F5 twice before it realises. I am on the version previous (0.21) to the latest update at the moment. I may hold off updating to 0.22…
That doesn’t do the trick for me. Back on 0.21.0 it shows my controller is offline. My suspicion is that something is wrong with the traffic to the docker container holding the controller.
Guess I’ll have to wait for it to be fixed as I see more people with the same issue.
A pity. I was glad I could get back in as I’d reverted back to before I added my extra non-wired AP’s. Restoring the latest didn’t see them adopted, so using the website approach I could at least sort them out! SWMBO was not happy when half the house went offline
I now went back all the way to version 0.19.2 and does not work… It might be actually be caused by a combination an OS upgrade (I will try that now to go to an earlier version of the OS).
things getting weirder… going back to 0.118.0 and addon version 0.19.2 doesnt work. Might not work because of a partial restore (only the OS and the addon), but still weird…
now going to try to re-install the addon from scratch.
What is even odder is that mine has decided to work using my old URL again now. Last night it refused, today it is working. Nothing has changed. Very very odd …
ok. so I finally have it working again. The only way to solve it was to uninstall the addon and to reinstall. Post that backup restore from unifi would break it again, so I had to build it back up from scratch, resetting the APs and re-adopt…
and again it failed. Maybe related to the last OS upgrade (can’t really recall if that was before or after the last post), but today it was unavailable again… .same issue and thus only re-install is possible.
To make things worse… I didn’t note down the SSH login details at install of the new controller after adopting the APs and for some reason the reset button on the AP doesn’t seem to work… holding it for more than 10sec doesn’t factory reset, so now I need to figure out how to factory reset the AP.
