weird, anything in /var/log/ncp.log (also can check from ncp-web)
Hm, it says it is configured in the logs… (edit: just the redis server)
root@01bc8618bcad:/# cat /var/log/ncp.log
Fri Oct 22 06:40:46 UTC 2021 - Running /etc/cron.daily/ncp-autoupdate...
[ nc-update-nc-apps-auto ]
checking for updates...
[ nc-limits ] (Fri Oct 22 19:19:36 UTC 2021)
Using 2907377664B for PHP
Using 6 PHP threads
Using 918794240 memory for the database
Stopping redis-server: redis-server.
Starting redis-server: redis-server.
System config value trusted_domains => 3 set to string <domain>
System config value overwrite.cli.url set to string <domain>
System config value trusted_proxies => 11 set to string 127.0.0.1
System config value trusted_proxies => 12 set to string ::1
System config value trusted_proxies => 13 set to string <domain>
System config value trusted_proxies => 14 set to string <external ip>
✓ redis is configured
🗴 push server is not receiving redis messages (received 877806118, got 0)
Should I add the docker-container IP as trusted domain?
Maybe it’s best to read about the HPB before getting into it, I have no clue if I should have configured something to make it work? I don’t want to bother you too much 
does this change anything?
bash /usr/local/bin/nextcloud-domain.sh
root@01bc8618bcad:/# bash /usr/local/bin/nextcloud-domain.sh
System config value trusted_domains => 11 set to string <public ip>
/usr/local/bin/nextcloud-domain.sh: line 16: 172.17.0.3: syntax error: invalid arithmetic operator (error token is ".17.0.3")
System config value trusted_domains => 22 set to string 01bc8618bcad
Still no push server, restarted the container as well:
root@01bc8618bcad:/# ncc notify_push:self-test
🗴 no push server configured
I could add my docker ip manually?
hmm that error is a bit weird. Do you mind editing /usr/local/bin/nextcloud-domain.sh, then adding the line set -x in the second line (after #!/bin/bash), running again and sharing output?
thanks
actually nevermind, I was able to reproduce
if you run ncc config:system:get trusted_domains, do you see your docker local IP there?
NOTE: The printed error shouldn’t affect, but it’s now gone in the latest version
Yes, the local docker IP is in the list: 172.17.0.3
thanks, and if you run this, you get a redis error, right?
ncc notify_push setup https://172.17.0.3/push
Yay, now it works!
You missed a :, it’s:
ncc notify_push:setup https://172.17.0.3/push but then everything got configured properly and HPB is up now.
NextCloudPi version v1.42.3
NextCloudPi image NextCloudPi_docker_09-20-21
OS Debian GNU/Linux 10. 5.10.60-meson64 (aarch64)
automount no
USB devices sda sdb
datadir /data/nextcloud/data
data in SD no
data filesystem btrfs
data disk usage 2.1T/3.7T
rootfs usage 7.9G/29G
swapfile none
dbdir /data/database
Nextcloud check ok
Nextcloud version 21.0.5.1
HTTPD service up
PHP service up
MariaDB service up
Redis service up
HPB service up
Postfix service up
internet check ok
port check 80 open
port check 443 open
IP 172.17.0.3
gateway 172.17.0.1
interface eth0
certificates none
NAT loopback no
uptime 5days
(I updated from NC21.0.4 to NC21.0.5 yesterday as I had a weird MariaDB error (twice) which solved itself by restarting the container.) I noticed that the NC-updater has been empty for a while. Is that to prevent people updating via the NC-web interface instead of NCP?
Thanks again for your help! Really good job with NCP!
that’s exactly right. It was very confusing for NCP users.
But it goes down again when you restart the container, I suppose? that’s where I am trying to get at, seems to be a thing unique to you
I’m having this same error. When I run
ncc notify_push:setup https://10.0.7.6/push
I get
✓ redis is configured
✓ push server is receiving redis messages
✓ push server can load mount info from database
🗴 push server can't connect to the Nextcloud server
XXXX is not configured as a trusted domain
Do you know what i need to do? This happened after updating to 22.2.2.0 via ncp-config.
Let’s Encrypt got fubar so I removed /etc/letsencrypt and ran it again from ncp-config. This has worked in the past but not this time.