Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to 1.1.33 requires clicking Log In button #6494

Closed
PathfinderNetworks opened this issue Nov 4, 2024 · 0 comments
Closed

Update to 1.1.33 requires clicking Log In button #6494

PathfinderNetworks opened this issue Nov 4, 2024 · 0 comments
Assignees
Labels

Comments

@PathfinderNetworks
Copy link

Describe the bug
I just updated one of my MeshCentral servers to 1.1.33. At the MeshCentral logon screen (no matter if you use the normal UI or the new bootstrap version) the Enter key no longer works for when you are entering the logon password. I tried in both Edge and Chrome thinking maybe it was some recent browser change. Same issue with both browsers. I have to click the Log in button to complete the logon procedure. Whereas, previously, I could just hit Enter after entering the password.

To Reproduce
Steps to reproduce the behavior:

  1. Go to the MeshCentral logon page
  2. Enter your logon information (username and password)
  3. In the past you could just hit 'Enter' after entering the password. This is no longer working. You now need to click the Log In button to complete the log in procedure.

Expected behavior
Hitting the Enter key should do the same as clicking the Log In button.

Screenshots
If applicable, add screenshots to help explain your problem.

Server Software (please complete the following information):

  • OS: Windows Server 2022
  • Virtualization: Hyper-V
  • Network: WAN
  • Version: 1.1.33
  • Node: 22.3.0

Remote Device (please complete the following information):

  • Device: Desktop
  • OS: Windows 11 23H2
  • Network: Remote over WAN
  • Current Core Version (if known): [HINT: Go to a device then console Tab then type info]

Additional context
Seeing the same issue no matter if the traditional interface is used or if the new bootstrap version is used.

@si458 si458 self-assigned this Nov 5, 2024
si458 added a commit that referenced this issue Nov 5, 2024
Signed-off-by: si458 <simonsmith5521@gmail.com>
@si458 si458 closed this as completed Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants