561 Unauthorized
The 561 HTTP response status code means there was an authentication failure.
You can Check Your URLs HTTP Code for FREE
Introduction
In Action
Sample
Conclusion
Introduction
Usage specific to AWS Elastic Load Balancer
When the HTTP response status code 561 Unauthorized is received from an AWS Elastic Load Balancer, it means there was an authentication failure. The client’s request lacked valid authentication credentials, and access to the requested resource was denied.
Usage specific to Pantheon
For Pantheon, the HTTP status code 561 No site detected indicates that there is a problem with the site. It suggests that the site being accessed does not exist or cannot be detected on the Pantheon platform. In this case, users may need to verify the correct site URL or contact Pantheon support for assistance.
In Action
Usage specific to AWS Elastic Load Balancer:
The 561 Unauthorized status code occurs when the AWS Elastic Load Balancer is set up to authenticate users, but there was an error during the authentication process. This may be due to an issue with the identity provider (IdP) that handles user authentication.
Usage specific to Pantheon:
The 561 No site detected status code is encountered when a site has been created on the Pantheon platform, but a content management system (CMS) has not been installed on it.
Alternatively, it may also appear instead of the Pantheon HTTP error 403 Forbidden (Directory Listing Denied) if there is no index file present on the site. To resolve this, users should ensure that a CMS is installed and the necessary files are in place for the site to function properly.
Conclusion
The 561 HTTP status code is an unofficial server error used in specific cases for AWS Elastic Load Balancer and Pantheon. For AWS Elastic Load Balancer, it indicates an authentication failure during the process of verifying user identities.
For Pantheon, it suggests that a site has been created but lacks a content management system (CMS) or an index file, leading to a site-related problem. Users encountering this code should check their authentication settings or ensure that the necessary components are properly configured for their site to function as expected.
