Troubles connecting to redis with secret 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 detailed description and logs you provided, it seems like the issue is related to the network connectivity between the Authelia container and the Redis container. Here are a few steps and checks you can perform to troubleshoot and potentially resolve the issue:

1. Network Configuration: Ensure that both the Authelia and Redis containers are on the same Docker network. This allows them to communicate with each other using their container names as hostnames.

2. Redis Host Configuration: In your Authelia configuration, you have specified the Redis host using an IPv4 address. Instead, try using the container name of the Redis server as the host. For example:

   redis:
     host: 'redis'  # Use the container name instead of the IP address
     port: '6379'

3. Check Redis Logs: Since the Redis logs do not show any attempt of connection from the Authelia container, it's possible that the connection attempts are not reaching the Redis container. This could be due to network misconfiguration or firewall rules.

4. Firewall and Security Groups: Check if there are any firewall rules or security groups that might be blocking the connection between the containers.

5. Redis Configuration: Ensure that the Redis container is configured to accept connections from other containers. This can typically be controlled through Redis configuration files or startup command flags.

6. Container Restart: Sometimes, simply restarting the containers can resolve transient network issues.

7. Use Docker Compose: If you are not already using Docker Compose, it might help to define your containers and their network settings in a docker-compose.yml file. This ensures that all containers are configured consistently.

8. Debugging Logs: Increase the logging level in both Authelia and Redis to get more detailed logs that might provide additional insights into the issue.

If after trying these steps the issue persists, it might be helpful to provide the configuration of your Docker network and any additional logs that might have relevant information.

This comment was generated by Glime.

[james-d-elliott]

To me this looks like a network issue (the improperly redacted IP is refusing connections on that port). Please show the output of running a separate redis CLI container on the same container network as authelia using the CLI to connect as well as the redis logs for both the authelia connection attempts and the CLI connection attempts.

[marinmo]

Yep, this was a network issue; I didn't really bother to figure out what went wrong (update from podman 4 -> 5 seems like a likely culprit but couldn't tell more closely). I put all containers into a pod and used localhost as host and it all works, seems - probably - the podman upgrade broke inter-container communication since the redis container was reachable from non-container locations as described in the bug report.

[marinmo]

Closing this as not a bug with Authelia.