Open Af0x opened 1 month ago
I just got this one after upgrading from 29.0.0.19 -> 29.0.1.1 Got an internal server error message on the webui. Disabling circles fixed the issue. Same message if I try to enable it
Just occured to me after updating two other plugins
Same when updating from nextcloud-28.0.5.1 to nextcloud-28.0.6.1
Erreur interne du serveur
Le serveur est incapable d’exécuter votre requête.
Si cela se reproduit, veuillez envoyer les détails techniques ci-dessous à l’administrateur du serveur.
Le fichier journal du serveur peut fournir plus de renseignements.
Renseignements techniques
Adresse distante : XXXX
ID de la demande : XXXX
Resolved by: docker exec -u www-data $(docker ps --filter name='srv-captain--nextcloud.1' -q) php occ app:disable circles
And repair: docker exec -u www-data $(docker ps --filter name='srv-captain--nextcloud.1' -q) php occ maintenance:repair
Followed by a container restart
Some people talk about it here: https://help.nextcloud.com/t/after-update-to-nc29-0-1-internal-server-error-circles-the-cause/194167
I have the same problem after updating from 28.0.6 to 29.0.1, but natively without docker-containter.
It helped to deactivate Circles via the terminal, then you can at least log in again.
Teams cannot be activated, because apparently a -dev version is available. Activation is prevented by the message ‘This app cannot be activated because it will make the server unstable’.
What fixed it for me completely:
occ app:disable circles
occ maintenance:repair
Beta
-> Version 29.0.2 RC2 will be availableocc app:enable circles
The webinterface will be accessible again with circles enabled. However, Beta channel can introduce new issues so make a backup first.
Is there any progress regarding the bugfix?
So far I've been unable to reproduce any of these behaviors.
Please share the output of:
occ config:list system
occ app:list
Hello,
I get the following error when trying to enable circles. Had to disable it because there was an Internal Server Error preventing the webinterface to load:
The issue first occurred after upgrading from nextcloud-28.0.5.1 to nextcloud-28.0.6.1 and persists after upgrading to Nextcloud 29.0.1.