NginxProxyManager / NginxProxyManager/nginx-proxy-manager
421 Misdirected Request
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Hi everyone. I hope someone can point me in the right direction.
As the title suggests, after an update to Apache (maybe) every time I try a to access a website on my homelab I always get this error.
Apache logs says:
[ssl:error] [pid 2013861:tid 140388841018944] [client 192.168.2.180:36498] AH02032: Hostname xxxxxx.xxxxx.xxx (default host as no SNI was provided) and hostname yyyyyy.yyyyyy.yyy provided via HTTP have no compatible SSL setup
I found this article but I don't know if it's relevant: https://support.plesk.com/hc/en-us/articles/33500191748887-Websites-hosted-in-Plesk-are-not-accessible-after-a-recent-Apache-update-421-Misdirected-Request
From the article:
In recent Apache version, Apache team has released fixes for CVEs that affected Apache + nginx functionality: new changes do not allow Apache process requests from nginx without the server name (by default, nginx does not pass the server name through SNI when establishing a connection with a proxied HTTPS server).
I tried my best to add those options to nginx-proxy-manager but after a restart they are lost.
I'm currently using the latest release, but I have tried with older versions but with no success.
Any advice?
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
Start by tracing how nginx-proxy-manager stores and applies the requested proxy options, then compare that configuration with the Apache AH02032 log and the linked Apache/nginx guidance. Done means the relevant options persist after restart and the reported 421 error no longer occurs, but the issue names no specific repository file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100