[GH-ISSUE #530] Is the session broken now? #4703

New issue

Closed

opened 2026-03-01 15:35:22 +03:00 by kerem · 4 comments

kerem commented

2026-03-01 15:35:22 +03:00

Owner

Originally created by @tamr on GitHub (Aug 31, 2024).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/530

Some versions ago I noticed being welcomed by "Authorization failed" message on the login screen. I see the secure_session_id cookie has the value of "undefined". Previously the session worked just fine even after upgrades.

Originally created by @tamr on GitHub (Aug 31, 2024). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/530 Some versions ago I noticed being welcomed by "Authorization failed" message on the login screen. I see the secure_session_id cookie has the value of "undefined". Previously the session worked just fine even after upgrades.

kerem

2026-03-01 15:35:22 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-01 15:35:23 +03:00

Author

Owner

@0xJacky commented on GitHub (Sep 1, 2024):

Hi @tamr，did you enable 2FA?

@0xJacky commented on GitHub (Sep 1, 2024): Hi @tamr，did you enable 2FA?

kerem commented

2026-03-01 15:35:23 +03:00

Author

Owner

@tamr commented on GitHub (Sep 1, 2024):

Hi @tamr，did you enable 2FA?

Nope, I have restricted it by ip with deny all. I think it started to ask for the login 2 updates ago.

@tamr commented on GitHub (Sep 1, 2024): > Hi @tamr，did you enable 2FA? Nope, I have restricted it by ip with deny all. I think it started to ask for the login 2 updates ago.

kerem commented

2026-03-01 15:35:23 +03:00

Author

Owner

@0xJacky commented on GitHub (Sep 1, 2024):

Do you mean you have configured IP access restrictions for the Nginx UI in your Nginx configurations?

@0xJacky commented on GitHub (Sep 1, 2024): Do you mean you have configured IP access restrictions for the Nginx UI in your Nginx configurations?

kerem commented

2026-03-01 15:35:23 +03:00

Author

Owner

@0xJacky commented on GitHub (Sep 1, 2024):

The "Authorization failed" message displayed on the login screen is not a bug. When the JWT expires (currently after 24 hours), you will be prompted with "Authorization failed" and asked to log in again.

@0xJacky commented on GitHub (Sep 1, 2024): The "Authorization failed" message displayed on the login screen is not a bug. When the JWT expires (currently after 24 hours), you will be prompted with "Authorization failed" and asked to log in again.