-
-
Notifications
You must be signed in to change notification settings - Fork 138
Closed
Description
Is there an existing issue for this?
- I have searched the existing issues
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
- OS:
- How docker service was installed: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
using keys found in /config/keys
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│ old date │ new date │ path │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2022-08-20 │ 2023-06-24 │ /config/nginx/ssl.conf │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
**** The following site-confs have extensions other than .conf ****
**** This may be due to user customization. ****
**** You should review the files and rename them to use the .conf extension or remove them. ****
**** nginx.conf will only include site-confs with the .conf extension. ****
/config/nginx/site-confs/default
/config/nginx/site-confs/default.conf.bak
[custom-init] No custom files found, skipping...
[ls.io-init] done.Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Done