nextcloud / nextcloud/notify_push
Trusted proxies issue: configuration behind Haproxy
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
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!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report points to the README troubleshooting section and the NEXTCLOUD_URL setting for deployments behind HAProxy. Read that section first; done means the guidance clearly explains the internal HTTP URL and the separate proxy/TLS configuration.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100