Redis Cloud Console Login Stuck on Spinner

Redis Cloud Console login may sometimes get stuck on a loading spinner after entering credentials. This typically indicates a browser, session, or network issue rather than a problem with your account. This guide covers Quick Fix checks, browser and cookie configuration, step-by-step troubleshooting, and what to collect if the issue persists.

Quick Fix Table

Why this happens

Most spinner issues are caused by client-side conditions:

• Stale or corrupted session data – Cached cookies or local storage from previous sessions

• Blocked cookies or pop-ups – Required for authentication redirects (SSO, MFA)

• Browser extensions interfering – Ad blockers or script blockers breaking login flows

• Browser-specific issues – Outdated version or corrupted profile

• Network restrictions – VPNs, corporate firewalls, or DNS filtering blocking redirects

• Temporary service disruption – Rare, but possible

Prerequisites

Before troubleshooting:

• Ensure you have a stable internet connection

• Confirm your browser is up to date

• Verify there's no ongoing incident (check Redis Cloud status page if available)

Step-by-Step Troubleshooting

1. Try a clean browser session

Quick isolation test:

• Open an Incognito/Private window and retry login

• Or use a different browser (Chrome, Firefox, Edge, Safari)

What this tells you:

• If it works → the issue is local (cache, extensions, cookies)

2. Allow cookies and pop-ups

Login flows require cross-site cookies and redirects.

• Chrome / Edge

  • Settings → Privacy and security

  • Allow third-party cookies (or add site exception)

  • Allow pop-ups and redirects for Redis Cloud and identity providers

• Firefox

  • Click shield icon → Disable Enhanced Tracking Protection for the site

  • Ensure cookies and pop-ups are allowed

• Safari

  • Settings → Privacy

  • Disable “Prevent cross-site tracking” (temporarily)

  • Allow pop-ups for the site

Important: If using SSO (Google, GitHub), both Redis Cloud and the identity provider must be allowed.

3. Disable browser extensions

Extensions commonly cause login failures.

• Disable:

  • Ad blockers

  • Privacy tools

  • Script blockers

• Retry login

Best isolation method:

• Use a Guest profile (Chrome) or clean browser profile

4. Clear site data and cache

Recommended: clear only Redis Cloud-related data

• Remove:

  • Cookies

  • Local storage

  • Cached files

Then:

• Fully close the browser

• Reopen and retry login

5. Force a clean reload

• Close all tabs for Redis Cloud

• Restart browser completely

• Reload login page

Optional (Chrome/Edge):

• Open DevTools → right-click refresh → Empty Cache and Hard Reload

6. Check network restrictions

Network-level blocking is a common cause.

• Disable VPN or proxy

• Try a different network (hotspot vs corporate network)

• If on corporate network:

  • Ask IT to allow:

    • Authentication redirects

    • Identity providers (Google, GitHub, etc.)

Also verify:

• System date/time is correct (important for secure sessions)

If the issue persists

Isolate the environment:

• Try:

  • Different device

  • Different browser

  • Different network

If it only fails in one environment, the issue is local.

What to provide to Support

If you still cannot log in, include:

• Browser and version

• Whether it works in another browser or network

• Steps already attempted

• Screenshot of the spinner state

• (Optional) HAR file or console logs showing failed or blocked requests