saarg

Have you tried using a previous tag? There are only dependencies updated in the latest build 2 days ago.

You need to check the swag logs and update the config files it mentions.

Do you use the IP to connect to nextcloud or reverse proxy limited to Lan only?

Everything. You have switched value and key and also remove =. Default value is also not -e. Just leave it blank.

I have no idea what is wrong in your setup, but it is something local to you as it works here on a fresh setup and my existing install.

I don't see the docker run command there and it's not really enough detailed info about what you have done. But could you try to set up a new nextcloud container and be sure to use anothe folder for both appdata and data. You can use sqlite for database. I just want to see if you get the same errors then, as I'm not getting it.

I'm confused now. Are you having two accounts here and posting as aspect also or did you just piggytail on his problem answering my post to him. Seeing you are not using unraid, please go to linuxserver.io/support and either join our discord or discourse forum to get support. This is for unraid users only.

I just installed a fresh nextcloud container here and there are no messages about missing well-known stuff. Post your docker run command, how you connect to nextcloud and exactly what you have been doing to try to fix it. And use the code tag.

Next time you post a config file or log, please use the code formatting. It's not easy to look at this on a mobile device when the formatting is screwed up. The file looks like it's the latest version, so try using incognito mode or private mode in your browser.

Press OK, and then you should get the login window. You might have to remove the previous set env variable for user/password as the base image was changed. It's in the changelog of the readme.

The fix is in the default file of the nextcloud container.

Post your default file.

Then it's something in your network not resolving the domain.

Still nothing with the container itself. Then it's either nextcloud, your phone, the nextcloud client or your router. Did you try using the browser on your phone? If it works using your domain there it's either the client or nextcloud itself.

It's getting fixed.

When have you seen us post anything support related with that account? It's only used to start the support thread, which we now stopped doing and will not do anymore as we want support to happen on our platforms. There are nobody else reporting any chrashes using our container, so it's a local issue. The container is receiving a signal to stop, so you will have to figure out what does that.

This has nothing to do with the container setup. It's your router that doesn't support NAT hairpin/split DNS out of the box.

You have to use https from your proxy to nextcloud.

Yes, read the previous posts.

Might be worth it to read the documentation some times 😉

There might be a couple of hundred post about the same issue in this thread, so a search would be welcome 😉 In short, you haven't updated nextcloud in a long time.

So that's why squid is driving around in a fancy new sports car 😆

It's building from the new repo.

As usual with Plex codecs errors, deleting the Codecs folder and restarting Plex usually fixes the problem.

We have discussed it internally now, and we will not release a new container under the new name. Daapd is now maintained by a community member (our community, not unraid).