j0nnymoe

Rolling back to an older image doesn't mean it's a "fix". You shouldn't have your database containers on auto update. Having a database update while it's beening accessed by X application (in this case nextcloud) is just asking for trouble and likely going to cause corruption or data loss.

Less so benefits for unraid users (x86_64) but better for our armhf / aarch64 users as mariadb don't release up to date versions for those platforms on ubuntu base.

Upgrading to `:latest` will put you on alpine.

Be aware that this will no longer get updates.

Probably best start by providing info on the container - Have you been keeping nextcloud updated within the container? Nginx logs? nextcloud logs?

OpenVPN-AS still gets updated from openvpn itself. The reason we've dropped it is due to the constant band-aid fixes we have to do and something breaks on every update they push out.

We've depreciated the container now so there will be no further updates/changes/support for the container.

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.