You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NextcloudPi version v1.51.4
NextcloudPi image NextcloudPi_docker_05-01-23
OS Debian GNU/Linux 11. 5.15.84-v8+ (aarch64)
automount no
USB devices sda sdb sdc
datadir /data/nextcloud/data
data in SD no
data filesystem ext2/ext3
data disk usage 264G/916G
rootfs usage 10G/29G
swapfile /var/swap
dbdir /data/database
Nextcloud check ok
Nextcloud version 24.0.3.2
HTTPD service up
PHP service up
MariaDB service up
Redis service up
HPB service up
Postfix service up
Internet check ok
Public IPv4 ***REMOVED SENSITIVE VALUE***
Public IPv6 ***REMOVED SENSITIVE VALUE***
Port 80 open
Port 443 open
IP ***REMOVED SENSITIVE VALUE***
Gateway ***REMOVED SENSITIVE VALUE***
Interface eth0
Certificates ***REMOVED SENSITIVE VALUE***
NAT loopback no
Uptime 158days
Add support for Nextcloud 26.0.3
### Changes
- Adds support for NC 26.0.3
- Add ZFS support for the data directory (#1767)
### Fixes
- Fix bug in ncp-backup (#1791)
- Fix missing configuration field for nc-backup-auto (#1787)
Setting up nc-backup-auto exits with the error message ERROR: 'BACKUPHOUR' must be a number between 0 and 24, was: '$BACKUPHOUR'.
I was able to narrow down the issue to a missing parameter line for this new introduced parameter both within ncp-config and ncp-web.
A quick workaround for me was setting
BACKUPHOUR
hardcoded inside the scriptnextcloudpi/bin/ncp/BACKUPS/nc-backup-auto.sh
after line 50.System information
<--! Paste this in GitHub report -->
NextcloudPi diagnostics
Nextcloud configuration
The text was updated successfully, but these errors were encountered: