Internal Server Error after upgrading to NC V27 #340
Comments
|
can you check the nextcloud log at |
I deleted the log before Jun 24th and attached it as below. Thank you once again for the help. |
|
Potential fix ONLYOFFICE/onlyoffice-nextcloud#830 (comment) |
I'm not sure how to fix it. I tried removing onlyoffice and installing onlyoffice V8.1.0, but it seems neither worked for me. |
|
Can you try removing onlyoffice entirely and not installing another version and see if things run? It could be a bug with onlyoffice that they need to fix. If things still don't run even when you remove onlyoffice entirely then it could be a bug on our end, or maybe still something else. |
|
Same problem here. Last update was 5/27 (v 26.02 I think). Updated today, and I'm getting the same message as @squallxb1983 |
|
Post your log. Even if it's the same error, there may be context around it. |
|
Here's the live log: **** The following active confs have different version dates than the samples that are shipped. **** |
|
It appears to be a Mariadb error. Nextcloud can't connect to the database, per log above. I ran database check on Mariadb mariadb-check: Got error: 2002: Can't connect to local server through socket '/var/run/mysqld/mysqld.sock' (2) when trying to connect I updated the Mariadb container at the same time as the Nextcloud update, as I've always done, but this time it seems there is an issue. Any pointers on how to fix Mariadb appreciated. Edit: I followed instructions detailed here linuxserver/docker-mariadb#125 and here https://github.com/linuxserver/cstate/blob/2505217ea6d06b00a1b413d44108c47f0a6cccee/content/issues/2023-05-28-mariadb.md to roll back Mariadb to 10.6.13. |
|
Fixed the issue on my Nextcloud instance and was able to upgrade to v27. After fixing the Mariadb issue (see above) and pinning to v 10.6.13, Nextcloud appeared in Maintenance mode due to some database errors. The fix was to change the line in the config file to turn maintenance mode off, then was able to log in to Nextcloud via the web interface. In Administration, ran checks and it showed database related errors, there were four outdated tables. Ran |
|
I gave up and installed nextcloud AIO instead. Then migrated all the data to AIO, now everything runs smoothly as it should be. The management in AIO is also easier and the new backup function is very useful. |
|
For the record, I started having these 2 errors and random crashes of Nextcloud after a forced shutdown of my NAS.
After connecting to docker and checking MariaDB, I randomly got these errors. Although the tables were declared as OK. Redownloading the image of the same version of MariaDB but a more recent build and recreating the stack fixed the problem. |
Is there an existing issue for this?
Current Behavior
After many attempts, I finally upgraded NC to V27, but now the login page says "Internal Server Error. The server was unable to complete your request."
The container log can be found below. Thank you for the help in advance.
Expected Behavior
No response
Steps To Reproduce
upgrade version of data from V21 to V27.
Environment
CPU architecture
x86-64
Docker creation
version: "2" services: nextcloud: image: ghcr.io/linuxserver/nextcloud container_name: nextcloud environment: - PUID=998 - PGID=100 - TZ=Europe/Stockholm volumes: - /srv/dev-disk-by-uuid-9dadb505-8d6a-4aba-8700-e4732a27f010/AppData/nextcloud/config:/config - /srv/dev-disk-by-uuid-9dadb505-8d6a-4aba-8700-e4732a27f010/Nextcloud/data:/data depends_on: - mariadb restart: unless-stopped mariadb: image: ghcr.io/linuxserver/mariadb container_name: mariadb environment: - PUID=998 - PGID=100 - MYSQL_ROOT_PASSWORD=mariadbpassword - TZ=Europe/Stockholm volumes: - /srv/dev-disk-by-uuid-9dadb505-8d6a-4aba-8700-e4732a27f010/AppData/mariadb/config:/config restart: unless-stoppedContainer logs
The text was updated successfully, but these errors were encountered: