j0nnymoe

The error shouldn't stop the controller from working itself but it's something to wait for unifi to fix.

I would highly suggest users having issues with this find a better solution, as I mentioned here:

We can't fix an isse that's related to upstream.

Some more info on what you've done might help

The well-known info needs to be added to the nextcloud nginx config and not the swag config. We've already updated this and mentioned it in the changelog for nextcloud.

The container was updated a couple hours after it was released

When it's released yes. (And that means when they publish it to their apt-get repo, not just on their forum/blog.)

Unfortunately, the state of this container currently is that it's a lottery if it will work for you. There has been a long standing issue with this container: https://github.com/linuxserver/docker-openvpn-as/issues/113 everything is explained there. In short, if you have issues with this container, I personally would suggest not wasting time on this and finding a better solution.

Yea apologies - we just need to add the additional nginx bits to the site config file. Though if you've done it manually, all good 👍

If it's an existing install, you won't get offered the update until Nextcloud release the OTA's.

Add this to the site config within the nextcloud container. We plan to add this soon.

It's a headless install as in zero display. It's not possible to use vnc with this. What you're seeing is actually the native Kodi webui.

You'll want to be checking your logs. nginx logs within the `/config` mount and also the nextcloud log itself in the root of your `/data` mount. That should give some sort of insight to what's happening.

Looks like someone had the same issue here: https://github.com/nextcloud/mail/issues/2583 Seems related to the Mail app within nextcloud.

The nextcloud web updater should offer you newer versions or you can cli into the container and run `updater.phar`