search

hassio-addons / addon-unifi

UniFi Network Application - Home Assistant Community Add-ons
https://addons.community
MIT License
278 stars 138 forks source link

Controller not reachable after update 1.0.0 #249

Closed Bounties1337 closed 2 years ago

Bounties1337 commented 3 years ago

Add-on updated to 1.0.0. http nor https onto controller possible.

However, Log looks good saying controller is starting... .

image

Hassio Log says the following: image

Any Idea?

bagg3rs commented 3 years ago

I am getting the same error and logs after the upgrade also.

I reverted back to v0.23.2 version successfully, https://github.com/hassio-addons/addon-unifi/releases/tag/v0.23.2 Which states it's the last 32bit version for armhf, armv7 & i386. There is a duplicate issue logged earlier also

pro2call-nl commented 3 years ago

Here also same issue.

HASSIO CORE core-2021.8.5 Supervisor supervisor-2021.06.8

64BIT OS Raspberry pi 4 8gb

restored the backup working OK now

bitcrumb commented 3 years ago

Same here, logs mention the unifi controller successfully started. No visible errors in the add-on logs. But the controller is unreachable (I had/have https configured).

The "Log Viewer" does repeatedly show this error: 2021-08-13 00:15:48 ERROR (MainThread) [homeassistant.components.unifi] Error connecting to the UniFi controller at 192.168.1.4: Error requesting data from 192.168.1.4: Cannot connect to host 192.168.1.4:8443 ssl:default [Connect call failed ('192.168.1.4', 8443)]

edit Reverting back to v0.23.2 version was succesful.

Thermostaatkraan commented 3 years ago

Exactly the same problem here. Logs seem fine but the controller is not reachable.

coffeepotatochips commented 3 years ago

version 0.23.2 broke the use of Let's Encrypt SSL and I had to uninstall unifi controller and disable SSL. A painful process as I had not made a backup of the config file and I have to reset my unifi devices for re-adoption.

For version 1.0.0, this broke the web UI access. Logs as follows:

:1023 Permanent error code on channel bind request: 403 - Forbidden IP
:1023 Permanent error code on channel bind request: 403 - Forbidden IP
:484 All TURN channel bindings failed
21-08-13 09:11:52 WARNING (MainThread) [supervisor.addons.options] Option 'ssl' does not exist in the schema for UniFi Controller (a0d7b954_unifi)
21-08-13 09:11:52 WARNING (MainThread) [supervisor.addons.options] Option 'certfile' does not exist in the schema for UniFi Controller (a0d7b954_unifi)
21-08-13 09:11:52 WARNING (MainThread) [supervisor.addons.options] Option 'keyfile' does not exist in the schema for UniFi Controller (a0d7b954_unifi)

Reverted back to version 0.23.2.

reicharb commented 3 years ago

I am having the same issue.

PrathikGopal commented 3 years ago

Same here with me, it fails to load UI after upgrade. Reverted back from backup for now.

Tried to reinstall clean and restore from backup, the UI came back online but the login fails(even default).

rkeyzer9 commented 3 years ago

Same issue here, since updating controller is not reachable anymore

Tommatheussen commented 3 years ago

I'm not sure if this is actually what made it work for me, but I went into the addon Configuration, selected to 'Edit in YAML'. Removed the SSL and cert options there and saved. After that it came right back up. The release notes state that SSL options are no longer there, maybe that caused a breaking loop or something.

dikt1338 commented 3 years ago

Same here.

21-08-13 08:52:26 WARNING (MainThread) [supervisor.addons.options] Option 'certfile' does not exist in the schema for UniFi Controller (a0d7b954_unifi)
21-08-13 08:52:26 WARNING (MainThread) [supervisor.addons.options] Option 'keyfile' does not exist in the schema for UniFi Controller (a0d7b954_unifi)
21-08-13 08:52:26 WARNING (MainThread) [supervisor.addons.options] Option 'certfile' does not exist in the schema for UniFi Controller (a0d7b954_unifi)
21-08-13 08:52:26 WARNING (MainThread) [supervisor.addons.options] Option 'keyfile' does not exist in the schema for UniFi Controller (a0d7b954_unifi)
21-08-13 08:52:30 WARNING (MainThread) [supervisor.addons.options] Option 'certfile' does not exist in the schema for UniFi Controller (a0d7b954_unifi)
21-08-13 08:52:30 WARNING (MainThread) [supervisor.addons.options] Option 'keyfile' does not exist in the schema for UniFi Controller (a0d7b954_unifi)
21-08-13 08:53:07 INFO (SyncWorker_7) [supervisor.docker.interface] Stopping addon_a0d7b954_unifi application
21-08-13 08:53:12 INFO (SyncWorker_7) [supervisor.docker.interface] Cleaning addon_a0d7b954_unifi application
21-08-13 08:53:14 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/unifi/aarch64 with version 1.0.0
21-08-13 08:53:26 INFO (SyncWorker_5) [supervisor.docker.interface] Stopping addon_a0d7b954_unifi application
21-08-13 08:53:30 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
21-08-13 08:53:30 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
21-08-13 08:53:30 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
21-08-13 08:53:30 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
21-08-13 08:53:30 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-08-13 08:53:30 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-08-13 08:53:30 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-08-13 08:53:30 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
21-08-13 08:53:30 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
21-08-13 08:53:31 INFO (SyncWorker_5) [supervisor.docker.interface] Cleaning addon_a0d7b954_unifi application
21-08-13 08:53:31 WARNING (SyncWorker_4) [supervisor.docker.interface] Can't grep logs from ghcr.io/hassio-addons/unifi/aarch64: 409 Client Error for http+docker://localhost/v1.41/containers/5b2720fe14599b9a1cb4817146ff1ade5f1f5041f99e18404e4f08add641a268/logs?stderr=1&stdout=1&timestamps=0&follow=0&tail=100: Conflict ("can not get logs from container which is dead or marked for removal")
21-08-13 08:53:46 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
21-08-13 08:53:46 INFO (SyncWorker_3) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/unifi/aarch64 with version 1.0.0
21-08-13 08:54:20 INFO (SyncWorker_6) [supervisor.docker.interface] Stopping addon_a0d7b954_unifi application
21-08-13 08:54:25 INFO (SyncWorker_6) [supervisor.docker.interface] Cleaning addon_a0d7b954_unifi application
21-08-13 08:54:27 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/unifi/aarch64 with version 1.0.0
21-08-13 08:54:47 INFO (SyncWorker_5) [supervisor.docker.interface] Stopping addon_a0d7b954_unifi application
21-08-13 08:54:52 INFO (SyncWorker_5) [supervisor.docker.interface] Cleaning addon_a0d7b954_unifi application
21-08-13 08:54:54 INFO (SyncWorker_2) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/unifi/aarch64 with version 1.0.0
21-08-13 08:55:26 INFO (SyncWorker_1) [supervisor.docker.interface] Stopping addon_a0d7b954_unifi application
21-08-13 08:55:32 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_a0d7b954_unifi application
21-08-13 08:55:34 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/unifi/aarch64 with version 1.0.0
21-08-13 08:56:03 INFO (SyncWorker_4) [supervisor.docker.interface] Stopping addon_a0d7b954_unifi application
21-08-13 08:56:08 INFO (SyncWorker_4) [supervisor.docker.interface] Cleaning addon_a0d7b954_unifi application
dbruynb commented 3 years ago

Same issue here, reverted back to version 0.23.2

stevehop commented 3 years ago

Same here, seems to break the redirection process. Strange that it complains about certfile and keyfile options even though they are no longer visible in the config yaml.

Not looking forward to setting this up with a reverse proxy as it's notoriously difficult to achieve

dikt1338 commented 3 years ago

reverted back, too. If I could help with logs or test anything - let me know

rkeyzer9 commented 3 years ago

Reverted back.... Hope there comes a solution

azazul1980 commented 3 years ago

Same here i reverted back

piouoso commented 3 years ago

Hello, same here, I tried also to edit the YAML and remove SSL and keyfile with no luck, I had to revert back to 0.23.2 after 10 minutes of real panic.

garyak commented 3 years ago

I migrated to a non-ssl configuration before moving to 1.0.0. The controller is reachable, but the same errors appear in the supervisor log:

21-08-13 03:57:40 WARNING (MainThread) [supervisor.addons.options] Option 'ssl' does not exist in the schema for UniFi Controller (a0d7b954_unifi)
21-08-13 03:57:40 WARNING (MainThread) [supervisor.addons.options] Option 'certfile' does not exist in the schema for UniFi Controller (a0d7b954_unifi)
21-08-13 03:57:40 WARNING (MainThread) [supervisor.addons.options] Option 'keyfile' does not exist in the schema for UniFi Controller (a0d7b954_unifi)
marcomsousa commented 3 years ago

same here, controller not reachable after update 1.0.0 I try to removed the SSL and cert options, but no lucky.

> [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: 1.0.0
>  You are running the latest version of this add-on.
>  System: Home Assistant OS 6.2  (aarch64 / raspberrypi4-64)
>  Home Assistant Core: 2021.8.5
>  Home Assistant Supervisor: 2021.06.8
> -----------------------------------------------------------
>  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 INFO
> [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.
> [15:17:00] INFO: Starting the UniFi Controller...

https://IP:8443 -> ERR_CONNECTION_REFUSED

strasharo commented 3 years ago

Same here, using HASS with a Letsencrypt cert. Reverted back to 0.23.2.

spudje commented 3 years ago

This is pretty insane. Didn't anyone test this? How do I revert back to an old version?

stevehop commented 3 years ago

This is pretty insane. Didn't anyone test this? How do I revert back to an old version?

Hopefully you have a HA snapshot that you can partially restore, that's the easiest way

spudje commented 3 years ago

Restore the full Hass stack??? That's stupid. I just want the older Unifi version again (for which I also have a backup).

stevehop commented 3 years ago

Restore the full Hass stack??? That's stupid. I just want the older Unifi version again (for which I also have a backup).

No, I clearly said a partial restore of a Home Assistant snapshot, that will allow you to restore just the old version of Unifi and your old config

spudje commented 3 years ago

Ah I see. Let's try that then. Thanks!

marcomsousa commented 3 years ago

I see that in this new 1.0.0 release, mongodb was upgrade from 2.6.10-0ubuntu1[ubuntu repo] to 3.4.24 [Mongodb repo] (without be reflected on the release notes).

Could this be the problem? @frenck

0.23.2 version: https://github.com/hassio-addons/addon-unifi/commit/d5839037c383c4a9e68025a3ecc626fd4cb18bd8#diff-aa3ca5069e32eb52aa889015b102e6bf275a3fc88789e6d699bd994e9a82ce81L29

1.0.0 version: https://github.com/hassio-addons/addon-unifi/commit/9592a785fbe9090b8299fc784e4cd317866ec3b5#diff-aa3ca5069e32eb52aa889015b102e6bf275a3fc88789e6d699bd994e9a82ce81R27

stevehop commented 3 years ago

Ah I see. Let's try that then. Thanks!

No problem, just in case: image

spudje commented 3 years ago

There's a snapshot from right before the updatre, but if I try to restore that, it doesn't really do anything?? Am to folow a different process to restore than just pick the snapshot and click on restore (and the 2nd confirmation)?

Thermostaatkraan commented 3 years ago

This is pretty insane. Didn't anyone test this? How do I revert back to an old version?

Hopefully you have a HA snapshot that you can partially restore, that's the easiest way

Thanks a lot for this, totally didn't think about that. Worked flawlessly, just had to wait a couple of minutes!

frenck commented 3 years ago

I've hidden all "I have the same issue" comments. Please use a 👍 on a comment or report. Those comments add nothing to debugging the issue at hand.

Additionally, this isn't a support forum either.

Thanks for understanding 👍

frenck commented 3 years ago

I see that in this new 1.0.0 release, mongodb was upgrade from 2.6.10-0ubuntu1[ubuntu repo] to 3.4.24 [Mongodb repo] (without be reflected on the release notes).

Could this be the problem? @frenck

Any change between the previous and last version could potentially be the problem. Could you explain why you conclude that is the problem?

frenck commented 3 years ago

Please don't report this problem here, it is not related to this issue.

21-08-13 09:11:52 WARNING (MainThread) [supervisor.addons.options] Option 'ssl' does not exist in the schema for UniFi Controller (a0d7b954_unifi)
21-08-13 09:11:52 WARNING (MainThread) [supervisor.addons.options] Option 'certfile' does not exist in the schema for UniFi Controller (a0d7b954_unifi)
21-08-13 09:11:52 WARNING (MainThread) [supervisor.addons.options] Option 'keyfile' does not exist in the schema for UniFi Controller (a0d7b954_unifi)

Additionally, those are in the release notes, SSL support has been dropped. Please remove those config options from your configuration.

And again, not part of this issue, so not the right place to discuss this even. Just posting this to get it out of the way.

spudje commented 3 years ago

I'm really sorry to still ask one final support question, which may be off-topic. Is it correct that after restoring a partial snapshot, this shows as an available update for the add-on, which I can then run to really install/roll-back? Or should it fully restore automatically and has something gone wrong?

marcomsousa commented 3 years ago

Could you explain why you conclude that is the problem?

Since there is no error logs, is impossible to have any conclusion.

I raise this concern just with comparing changes. This mongodb upgrade could not be intentional (since was not in release notes, and you rollback the new mongodb 3.6).

frenck commented 3 years ago

Then I'm not sure why you raising it. 🤷‍♂️

I raise this concern just with comparing changes. This mongodb upgrade could not be intentional (since was not in release notes, and you rollback the new mongodb 3.6).

The add-on ran MongoDB 2.x, there is no upgrade path from 2.x -> 3.6+. The max version for that is 3.4 the add-on runs 3.4, so in a couple of months, we can remove the 3.4 pin and upgrade to even further.

This upgrade path has been tested on multiple devices, from existing installations and new setups (including my fully loaded production instance before releasing it to you guys).

marcomsousa commented 3 years ago

To be more helpfully, I connect to the addon-unifi container and I was able to get the mongodb error message

image

frenck commented 3 years ago

Nice! Thanks!

stevehop commented 3 years ago

I'm really sorry to still ask one final support question, which may be off-topic. Is it correct that after restoring a partial snapshot, this shows as an available update for the add-on, which I can then run to really install/roll-back? Or should it fully restore automatically and has something gone wrong?

No, the available update is telling you that the restore is successful and there's a newer update available, the version you've just rolled back from

marcomsousa commented 3 years ago

Trying to find how to install mmapv1 storage engine dependency manually, but I do not find it how. (Should be already inside mongodb 3.4 installation, but do not work).

I manually downgrade mongo-server to mongodb 2.6 ports ubuntu repo (inside the container), and my Unifi addon is able to work fine.

frenck commented 3 years ago

mongodb 2.6 ports ubuntu repo

The problem is that we cannot stick on that version for the future.

coffeepotatochips commented 3 years ago

Please don't report this problem here, it is not related to this issue.

21-08-13 09:11:52 WARNING (MainThread) [supervisor.addons.options] Option 'ssl' does not exist in the schema for UniFi Controller (a0d7b954_unifi)
21-08-13 09:11:52 WARNING (MainThread) [supervisor.addons.options] Option 'certfile' does not exist in the schema for UniFi Controller (a0d7b954_unifi)
21-08-13 09:11:52 WARNING (MainThread) [supervisor.addons.options] Option 'keyfile' does not exist in the schema for UniFi Controller (a0d7b954_unifi)

Additionally, those are in the release notes, SSL support has been dropped. Please remove those config options from your configuration.

And again, not part of this issue, so not the right place to discuss this even. Just posting this to get it out of the way.

OT here but maybe it's just me not technically competent enough to determine whether the log I post is relevant to the problem or not. Next time I shall stand idle for fear of posting irrelevant logs.

Hope you don't get the wrong way, anyhow I will make a donation as I appreciate the work you are doing.

shemeel commented 3 years ago

I have the Same issue - Reverting now

marcomsousa commented 3 years ago

Checking the documentation and say that we need to perform more upgrades steps:

To upgrade an existing MongoDB deployment to 3.4, you must be running a 3.2-series release.

To upgrade from a version earlier than the 3.2-series, you must successively upgrade major releases until you have upgraded to 3.2-series. For example, if you are running a 3.0-series, you must 3.2 before you can upgrade to 3.4.

2.6 -> 3.0 upgrade to 3.0 3.0 -> 3.2 upgrade to 3.2 3.2 -> 3.4 upgrade to 3.4 3.4 -> 3.6 upgrade to 3.6

So we need to go first to 3.0?

pbouna321 commented 3 years ago

I have the Same issue - Reverting now

Same. Watching this for updates.

bcutter commented 3 years ago

Running HA 2021.8.6 / HASS OS 6.2 64 bit on RPi4 8 GB, ran into the same "no web interface loading after updating the addon to v1.0.0" issue.

Needed to restore from backup (they are so important :-) ) too. Will watch this issue and keep away from the update button, 0.23.2 is safe.

mpoli commented 3 years ago

When I upgraded to 0.23.2 I was caught in the #235 and couldn't connect to the controller.

Installing a fresh 1.0.0 gives me a functional web interface, but trying to upgrade from 0.23.2 to 1.0.0 results in non functional web interface.

I did a manual restore from a home assistant add on backup (0.23.2), using method number 3 in this link: https://help.ui.com/hc/en-us/articles/204952144-UniFi-How-to-Create-and-Restore-a-Backup both preserving and replacing the the keystore file. All attempts result in:

root@a0d7b954-unifi:/data/unifi/data# cat /run/s6/services/unifi/logs/server.log
[2021-08-13T23:13:14,468] <localhost-startStop-1> INFO  Version - HV000001: Hibernate Validator 6.1.2.Final
[2021-08-13T23:13:15,270] <localhost-startStop-1> INFO  system - ======================================================================
[2021-08-13T23:13:15,273] <localhost-startStop-1> INFO  system - UniFi 6.2.26 (build atag_6.2.26_15319 - release/release) is started
[2021-08-13T23:13:15,274] <localhost-startStop-1> INFO  system - ======================================================================
[2021-08-13T23:13:15,279] <localhost-startStop-1> INFO  system - BASE dir:/usr/lib/unifi
[2021-08-13T23:13:15,424] <localhost-startStop-1> INFO  system - Current System IP: 172.30.33.4
[2021-08-13T23:13:15,424] <localhost-startStop-1> INFO  system - Hostname: a0d7b954-unifi.local.hass.io
[2021-08-13T23:13:15,429] <localhost-startStop-1> INFO  system - ubic.env: prod
[2021-08-13T23:13:16,065] <localhost-startStop-1> WARN  system - Valid keystore is missing or invalid. Generating one ...
[2021-08-13T23:13:16,066] <localhost-startStop-1> INFO  system - Generating Certificate[UniFi]... please wait...
[2021-08-13T23:13:17,211] <localhost-startStop-1> INFO  system - Certificate[UniFi] generated!
[2021-08-13T23:13:17,903] <localhost-startStop-1> INFO  db     - waiting for db connection...
[2021-08-13T23:13:19,636] <db-server> INFO  db     - DbServer stopped
[2021-08-13T23:13:19,637] <db-server> WARN  db     - DbServer not shutdown cleanly and need repairing on next startup
[2021-08-13T23:13:23,693] <db-server> ERROR system - [exec] error, rc=100, cmdline=[bin/mongod, --dbpath, /usr/lib/unifi/data/db, --port, 27117, --unixSocketPrefix, /usr/lib/unifi/run, --logRotate, reopen, --logappend, --logpath, /usr/lib/unifi/logs/mongod.log, --pidfilepath, /usr/lib/unifi/run/mongod.pid, --smallfiles, --bind_ip, 127.0.0.1, --repair]
[2021-08-13T23:13:25,350] <db-server> INFO  db     - DbServer stopped
[2021-08-13T23:13:29,406] <db-server> INFO  db     - DbServer stopped
[2021-08-13T23:13:33,464] <db-server> INFO  db     - DbServer stopped
[2021-08-13T23:13:37,521] <db-server> INFO  db     - DbServer stopped
[2021-08-13T23:13:41,576] <db-server> INFO  db     - DbServer stopped

So even trying to manually upgrade from a borked 0.23.2 to a fresh new 1.0.0 by simply copying the /data dir inside the docker volume results in non-functional and in no really useful log entries.

Could this be a mongodb version thing?

EDIT: From /usr/lib/unifi/logs/mongod.log:

2021-08-14T12:53:50.427-0300 I CONTROL  [initandlisten] options: { net: { bindIp: "127.0.0.1", port: 27117, unixDomainSocket: { pathPrefix: "/usr/lib/unifi/run" } }, processManagement: { pidFilePath: "/usr/lib/unifi/run/mongod.pid" }, storage: { dbPath: "/usr/lib/unifi/data/db", mmapv1: { smallFiles: true } }, systemLog: { destination: "file", logAppend: true, logRotate: "reopen", path: "/usr/lib/unifi/logs/mongod.log" } }
2021-08-14T12:53:50.432-0300 I -        [initandlisten] Detected data files in /usr/lib/unifi/data/db created by the 'mmapv1' storage engine, so setting the active storage engine to 'mmapv1'.
2021-08-14T12:53:50.432-0300 I STORAGE  [initandlisten] exception in initAndListen: 18656 Cannot start server with an unknown storage engine: mmapv1, terminating
2021-08-14T12:53:50.432-0300 I NETWORK  [initandlisten] shutdown: going to close listening sockets...

So Mongo engine missing from an old implementation compared to the new. Migration path issue?

frenck commented 3 years ago

Checking the documentation and say that we need to perform more upgrades steps:

According to the server itself, it can upgrade from 2.x -> 3.4 directly (which has been done for a lot of people. Considering 24 participants in this issue and over 5K instances already upgraded/migrated, I would think there is an edge case. One that happens and is real, but still...

As said, the upgrade path for MongoDB has been tested in different scenarios. In the end, is just odd in some cases it reports a missing mmapv1 engine, while that is still part of the 3.x MongoDB series (dropped in 4.x).

I'm in the dark at this point, and I'm really concerned about a path moving forward. I've broken my head over this for days to figure out the current path and getting things reliable. With this, as a result, I'm afraid it starts to look like it isn't something that can be fixed.

Honestly, if anybody from Ubiquiti reads this: Get rid of MongoDB or at least try to keep up (oh and if you are at it... time ditch Java 8, originating from 2014, as well...) 😢

pro2call-nl commented 3 years ago

I had some free time today.

what i have done:

  1. made a backup in the unifi controller
  2. removed 0.23.2
  3. installed 1.0.0
  4. restored backup.

All OK now.

this is maybe the easiest step for the 24 users

tykeal commented 3 years ago

I had some free time today.

what i have done:

  1. made a backup in the unifi controller
  2. removed 0.23.2
  3. installed 1.0.0
  4. restored backup.

All OK now.

this is maybe the easiest step for the 24 users

Thought this was going to be a good way forward for myself as well. Except that I've got SSL all configured with HSTS on my HA setup and doing this completely breaks.

Anybody got a code snippet for adding an extra server handler to the Nginx proxy Add-On to make it deal with this thing?

garyak commented 3 years ago

When I attempt to restore a add-on generated backup on 1.0.0, I get "There was an error restoring the backup" pop-up.

PrathikGopal commented 3 years ago

I had some free time today.

what i have done:

  1. made a backup in the unifi controller
  2. removed 0.23.2
  3. installed 1.0.0
  4. restored backup.

All OK now.

this is maybe the easiest step for the 24 users

Strangely enough. I had already tried this earlier, but it failed.

But today after seeing your comments, gave it another go and it worked. moved to 1.0.0 and restored from the auto backup within the add-on.