Closed Marcus1Pierce closed 4 months ago
I manage it my self. Nextcloud and Notify Push container can't resolve my nextcloud.domain.tld so i edit my docker-compose to
nextcloud-notify-push:
image: nextcloud:27-fpm
container_name: nextcloud-notify-push
restart: always
user: www-data
entrypoint: /var/www/html/custom_apps/notify_push/bin/aarch64/notify_push /var/www/html/config/config.php
networks:
- default
ports:
- 7867:7867
depends_on:
- nextcloud-postgres
- nextcloud-postgres-snappymail
- nextcloud-redis
environment:
- TZ=Asia/Jakarta
- PORT=7867
- NEXTCLOUD_URL=https://nextcloud.domain.tld
volumes:
- ${nextcloud}/server:/var/www/html
- ${nextcloud}/nextcloud_data:/var/www/html/data
extra_hosts:
- nextcloud.domain.tld:my.host.ip.address
Add extra_hosts
make it work
I have issue with notify_push using manual setup in Nextcloud Docker. I run notify_push using docker-compose like this:
When i run php occ notify_push:setup https://nextcloud.domain.tld/push i have this error
When i open https://nextcloud.domain.tld/push/test/reverse_cookie result is
error sending request for url (https://nextcloud.domain.tld/index.php/apps/notify_push/test/cookie): error trying to connect: tcp connect error: Connection refused (os error 111)
Logs on nextcloud-notify-push container
When i open https://nextcloud.domain.tld/index.php/apps/notify_push/test/version it just give me
1 | null
https://nextcloud.domain.tld/index.php/apps/notify_push/test/cookie give me
1 | 847648800
I use caddy for reverse proxy and i setup notify_push like this
I run this on: Raspberry Pi 4B Debian GNU/Linux 12 (bookworm) aarch64 Docker version 26.0.1, build d260a54 Nextcloud 27.1.8 Client Push 0.6.10