Article Summary
This article provides troubleshooting steps to resolve the "Could not load credential" error that prevents users from accessing the Reservation Zone, connecting channels, or modifying existing client accounts. The primary root cause is a local browser cache or cookie conflict.
Symptoms and Impact
Error Message: "Could not load credential" appears when attempting to access the Reservation Zone:
- Access Blocked: Users are unable to navigate to the reservation zone for new clients.
- Workflow Impact: Blocks the ability to establish or modify channel credentials.
Root Cause
The "Could not load credential" error is triggered by corrupted or outdated local browser cache and cookie data. This stale data conflicts with the authentication mechanism, preventing the system from validating user credentials.
Resolution Steps
Step 1: Verify Access with Incognito Mode
To isolate the issue from your primary browser environment, access the portal using a private or incognito window.
- Open an Incognito (Chrome) or Private (Firefox/Safari) browser window.
- Navigate to the client login portal.
- Authenticate (using 2FA if prompted) and attempt to access the Reservation Zone.
- Result: If access is successful, the issue is confirmed to be localized browser cache/cookies. Proceed to Step 2 for a permanent fix.
Step 2: Clear Browser Cache and Cookies
To resolve the credential loading failure without relying on Incognito mode, clear the cached data for the specific platform domain.
- In your standard browser window, open your Settings (or history menu).
- Go to Privacy and Security > Clear Browsing Data.
- Select a time range of at least Last 7 Days (All Time is recommended).
- Check the boxes for Cookies and other site data and Cached images and files.
- Click Clear Data.
- Restart your browser, log back into the portal, and access the Reservation Zone.
Keywords
- Core Entities: Reservation Zone, client account, channel connection manager.
- Error Patterns: "Could not load credential", credentials failing to load, login credentials blocked.
- System Terms: Browser cache, local cookies, authentication failure, 2FA bypass, multi-window session, and session storage conflicts.