mirror of
https://github.com/0xJacky/nginx-ui.git
synced 2026-04-25 08:45:58 +03:00
[GH-ISSUE #342] Authorization failed when link start to a wrong environment #4623
Labels
No labels
Q/A
bug
casdoor
dependencies
docker
documentation
duplicate
enhancement
help wanted
invalid
lego
platform:openwrt
platform:windows
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-ui#4623
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @leic4u on GitHub (Apr 1, 2024).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/342
Describe the bug
There are 3 Nginx-UI on 3 VPS. we could call them S1, S2, S3.
S3 was linked to the others.
A few days ago, the domain of S1 was expired, then I changed the DNS of S1.
Today I logged in Nginx-UI on S3, and found that S1 was disconnected, then I clicked the LINK START button, and I was be forced logout from Nginx-ui on S3.
Just like this: (and I lose the Nginx-UI on S1 after I click the button)
When I want to login, the Nginx-UI tells me Authorization failed.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Login correctly.
Info (please complete the following information):
@nianzecong commented on GitHub (Apr 12, 2024):
same issue
@nianzecong commented on GitHub (Apr 12, 2024):
A front-end stored configuration is causing this issue. Open the browser console, delete the data in storage under 'settings', refresh the page, and log in again to fix the issue.
@0xJacky commented on GitHub (Apr 27, 2024):
I am sorry that I can't reproduce this issue. First I login in into S1 and click link start to S2, then I stop the nginx-ui on S2. I can logout and login again.
By the way, we did not proxy the login request to the target server you linked to.
@leic4u commented on GitHub (Apr 27, 2024):
Try to fill in a wrong url to click the Link Start?
@0xJacky commented on GitHub (Apr 28, 2024):
Still can not reproduce.
@leic4u commented on GitHub (Apr 28, 2024):
I could reporduce this issue everytime...
The simplest way is to delete one letter from Node Secret of S2, making the enviroment wrong.
I test it in the latest version of Chrome. And I can solve this issue by using the method @nianzecong provided in https://github.com/0xJacky/nginx-ui/issues/342#issuecomment-2051097567 .