NginxProxyManager / NginxProxyManager/nginx-proxy-manager
PATCH requests blocked by default?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
I'm having an issue with appwrite ( and had a similar one with supabase ).
Both use PATCH requests, to update some settings from the UI.
I get a 504 and it's just hanging and timing out.
I am pretty sure nginx proxy manager is blocking it, because the docker compose of appwrite works fine locally. when behind NPM, I cannot get this PATCH endpoint to work, so I cannot apply any changes from the admin UI.
Is there any way to disable that? Or add a custom rule or something?
I tried unchecking the "block common exploits" but it didn't help.
Contributor guide
No contributing guide indexed for this repository
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 names Appwrite, Supabase, the admin UI, a PATCH endpoint, Docker Compose, and Nginx Proxy Manager; start by reproducing the timeout locally and behind NPM. Compare behavior with “block common exploits” enabled and disabled, then identify whether the proxy is rejecting or mishandling PATCH requests. Done means documenting a supported configuration or confirming the behavior as a product bug.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, nginx
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100