Cloudron Forum

@girish I found this when i clicked update:
61f3d999-30ce-405d-9639-1e1c26465759-image.png

Both my apps are running and are accessible.

I now tried stopping the Nextcloud instance and started it.
And it the app the 1 dead app is now 2 alive and 0 dead.
Now i could update normally.

Not sure what i missed in the first place but now works.

Thanks for the help 🙂

Fixed now with the latest app package.

@smilebasti The /home/yellowtent/appsdata is the location of apps. This size seems to roughly match the nextcloud size. As for docker, you should not use du tools inside docker's image directories since they are overlays and the du tool is not smart enough to figure out the size correctly. Try docker system df to get a better idea about the actual size docker uses (this is what is reported in the graph as ~5GB). The volumes also link into appsdata so they might be double counted the du tools.

To take a wild guess, maybe you were backing up to the file system for some time before you moved to NAS via SMB? If this was the case, then you should remove the old backups manually from /var/backups. You can just safely nuke all the timestamped directories and the snapshot directory inside it.

@alwynispat do you mean nginx? How is NPM involved here?

edit: oh, maybe you mean your nginx proxy manager?

@smilebasti Possibly because the destination file system does not support hard links. In the Backup -> Configure, there is a checkbox to disable hard links.

@randyisscott I'm not entirely sure if the article I saw on https://www.proxies.com/ipv6 is attending to my question. I don't think I need all the additional trusted domains and trusted proxies stated there. Trusted domains are meant to tell nextcloud to allow access when you access it at cloudxxx or by IP address. They also have a duplicate in there, probably need to remove that. Trusted proxies I believe should only list the IP address of the proxy server, nothing else. I'm not sure if that affects the redirect loop but I would start there.