NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Allow defining custom messages/pages for 404 Hosts
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Is your feature request related to a problem? Please describe.
I would like to define some additional info in HTMLs returned by 404 hosts like (this website does not exist anymore because...)
Describe the solution you'd like
Adding simple form in 4040 host config
Describe alternatives you've considered
Changing HTML of default site, but it won't be sufficient
Additional context
It may be linked with https://github.com/NginxProxyManager/nginx-proxy-manager/issues/26
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 reading the linked issue #26 and tracing how the current 404 host and default-site HTML are selected. Define the configuration and UI scope before implementation; done should allow a 404 host to provide custom HTML or additional information instead of relying only on the default site.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100