Connection impossible about authelia

[glime-ai]

Please note this response was created using generative AI leveraging previously available information from the repository. This information may be helpful however it is our strong recommendation that you carefully consider the information before blindly applying it.

---

Based on the information provided, it seems like you are encountering an issue with Authelia where you are unable to log in, receiving a "username/password incorrect" message despite the logs not providing further insight into the issue. Given the detailed configuration and logs you've shared, there are a few potential areas to investigate:

1. User Configuration and Password Hash: Ensure that the password hash in your user configuration matches the password you are attempting to use. The hash provided in your configuration corresponds to the password 'authelia' for the user 'authelia'. If you've changed the password but not updated the hash accordingly, this could be the cause of the issue.

2. Database Connection: Since you mentioned the issue persists whether using file-based or SQL (MariaDB) storage for user passwords, ensure that Authelia can successfully connect to your MariaDB database. Any issues with database connectivity could prevent Authelia from verifying user credentials properly.

3. Network Configuration: Your Docker Compose configuration shows multiple networks. Ensure that Authelia is able to communicate over the network with any other services it needs to interact with, such as your database or the reverse proxy.

4. Reverse Proxy Configuration: Ensure that your SWAG reverse proxy is correctly configured to forward requests to Authelia and that there are no misconfigurations that could be causing issues with the authentication flow.

5. Authelia Version: You mentioned upgrading to Authelia version 4.38.6. Ensure that there are no known issues with this version related to authentication. You can check the Authelia GitHub issues page for any reports that might match your situation.

6. Session Cookie Configuration: The error log from Authelia mentioning "Target URL does not appear to have a relevant session cookies configuration" suggests there might be an issue with how session cookies are configured or handled. Ensure that your Authelia configuration correctly specifies the domain for session cookies, and it matches the domain you are accessing Authelia from.

Given the complexity of the issue and the number of components involved, it might also be helpful to enable more verbose logging for Authelia and review the logs for any additional clues as to what might be going wrong.

If after checking these areas the issue persists, consider reaching out to the Authelia community for further assistance, providing them with the details and findings from your investigation.

This comment was generated by Glime.

[james-d-elliott]

Can't do anything without the full configuration sorry.

[Nicolas-mahe]

there is it this
configuration-an.zip

[james-d-elliott]

Ah, see the required headers. The redaction made it a bit unclear but your proxy doesn't appear to be setting them.Since this is not a bug I will close this, but let me know if you want me to convert it to a discussion for support.

[Nicolas-mahe]

Yes please I need support on this subject :)