You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
Yes / No
Are you sure you're not using someone else's docker image?
Yes / No
Have you searched for similar issues (both open and closed)?
Yes / No
Describe the bug
Email formatted content is not required in the Edit User email input field. This means a user can enter a non-email value (for example, just their name). However, the login page does enforce an email formatted value blocking the user from logging in.
Nginx Proxy Manager Version
v2.12.1
To Reproduce
Login
Edit the users email to be a non-email, for example joe
Logout
Try to login
Note: if you find yourself in this situation, in a chrome browser right click and inspect the email field on the login page, then edit the type="email" attribute on the email form to be type="text" and login.
Expected behavior
I think there are two directions here:
Update the login key to be any value (not email specific)
Enforce the email format in the Edit User page
Either are acceptable IMO.
Screenshots
Operating System
TrueNAS Scale 24.10 deployed with Docker, using the community chart.
Additional context
The text was updated successfully, but these errors were encountered:
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug
Email formatted content is not required in the
Edit User
email input field. This means a user can enter a non-email value (for example, just their name). However, the login page does enforce an email formatted value blocking the user from logging in.Nginx Proxy Manager Version
v2.12.1
To Reproduce
joe
Expected behavior
I think there are two directions here:
Edit User
pageEither are acceptable IMO.
Screenshots
Operating System
TrueNAS Scale 24.10 deployed with Docker, using the community chart.
Additional context
The text was updated successfully, but these errors were encountered: