Loading

Troubleshoot Browser Issues in Salesforce (Cache, Cookies, Redirects, Login Failures)

Publish Date: May 30, 2026
Description

Before following the steps below, answer these questions to identify which section applies to you:

Question

What It Means

Does the issue occur in incognito or private browsing mode?

If NO → browser cache, cookies, or extension is the cause → go to Step 2. If YES → likely not browser-related → check Salesforce Trust site first

Does the issue affect only one user or multiple users?

Multiple users → check Salesforce Trust site for active incidents before troubleshooting browsers

Did the issue start after a browser update, OS update, or Salesforce maintenance?

After maintenance → go to Step 6. After browser/OS update → go to Step 2 and Step 3

Does the issue occur in a different browser?

If NO → browser-specific issue → Step 4 for Chrome, Step 5 for Firefox

Is the user on a corporate device with managed browser policies?

If YES → IT administrator may need to push cookie or extension exceptions via policy

 

Browser Cache and Cookie Conflicts
After Salesforce maintenance, Instance Refresh, Org Migrations, or browser updates, old cached data or cookies in the browser can conflict with the current Salesforce session or domain configuration. This causes symptoms that appear to be Salesforce outages but are specific to the affected user's browser state. This is the most common cause of issues that affect one user but not others on the same network.


Third-Party Cookie Blocking — Chrome and Firefox
Salesforce Lightning Experience requires third-party cookies to maintain your authenticated session across Salesforce's multiple subdomains. When Chrome or Firefox blocks these cookies — either through default browser configuration or through a privacy extension such as DuckDuckGo Privacy Essentials — pages fail to load, redirect continuously, display blank, or show the cross-domain cookie error message. In Chrome, a blocked cookie icon appears in the address bar when this is occurring.

The specific error message for this condition is:
"We can't display this page because your browser blocks cross-domain cookies."

Too Many Redirects and Blank Pages — Chrome
Chrome's third-party cookie blocking causes redirect loops and blank pages in Lightning Experience because the browser blocks the session cookie exchange that Lightning requires to authenticate between Salesforce subdomains. Each failed authentication attempt triggers a new redirect, resulting in a "too many redirects" error or a blank white page. Un-editable email body fields in Chrome are caused by this same restriction — the third-party cookie block prevents the Lightning rich text editor component from loading correctly. All three symptoms share the same root cause and are resolved by the same steps in Step 4.

Firefox Enhanced Tracking Protection
Firefox's Enhanced Tracking Protection feature blocks trackers and cross-site cookies by default. This interferes with Salesforce Lightning Experience in the same way as Chrome's cookie blocking — causing Setup menus not to display, email body fields to be un-editable, login failures, and Outlook integration login issues.

⚠️ Important — Firefox version requirement: Salesforce supports only the latest stable release of Mozilla Firefox for Lightning Experience. Older Firefox versions, including Firefox ESR (Extended Support Release), are not supported. If an issue cannot be reproduced in the current stable release of Firefox, it is outside Salesforce's support scope. See Supported Browsers and Devices for Lightning Experience for the full supported browser list.


Browser Extension Conflicts

Extensions installed in the browser can interfere with Salesforce Lightning Experience page rendering and login flows. The most reliable way to determine whether an extension is causing your issue is to test in incognito or private browsing mode — most extensions are disabled in private mode by default. If the issue disappears in private mode, an extension is the cause.

The most commonly reported conflicting extension types are as follow:

  • DuckDuckGo Privacy Essentials — After a recent update to this extension, Lightning Experience users encounter the following errors when navigating pages and records:
    "We can't display this page because your browser blocks cross-domain cookies"
    "We can't display this page because your browser blocks cross-domain cookies, but you can view this page in Salesforce Classic."  This extension blocks cross-domain cookies that Salesforce Lightning Experience requires to maintain your authenticated session. It directly causes the error "We can't display this page because your browser blocks cross-domain cookies." To resolve: click the DuckDuckGo extension icon in your browser toolbar and disable Site Privacy Protection for your Salesforce org URL, or follow Step 4 to add Salesforce domains to Chrome's cookie allowlist permanently
  • Password manager browser extensions — Extensions that auto-fill login credentials can interact with Salesforce login pages in ways that cause redirect loops or authentication failures, particularly when the extension intercepts the page before Salesforce's authentication flow completes. Disable your password manager extension temporarily and attempt to log in manually. If login succeeds without the extension, configure the extension to exclude your Salesforce org URL from auto-fill.
  • Ad blocker extensions — Ad blockers can block JavaScript components that Salesforce Lightning Experience requires to render pages correctly, resulting in blank pages, partially loaded content, or missing UI elements. Disable your ad blocker temporarily for your Salesforce org URL and reload the page. If confirmed as the cause, add your Salesforce org URL to the ad blocker's allowlist rather than disabling it globally.
  • Corporate endpoint security browser extensions — Browser components installed by corporate endpoint security or antivirus software can interfere with Lightning Experience page rendering. If you are on a corporate-managed device and experiencing rendering issues that cannot be resolved by cache clearing or extension isolation, contact your IT administrator to determine whether a corporate security tool is affecting browser behavior
  • Corporate SSO and identity management extensions — Browser extensions that enforce corporate login or identity policies can conflict with Salesforce's own SSO and authentication flow, causing login failures or redirect loops. If your organization uses a corporate SSO browser extension, contact your IT administrator to verify it is configured to permit Salesforce authentication to proceed without interception and that your My Domain URL is added to the exception configuration.
📝 Note: If you are on a corporate-managed device and cannot disable extensions yourself, provide this list to your IT administrator and request that Salesforce domains be added to the browser extension exception list. See Supported Browsers and Devices for Lightning Experience for Salesforce's official browser support documentation.
Resolution
Step 1: Test in incognito or private mode first

Before clearing any data, open an incognito (Chrome), private (Firefox/Edge), or InPrivate window and log in to Salesforce. If the issue does not occur in incognito mode, the cause is browser cache, cookies, or an extension. Proceed to Step 2.

If the issue ALSO occurs in private mode:
The cause is likely not browser-related. Before continuing:
  1. Check the Salesforce Trust site for active incidents on your instance
  2. If no active incident exists, run network diagnostics per Use Pings and Traceroutes to Troubleshoot Network Issues (000395046)

If network tests are clean and no active incident exists, contact Salesforce Support


Step 2: Clear Browser Cache and Cookies 

📝 Note: Simply closing a browser tab is not sufficient. The browser must be fully closed and all windows reopened after clearing cache. Do not use password manager autofill on the first login — navigate directly to your My Domain URL and log in fresh.

Chrome:
  1. Press Ctrl+Shift+Delete (Windows) or Cmd+Shift+Delete (Mac)
  2. Set time range to All time
  3. Check Cookies and other site data and Cached images and files
  4. Click Clear data
  5. Completely close all Chrome windows, reopen, and test Salesforce

Firefox:
  1. Press Ctrl+Shift+Delete (Windows) or Cmd+Shift+Delete (Mac)
  2. Set time range to Everything
  3. Check Cookies and Cache
  4. Click Clear Now
  5. Completely close all Firefox windows, reopen, and test Salesforce

Microsoft Edge:
  1. Press Ctrl+Shift+Delete
  2. Set time range to All time
  3. Check Cookies and other site data and Cached images and files
  4. Click Clear now
  5. Completely close all Edge windows, reopen, and test Salesforce

Safari (macOS):
  1. Go to Safari → Settings → Privacy → Manage Website Data
  2. Search for "salesforce" and remove all Salesforce entries
  3. Alternatively: enable Develop menu via Safari → Settings → Advanced → Show Develop menu, then select Develop → Empty Caches
  4. Completely close Safari, reopen, and test Salesforce
 
Step 3: Check and Disable Browser Extensions

Use this step if private mode resolves the issue but clearing cache does not — a browser extension is the cause.

Chrome:
  1. Go to chrome://extensions
  2. Toggle all extensions off
  3. Test Salesforce in a normal (non-incognito) window
  4. Re-enable extensions one at a time, testing after each, until the conflicting extension is identified
  5. For DuckDuckGo Privacy Essentials specifically: click the extension icon → toggle off Site Privacy Protection for your Salesforce org URL

Firefox:
  1. Go to Menu → Add-ons and Themes → Extensions
  2. Disable all extensions
  3. Test Salesforce in a normal (non-private) window
  4. Re-enable extensions one at a time to isolate the cause
  5. Additionally, click the shield icon in the Firefox address bar and toggle Enhanced Tracking Protection off for this site

⚠️ Important — Corporate managed devices: If you are on a corporate device with managed browser policies, individual users may not be able to modify extension or cookie settings. Your IT administrator must push the required exceptions via Group Policy (Chrome Enterprise) or Firefox policy. Refer your IT team to Allow the Required Domains on Salesforce Help.

 

Step 4: Fix Chrome Cross-Domain Cookie Errors, Redirect Loops, and Blank Pages

Use this step if Chrome displays any of the following:
  • "We can't display this page because your browser blocks cross-domain cookies"
  • Too many redirects error or redirect loop
  • Blank white page in Lightning Experience
  • Un-editable email body field in the email composer

All of these symptoms share the same root cause: Chrome is blocking the third-party cookies that Salesforce Lightning Experience requires to authenticate your session across its subdomains.

Option A — Add Salesforce domains to Chrome's cookie allowlist (Recommended permanent fix):
  1. In Chrome, go to chrome://settings/cookies
  2. Under Sites that can always use cookies, click Add
  3. Add each of the following domains exactly as shown — the [*.] notation covers all subdomains:
    • [*.]salesforce.com
    • [*.]force.com
    • [*.]content.force.com
    • [*.]visualforce.com
    • [*.]salesforceliveagent.com (required if your org uses Live Agent, Omni-Channel, or SOS Video)
    • [*.]yourcompany.my.salesforce.com (replace "yourcompany" with your actual My Domain name)
  4. Click Add after each entry
  5. Completely close all Chrome windows, reopen, and test Salesforce

💡 Note: The domain list above covers the most commonly required Salesforce domains for Lightning Experience. For a complete list of domains specific to your Salesforce products and features (Experience Cloud, Communities, Tableau, etc.), see Allow the Required Domains on Salesforce Help.

Option B — Temporarily allow all third-party cookies (diagnostic only):
  1. Go to chrome://settings/cookies
  2. Under Third-party cookies, select Allow third-party cookies
  3. Test Salesforce to confirm this resolves the issue
  4. Once confirmed, revert to Option A as the permanent fix — allowing all third-party cookies globally is not recommended as a permanent security configuration

Option C — Update Chrome to the latest version:
  1. Go to chrome://settings/help
  2. Chrome will check for and install updates automatically
  3. Restart Chrome and test

Step 5: Fix Firefox-Specific Issues (Setup Menus, Email Body, Tracking Protection, Login Failures)

Use this step for issues specific to Firefox including:
  • Setup menus not displaying or appearing blank
  • Unable to type in or access the email body field in Lightning Experience
  • Outlook integration login failures in Firefox
  • Login failures or redirect loops specific to Firefox

⚠️ Important — Firefox version requirement: Salesforce makes every effort to test and support the most recent version of Firefox. Older Firefox versions are not guaranteed to support all Salesforce features. If an issue cannot be reproduced in the most recent stable release of Firefox, it may be outside Salesforce's support scope. [Source] Download the most recent stable release of Firefox and verify before filing a support case.

⚠️ Important — Cookies must be enabled: If cookies are not enabled in Firefox, certain features managed via checkboxes will not appear — including the email composer in Lightning Experience. [Source] Ensure cookies are fully enabled in Firefox settings before troubleshooting further.
Fix 1 — Verify Firefox cookies are enabled (start here for email body issues):
  1. Go to Firefox Menu → Settings → Privacy & Security
  2. Under Enhanced Tracking Protection, confirm the setting is not blocking cookies required for Salesforce
  3. Select Custom under Enhanced Tracking Protection
  4. Uncheck Trackers
  5. Reload Salesforce and test

Fix 2 — Turn off Enhanced Tracking Protection for your Salesforce org URL:
  1. Navigate to your Salesforce org URL in Firefox
  2. Click the shield icon in the address bar to the left of the URL
  3. Click the toggle to turn Enhanced Tracking Protection off for this site
  4. Firefox will reload the page automatically — test Salesforce

Fix 3 — Update Firefox to the most recent stable release:
  1. Go to Firefox Menu → Help → About Firefox
  2. Firefox will automatically check for and install updates
  3. Restart Firefox after updating and test Salesforce
  4. Confirm you are on the most recent stable release

Fix 4 — Refresh Firefox for persistent issues (resets settings, preserves data):
  1. Go to Firefox Menu → Help → More Troubleshooting Information
  2. Click Refresh Firefox
  3. This resets Firefox add-ons and modified settings while preserving your bookmarks and saved passwords
  4. Test Salesforce after the refresh

Step 6: After Salesforce Maintenance — Special Instructions
Use this step if the issue started immediately after a Salesforce scheduled maintenance window.

Salesforce maintenance can cause browser-side symptoms even when infrastructure is healthy because:
  • Session tokens issued before maintenance are invalidated after the window completes
  • Cached Lightning component bundles become stale when new versions are deployed during maintenance
  • DNS changes during maintenance can cause the browser to temporarily serve a cached old IP

Resolution steps after maintenance:
  1. Clear cache and cookies fully per Step 2
  2. Completely close the browser — all windows, not just the active tab
  3. Reopen the browser
  4. Navigate directly to your My Domain URL — do not follow a bookmark to a legacy instance URL such as na45.salesforce.com
  5. Log in fresh — do not use password manager autofill on the first post-maintenance login
  6. If the issue persists, wait 15 minutes and retry — DNS propagation after maintenance can take a short period to fully resolve

💡 Note: If users have bookmarked a legacy instance URL (for example, `instance.salesforce.com`) instead of their My Domain URL, they will repeatedly experience cache-related issues after every maintenance window. Update all bookmarks to your mydomain `yourcompany.my.salesforce.com` to prevent recurrence.

Step 7: Switch to a Supported Browser

If the issue persists after all steps above, switch to a different Salesforce-supported browser:


FAQ
If the issue is specific to one browser and does not reproduce in any other supported browser, the cause is a browser version, extension, or policy conflict — not a Salesforce platform issue. Check the Salesforce Known Issues site for browser-specific known issues before filing a support case.

The issue happens for one user but not others on the same network. Is it a browser or account issue?
When an issue affects one user but not others on the same network, the cause is almost always the individual user's browser cache, cookies, or a browser extension — not a Salesforce infrastructure or network issue. Have the affected user clear their cache (Step 2) and test in incognito mode (Step 1). If the issue persists on one machine only, check for antivirus software, group policy settings, or other locally installed applications interfering with the browser.

Clearing cache resolved the issue, but it keeps coming back. What causes this?
Recurring cache-related issues most commonly occur when a user has bookmarked a legacy instance URL (for example, na45.salesforce.com) instead of their My Domain URL. Update the bookmark to MyDomain example: yourcompany.my.salesforce.com. Recurring issues also occur after Salesforce maintenance when the browser re-caches stale Lightning component bundles — always perform a full browser close and reopen after clearing cache following maintenance.

A user cannot log in even after clearing cache. The error references "login error" or random error code.
Error code is a session token validation failure — the browser is presenting an expired or invalidated session token. This most commonly occurs after a Salesforce maintenance window that reset active sessions. If clearing cache and cookies does not resolve it, verify:
  1. The user's IP address is within the trusted IP range in Setup → Network Access
  2. No recent network, VPN, or SSO configuration changes have affected login access
  3. The user is navigating to their My Domain URL — not a legacy instance URL
  4. If the user is on a VPN, test login with VPN disconnected to determine whether the VPN is applying an IP restriction

I disabled the DuckDuckGo Privacy Essentials extension but the error still appears. What else can I try?
After disabling the extension, fully close all Chrome windows and reopen Chrome — closing only the tab is not sufficient. If the cross-domain cookie error persists, the block is coming from Chrome's native cookie settings rather than the extension. Follow Step 4 Option A to add the Salesforce domains to Chrome's cookie allowlist at chrome://settings/cookies.
Knowledge Article Number

005385647

 
Loading
Salesforce Help | Article