Closed aMU5Ed closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Same Problem
We need the template filled in properly with container logs and docker run or compose yaml
A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.
@aptalca Sorry for any inconvinience but this one of my first issues on Github. Here is the container log: [migrations] started [migrations] 01-nginx-site-confs-default: skipped [migrations] 02-default-location: skipped [migrations] done usermod: no changes ───────────────────────────────────────
██╗ ███████╗██╗ ██████╗
██║ ██╔════╝██║██╔═══██╗
██║ ███████╗██║██║ ██║
██║ ╚════██║██║██║ ██║
███████╗███████║██║╚██████╔╝
╚══════╝╚══════╝╚═╝ ╚═════╝
Brought to you by linuxserver.io ───────────────────────────────────────
To support LSIO projects visit: https://www.linuxserver.io/donate/
─────────────────────────────────────── GID/UID ───────────────────────────────────────
User UID: 99 User GID: 100 ───────────────────────────────────────
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 │ ├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤ │ 2018-08-16 │ 2023-04-13 │ /config/nginx/nginx.conf │ │ │ 2023-06-23 │ /config/nginx/site-confs/default.conf │ └────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘ [custom-init] No custom files found, skipping... [ls.io-init] done.
Here is the docker run command: docker run -d --name='nextcloud' --net='br0' --ip='192.168.1.204' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="unraid" -e HOST_CONTAINERNAME="nextcloud" -e 'TCP_PORT_443'='443' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='https://_mysubdomain.mydomain_' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/nextcloud-icon.png' -v '/mnt/user/nextcloud_data/':'/data':'rw' -v '/mnt/user/nextcloud_scanner/':'/scanner':'rw' -v '/mnt/user/appdata/nextcloud':'/config':'rw' 'linuxserver/nextcloud'
This is a nextcloud issue: https://github.com/nextcloud/files_fulltextsearch/issues/221 Workaround is: occ app:disable files_fulltextsearch
Is there an existing issue for this?
Current Behavior
After upgrading the docker container from 26.0.2 to 27.0.0 I have following experience. File sync basically works but desktop and mobile client are sting an HTTP 500. Webinterface is not accessable because of:
Interner Serverfehler Der Server konnte die Anfrage nicht fertig stellen.
Sollte dies erneut auftreten, sende bitte die nachfolgenden technischen Einzelheiten an deinen Server-Administrator.
Weitere Details können im Server-Protokoll gefunden werden.
Technische Details Entfernte Adresse: 192.168.1.31 Anfragekennung: 1xLCGuaY1JohNusWGOZI
I have the follwing error in the nextcloud.log
So webinterface is not accessable at all.
Expected Behavior
Webinterface and desktop sync should work.
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs