HTTP troubleshooting
401 Unauthorized
Your uptime monitor detected that the server refused to load the page because it requires valid security login keys or passwords. The server did not recognize or accept the identity proof provided in the request.
What 401 Status Code Means
- 1.
Missing login details
The request tried to open a private page without sending any username, password, or security token.
- 2.
Expired security keys
The security token or API key used by the monitor has expired or is no longer valid on the server.
- 3.
Uptime monitor behavior
Our monitor flagged this page because it hit a lock screen or private wall instead of loading the public website content.
Troubleshooting checklist
- 1.
Check access permissions
Verify if the specific page or API link is supposed to be private or if it was made private by mistake.
- 2.
Review monitor headers
Look at the authorization headers or API keys you saved inside this uptime monitor setup.
- 3.
Test keys manually
Try using the exact same security token in a tool like Postman to see if the server still accepts it.
- 4.
Inspect auth logs
Check your server login logs to see if it rejected the connection due to an incorrect key format.
How to Fix It
- 1.
Add login credentials
Update this monitor's settings to include the correct username, password, or bearer token for private pages.
- 2.
Renew expired tokens
Generate a brand new API key or security token in your website dashboard and paste it into the monitor.
- 3.
Fix token formatting
Make sure words like 'Bearer' or 'Basic' are spelled correctly right before your token string inside the header.
- 4.
Make the page public
Adjust your website code or routing settings if this specific page was accidentally locked down behind a login shield.
After the Service is Fixed
- 1.
Verify with Uptime Monitor
Confirm that the monitor shows a healthy green status now that it has the correct keys to pass the security wall.
- 2.
Check token expiry dates
Set a personal reminder to renew these security keys before they expire and cause another false alarm.
- 3.
Secure your credentials
Ensure your API keys and passwords inside the monitor settings are encrypted and hidden from public view.
- 4.
Monitor auth failures
Set up a server alert to track if too many failed login attempts happen in a row, which could mean a security issue.