[GH-ISSUE #1275] Login Page Broken After Upgrading to Latest Version #7825

New issue

Closed

opened 2026-03-12 22:56:20 +03:00 by kerem · 3 comments

kerem commented

2026-03-12 22:56:20 +03:00

Owner

Originally created by @benji-emd on GitHub (Jul 29, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1275

After upgrading to the latest version of the application, the login page is no longer functioning as expected. Users are unable to log in, and the page either fails to load properly or returns an error upon submitting credentials.

Steps to Reproduce:

Upgrade the application to the latest version (2.1.14).

Navigate to the login page.

Enter valid user credentials and submit the form.

Expected Result:
User should be successfully authenticated and redirected to the dashboard (or appropriate landing page).
it occurs Request Timeout as response

api/crypto/public_key => {"scope":"crypto","code":40401,"message":"request timeout"}

Additional Notes:

This issue did not exist in any of the previous versions, including v2.1.12.

Rollback to the previous version (v2.1.12) resolves the issue.

Originally created by @benji-emd on GitHub (Jul 29, 2025). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1275 After upgrading to the latest version of the application, the login page is no longer functioning as expected. Users are unable to log in, and the page either fails to load properly or returns an error upon submitting credentials. Steps to Reproduce: Upgrade the application to the latest version (2.1.14). Navigate to the login page. Enter valid user credentials and submit the form. Expected Result: User should be successfully authenticated and redirected to the dashboard (or appropriate landing page). it occurs Request Timeout as response api/crypto/public_key => {"scope":"crypto","code":40401,"message":"request timeout"} Additional Notes: This issue did not exist in any of the previous versions, including v2.1.12. Rollback to the previous version (v2.1.12) resolves the issue.

kerem

2026-03-12 22:56:20 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-12 22:56:36 +03:00

Author

Owner

@0xJacky commented on GitHub (Jul 29, 2025):

Can you login to the demo with admin/admin: https://demo.nginxui.com/#/login

@0xJacky commented on GitHub (Jul 29, 2025): Can you login to the demo with admin/admin: https://demo.nginxui.com/#/login

kerem commented

2026-03-12 22:56:41 +03:00

Author

Owner

@0xJacky commented on GitHub (Jul 29, 2025):

At the same time, the time difference between the server and the local system must be less than 10 seconds.

@0xJacky commented on GitHub (Jul 29, 2025): At the same time, the time difference between the server and the local system must be less than 10 seconds.

kerem commented

2026-03-12 22:56:47 +03:00

Author

Owner

@benji-emd commented on GitHub (Jul 29, 2025):

At the same time, the time difference between the server and the local system must be less than 10 seconds.

Thank you for the clarification. I believe this time difference requirement is exactly what's causing the issue in my case. Is there a way to bypass or disable this restriction? In my case, the server and client systems aren't always perfectly synchronized, so a workaround or option to skip this time sync check (or relax the 10-second limit) would be very helpful.

@benji-emd commented on GitHub (Jul 29, 2025): > At the same time, the time difference between the server and the local system must be less than 10 seconds. Thank you for the clarification. I believe this time difference requirement is exactly what's causing the issue in my case. Is there a way to bypass or disable this restriction? In my case, the server and client systems aren't always perfectly synchronized, so a workaround or option to skip this time sync check (or relax the 10-second limit) would be very helpful.