[Bug]: Try to use program (Auth error 401)

[MatVasylenko]

• Download redisinsights from site
• Work some days

Today have 401 error 🙂‍↔️

[ZantsuRocks]

Same here, it blinks the interface for a brief period then goes black forever.

[ItzHoffe]

In network tab:
{message: "Authorization failed", statusCode: 401, error: "CloudApiUnauthorized", errorCode: 11001}

[kaedros]

Description

When accessing the Redis interface, the screen remains completely black/blank. Inspection via browser DevTools reveals failed API requests returning HTTP 401 Unauthorized with the message:

Authorization failed

Actual Behavior

Blank/black screen (UI fails to render)

Additional Information

• Redis Insight version: 7.0.15
• Ubuntu 0.24.04.2

[jaceenet]

Same error same issue

[snowden-simna]

Same issue - believe it's affected by the AWS outage?

[MatVasylenko]

Same issue - believe it's affected by the AWS outage?

I thinks yes - because today also have problem with jira & bitbucket etc - It seems like everything has been fixed, but maybe Redis hasn't updated anything yet🧐

[ZantsuRocks]

A software running locally on a machine, which doesn’t necessarily require a paid service to operate, being completely broken due to another service that doesn’t directly impact its functionality seems wrong to me.
I believe the Redis team should reconsider this and at least allow limited free use in such cases.

[pernydev]

This is just actually sad. How can a local application have such reliance on the cloud, without even providing proper errors.

[pedrograaff]

Same issue

[Parsonswy]

I could not find a documented way to clear my Redis Insights session. I have a Ubuntu Snap install and the data persisted even after multiple re-installs and snapshot purges.

Doing the following I was able to hack my way to a new session:

1. Launch Redis Insights and let it fail to load.
2. Right click anywhere in the window and select inspect element.
3. Navigate to the network tab and change throttling to 3G (keep this panel open).
4. In the top left under the "View" menu click "Reload." The interface will slowly load in.
5. Once you see the "sign in with Redis" option in the top right change the throttling mode in the network tab to "offline." This will block the failing /me request from finishing with the 401 that is breaking everything. Blocking the failing /me request is important and may take a few tries. The window between the sign in button loading and the /me request completing was only a few seconds.
6. Change the throttling setting in the network tab back to "no throttling."
7. At this point I had the sign-in popup and was able to get a new session and the app worked normally from there.

Hopefully this helps while they presumably fix the session handling to not soft-lock the app.

[yj2280]

Same issue

[wilac-pv]

this good idea

[oriondesign2015]

I fixed the issue in this PR:
#5085

If you can, please upvote it to help expedite the review and merge.