nextcloud / nextcloud/notify_push
`502 Bad Gateway` after setup
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
I've set up notify_push on my FreeBSD 15.1 server. There are no errors in the log, so I have absolutely nothing to work with. The command line to start it is /usr/local/www/nextcloud/apps/notify_push/bin/fbsd_amd64/notify_push /usr/local/www/nextcloud/config/config.php, and it is run - like PHP - as user www.
The proxy is set up as listed in the README:
location ^~ /push/ {
proxy_pass http://127.0.0.1:7867/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
I've also set the env var PORT=7867 just to make sure.
Here's the output trying to run setup with the URL:
root@nextcloud:~ # occ notify_push:setup https://nextcloud.lyrion.ch/push
✓ redis is configured
🗴 can't connect to push server: Server error: `GET https://nextcloud.lyrion.ch/push/test/cookie` resulted in a `502 Bad Gateway` response:
<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>ngin (truncated...)
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
Start with the README reverse-proxy setup and the occ notify_push:setup entry point, then trace the /push/test/cookie request through the proxy and push server using the supplied command and configuration. Confirm the cause of the 502 on FreeBSD 15.1 and document a reproducible configuration or a clearly identified compatibility issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx, rust
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100