hassio-addons: Nextcloud : One of the updates over the last couple of weeks is causing permission denied error
2023/03/28 07:30:18 [error] 2481#2481: *12019 open() "/data/config/www/nextcloud/robots.txt" failed (13: Permission denied), client: 127.0.0.1, server: _, request: "GET /robots.txt HTTP/1.1", host: "127.0.0.1" 127.0.0.1 - - [28/Mar/2023:07:30:18 -0700] "GET / HTTP/1.1" 400 248 "-" "curl/7.88.1"
not sure whats going on. it says it mounts my network share fine, maria db seems to be running fine.
`GID/UID ─────────────────────────────────────── User UID: 1000 User GID: 1000 ─────────────────────────────────────── Add-on version: 26.0.0-4 You are running the latest version of this add-on. System: Home Assistant OS 9.5 (aarch64 / raspberrypi4-64) Home Assistant Core: 2023.3.6 Home Assistant Supervisor: 2023.03.2
Please, share the above information when looking for help or support in, e.g., GitHub, forums https://github.com/alexbelgium/hassio-addons
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0 cont-init: info: running /etc/cont-init.d/01-custom_script.sh [07:36:27] INFO: Execute /config/addons_autoscripts/nextcloud-ocr.sh if existing [07:36:27] INFO: … no script found cont-init: info: /etc/cont-init.d/01-custom_script.sh exited 0 cont-init: info: running /etc/cont-init.d/01-folders.sh Checking permissions …done
cont-init: info: /etc/cont-init.d/01-folders.sh exited 0 cont-init: info: running /etc/cont-init.d/02-init_steps.sh Cleaning files Setting logs
Nextcloud 24.0.5 is installed
New version available : 26.0.0 …auto_updater not set in addon options, please update from nextcloud settings cont-init: info: /etc/cont-init.d/02-init_steps.sh exited 0 cont-init: info: running /etc/cont-init.d/02-mariadb_discovery.sh
MariaDB addon was found! It can’t be configured automatically due to the way Nextcloud works, but you can configure it manually when running the web UI for the first time using those values : Database user : service bashio::log.blue Database user : service Database password : xxxxxx Database name : xxxx Host-name : core-mariadb:3306
cont-init: info: /etc/cont-init.d/02-mariadb_discovery.sh exited 0 cont-init: info: running /etc/cont-init.d/30-ssl.sh cont-init: info: /etc/cont-init.d/30-ssl.sh exited 0 cont-init: info: running /etc/cont-init.d/92-local_mounts.sh cont-init: info: /etc/cont-init.d/92-local_mounts.sh exited 0 cont-init: info: running /etc/cont-init.d/92-smb_mounts.sh Mounting smb share(s)… Using PUID 1000 and PGID 1000 [07:36:38] INFO: … //192.168.0.116/i/nextcloud successfully mounted to /mnt/nextcloud with options cont-init: info: /etc/cont-init.d/92-smb_mounts.sh exited 0 cont-init: info: running /etc/cont-init.d/99-add_packages.sh [07:36:38] INFO: Installing additional apps : … inotify-tools cont-init: info: /etc/cont-init.d/99-add_packages.sh exited 0 cont-init: info: running /etc/cont-init.d/99-elasticsearch.sh cont-init: info: /etc/cont-init.d/99-elasticsearch.sh exited 0 cont-init: info: running /etc/cont-init.d/99-ocr.sh cont-init: info: /etc/cont-init.d/99-ocr.sh exited 0 cont-init: info: running /etc/cont-init.d/99-trusted_domains.sh [07:36:41] INFO: Currently set trusted domains : Could not open input file: /data/config/www/nextcloud/occ [07:36:42] INFO: No trusted domain set yet. The first one will be set when doing initial configuration [07:36:42] INFO: Trusted domains set in the configuration. Refreshing domains. [07:36:42] INFO: … removing previously added trusted domain (except for first one created) Could not open input file: /data/config/www/nextcloud/occ cont-init: info: /etc/cont-init.d/99-trusted_domains.sh exited 1 Setting resolver to 127.0.0.11 Setting worker_processes to 4 using keys found in /data/config/keys
do daily/weekly/monthly maintenance
min hour day month weekday command
*/15 * * * * run-parts /etc/periodic/15min 0 * * * * run-parts /etc/periodic/hourly 0 2 * * * run-parts /etc/periodic/daily 0 3 * * 6 run-parts /etc/periodic/weekly 0 5 1 * * run-parts /etc/periodic/monthly
nextcloud cron
*/5 * * * * (s6-setuidgid abc php -f /data/config/www/nextcloud/cron.php) &>/proc/1/fd/1 [custom-init] No custom files found, skipping… services-up: info: copying legacy longrun cron (no readiness notification) [ls.io-init] done. [28-Mar-2023 07:36:43] NOTICE: fpm is running, pid 572 [28-Mar-2023 07:36:43] NOTICE: ready to handle connections 2023/03/28 07:36:44 [error] 610#610: *1 open() “/data/config/www/nextcloud/robots.txt” failed (13: Permission denied), client: 127.0.0.1, server: _, request: “GET /robots.txt HTTP/1.1”, host: “127.0.0.1” 127.0.0.1 - - [28/Mar/2023:07:36:44 -0700] “GET / HTTP/1.1” 400 248 “-” “curl/7.88.1”`
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 62 (30 by maintainers)
Commits related to this issue
- Convert scripts to unix before execution https://github.com/alexbelgium/hassio-addons/issues/775 — committed to alexbelgium/hassio-addons by alexbelgium a year ago
- Clarify default datadirectory if nextcloud not installed https://github.com/alexbelgium/hassio-addons/issues/775 — committed to alexbelgium/hassio-addons by alexbelgium a year ago
- check_data_directory_permissions = false https://github.com/alexbelgium/hassio-addons/issues/775 — committed to alexbelgium/hassio-addons by alexbelgium a year ago
- New version https://github.com/alexbelgium/hassio-addons/issues/775 — committed to alexbelgium/hassio-addons by alexbelgium a year ago
- 2023 logic for removing permissions check https://github.com/alexbelgium/hassio-addons/issues/775 — committed to alexbelgium/hassio-addons by alexbelgium a year ago
Yes everything is working properly. Thanks so much for your help again.
Nailed it, thank you. Also just so I know, when do you recommend updating? I wasn’t aware I shouldn’t be updating when I was back on v24.
I use nextcloud to sync all the data from my phones to my NAS, and then that syncs to an old pixel 1 to use unlimited raw photo backup to Google photos lol
Ok, got the reinstall to work, specified /mnt/nextcloud on the config page at install, install went fine, but same error "Error Your data directory is readable by other users.
Please change the permissions to 0770 so that the directory cannot be listed by other users."
I’m assuming this is because the data directory is being held on a samba share. If I remember correctly, I had this issue about a year ago, and you pushed a fix to disable the check in nextcloud. Why can’t I override this as an admin?
i’m reading users are adding “‘check_data_directory_permissions’ => false,” to the config. Ridiculous this is required.
can I add that to the yaml or do I need to do it from docker?
odd because im pretty positive I had it in the config on first install. regardless, can I access the file system from portainer and edit it in a visual editor? I suck at editing configs via command line