NginxProxyManager / NginxProxyManager/nginx-proxy-manager
No Logging: Invalid password or No relevant user found
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Discussed in https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/4096
Originally posted by wforumw October 21, 2024
Hi,
We use fail2ban to block unwanted IP's. When an IP is blocked by a rule it is logged in NPM log files like
[error] 208#208: *1046 access forbidden by rule, client: x.x.x.x, server: npmservr, request: "GET /api/ HTTP/2.0", host: "npmservr", referrer: "npmservr"
so it is easy to filter these by fail2ban.
Now when a login is unauthorized, on the website we get
Invalid password
or
No relevant user found
but nothing is logged in the NPM log files.
Is there a way to get these logged also?
Thanks!
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 issue mentions the NPM log files, the website login flow, and the "Invalid password" and "No relevant user found" responses, but names no source file or test. Start by tracing the login endpoint that produces those messages; done means unauthorized login attempts appear in NPM logs in a form that fail2ban can filter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx, typescript
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100