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

Better error scheme for gateway ui faililng to connect to the gateway #514

Open
Kodylow opened this issue Sep 3, 2024 · 3 comments
Open

Comments

@Kodylow
Copy link
Member

Kodylow commented Sep 3, 2024

currently just always gives invalid password

@kleyberthsantos
Copy link
Contributor

kleyberthsantos commented Nov 13, 2024

Hi Kody, I attempted to replicate the error in different scenarios, but I was unable to get the same result.
Here are the details of the tests I performed:

Invalid password with gateways active
Result: Error fetching gateway info with Status: 401 Unauthorized.
Gateway Access Feedback

Correct password with gateways active
Result: Error fetching balance with Status: 404 Not Found.
Gateway Access Feedback (1)

Invalid password with one gateway active
Result: Error fetching gateway info with Status: 401 Unauthorized.
Gateway Access Feedback (2)

Correct password with one gateway active
Result: Error fetching balance with Status: 404 Not Found.
Gateway Access Feedback (3)

If you could provide more details about the environment in which the error occurred or additional specific steps, it would help me investigate further and better understand the issue.

@Kodylow
Copy link
Member Author

Kodylow commented Nov 15, 2024

that 3rd picture is the issue: if you put the correct password in when the gateway is down it doesn't give you a failed to connect error, it gives you a 401 unauthorized

@kleyberthsantos
Copy link
Contributor

WIP 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants