Trusted proxies issue: configuration behind Haproxy

[sm8ps]

I hope it is okay to write a solution instead of an issue here. After hours of searching here and everywhere else on the internet I finally stumbled over a solution that may help others. My problem was that all how-tos seem use https:// followed by a DNS-name for NEXTCLOUD_URL. It took me quite some time of staring at it before I realized that there are two knobs that can be turned separately.

My Nextcloud server is behind a HA proxy that does TLS-termination. So in hindsight it is pretty obvious that NEXTCLOUD_URL should be given with http://. Just as suggested in the troubleshooting part of the readme it took the internal IP-address of the server to make it all work.

Thanks a lot for providing this useful piece of software!

[ikke-t]

Biggest hurdle for me has been the liveness check for notify_push so that haproxy opens it up for traffic. I wasted quite a lot of hours trying to get 200 response from the 7867 port. I totally failed until I realized to enable metrics for HAproxy liveness check. I didn't get any proper answer (other than 4xx) with curl from 7867 port, nor it logs anything from container. But after enabling port 7868 for metering, it nicely responds to liveness checks from url:7868/metrics. Even though instructions in README say you could use the same port for metrics, you can't, as the rust program will panic as it can't bind the metrics to normal notify port.

But with that it works with haproxy. Would be easier if notify push would have some /ping or /status endpoint for liveness probes.