Yes, you’ll be notified on cluster status page.
Automatic/scheduled updates are available with the subscription, see also
https://docs.nethserver.org/projects/ns8/en/latest/subscription.html
Oh I see, thanks @mrmarkuz , but I am not in subscription 
, I think I need to manual this one.
1 Like
No. You don’t need a sub for the Nethserver Nextcloud upgrades, do not upgrade Nextcloud from within Nextcloud unless directed because something ended up broken.
@caldedragon
3 Likes
During update “bad gateway” is normal but it should work again after the update.
Are there errors in the logs?
@mrmarkuz how to display logs ? Yes that should be.
1 Like
Here it is @mrmarkuz
Did you already try to save the NS8 Nextcloud settings in the cluster-admin to restart the services/containers?
There’s an error about ffmpeg. Did you install it or maybe some video app in Nextcloud?
The other log entries are ok.
Let’s check the permissions:
runagent -m nextcloud1 podman exec nextcloud-app ls -l . bin
Let’s check if the containers are running:
[root@ns8rockytest ~]# runagent -m nextcloud1 podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
730d8046c7c3 localhost/podman-pause:5.2.2-1743105461 2 days ago Up 2 days 127.0.0.1:20012->80/tcp 7128dc122eb6-infra
5eb8e3571794 docker.io/library/mariadb:10.6.21 mariadbd 2 days ago Up 2 days 127.0.0.1:20012->80/tcp, 3306/tcp nextcloud-db
abcea1a02c09 docker.io/library/redis:7.4.2-alpine --appendonly yes 2 days ago Up 2 days 127.0.0.1:20012->80/tcp, 6379/tcp nextcloud-redis
82a262eb56e2 ghcr.io/nethserver/nextcloud-app:1.4.1 /usr/bin/supervis... 2 days ago Up 2 days 127.0.0.1:20012->80/tcp, 9000/tcp nextcloud-app
d6be74109344 docker.io/library/nginx:1.27.5-alpine nginx -g daemon o... 2 days ago Up 2 days 127.0.0.1:20012->80/tcp, 80/tcp nextcloud-nginx
4769251b554e ghcr.io/nethserver/nextcloud-notify_push:1.4.1 /notify_push 2 days ago Up 2 days 127.0.0.1:20012->80/tcp, 7867/tcp nextcloud-notify_push
I will say I consistently note a 5 to 10 minute bad gateway for Nextcloud on NS8 on my old hardware with a reboot.
Yes I notice this after the core update, CPU usage got up., that is why the machine keeps unresponding.
The permissions of the bin directory are wrong.
If you don’t need the bin directory in Nextcloud, you could remove it:
runagent -m nextcloud1 podman exec nextcloud-app rm -rf bin
Now configuring Nextcloud from the cluster-admin should work.
Sorry, this one should work:
rm -rf /home/nextcloud1/.local/share/containers/storage/volumes/nextcloud-app-data/_data/bin
@mrmarkuz I am able to remove that particular folder now but in the level of root.
after that I’ll revert again inside nextcloud user.
then go back again to my cluster and do some settings update but still having this error.
Could you share logs again to catch the error?
If there’s not much data in Nextcloud, maybe it’s better to remove Nextcloud and reinstall it?
man you so kind… anyways trying also to figure out , I restart the nextcloud
after what we are doing man, and now showing maintenance mode:
What’s the next on this to turn off the maintenance mode? is this regular happen if there’s an update?
unfortunately, this is now having data, I want to work around how this works. for future referrence.
To run the upgrade and disable maintenance mode manually:
1 Like