Authelia stop without errors

[Marc-Proux]

Hi, I'm new in authelia. I'm trying to deploy an authelia docker as an SSO on my server. But every time, the container exit without any error. In the logs, I've got some warnings but nothings that should made crash the conatiner.

My configuration.yml

theme: dark
jwt_secret: "secrets"

server: 
  host: 0.0.0.0 # do not change this! 
  port: 9091 # do not change this, this is Authelia internal port 

log: 
  level: info 
  format: text 
  file_path: /var/log/authelia/authelia.log

authentication_backend:
  password_reset:
    disable: false
  refresh_interval: 5m
  ldap:
    implementation: custom
    url: ldap://openldap:389
    timeout: 5s
    start_tls: false
    base_dn: DC=arcadia-hub,DC=com
    username_attribute: uid
    additional_users_dn: ou=users
    users_filter: (&({username_attribute}={input})(objectClass=person))
    additional_groups_dn: ou=groups
    groups_filter: (&(member={dn})(objectClass=groupOfNames))
    group_name_attribute: cn
    mail_attribute: mail
    display_name_attribute: displayName
    user: CN=admin,DC=arcadia-hub,DC=com
    password: "password"

session: 
  secret: 'insecure_session_secret' 
  name: 'authelia_session' 
  inactivity: '5m' 
  expiration: '1h' 
  remember_me: '1M' 
  cookies: 
    - domain: 'arcadia-hub.com' 
      authelia_url: 'https://auth.arcadia-hub.com' 
      default_redirection_url: 'https://www.arcadia-hub.com' 
      name: 'authelia_session' 
      inactivity: '5m' 
      expiration: '1h' 
      remember_me: '1d'

regulation: 
  max_retries: 5 
  find_time: 10m
  ban_time: 12h

storage: 
  encryption_key: "sql_secrets_key"
  local: 
    path: /config/db.sqlite

notifier: 
  filesystem: 
    filename: /config/notification.txt

access_control:
  default_policy: deny
  rules:
    ## bypass rule
    - domain: 
        - "auth.arcadia-hub.com"
      policy: bypass
    - domain:
        - "traefik.arcadia-hub.com"
      subject: 
        - "group:admins"
        - "group:dev"
      policy: one_factor

My docker-compose.yml

services:
  authelia:
    image: authelia/authelia
    container_name: authelia
    volumes:
      - /app/authelia/config:/config
      - /app/authelia/config/configuration.yml:/config/configuration.yml
      - /app/authelia/log:/var/log/authelia
    networks:
      - arcadia_network
    ports:
      - "9091:9091"

networks:
  arcadia_network:
    name: arcadia_network
    driver: bridge

And the log :

time="2024-04-15T08:24:53Z" level=debug msg="Loaded Configuration Sources" files="[/config/configuration.yml]" filters="[]"
time="2024-04-15T08:24:53Z" level=debug msg="Logging Initialized" fields.level=debug file=/var/log/authelia/authelia.log format=text keep_stdout=false
time="2024-04-15T08:24:53Z" level=debug msg="Process user information" gid=0 gids="1,2,3,4,6,10,11,20,26,27" name=root uid=0 username=root
time="2024-04-15T08:24:53Z" level=warning msg="Configuration: configuration key 'authentication_backend.ldap.display_name_attribute' is deprecated in 4.38.0 and has been replaced by 'authentication_backend.ldap.attributes.display_name': you are not required to make any changes as this has been automatically mapped for you, but to stop this warning being logged you will need to adjust your configuration, and this configuration key and auto-mapping is likely to be removed in 5.0.0"
time="2024-04-15T08:24:53Z" level=warning msg="Configuration: configuration key 'session.remember_me_duration' is deprecated in 4.38.0 and has been replaced by 'session.remember_me': this has not been automatically mapped for you because the replacement key also exists and you will need to adjust your configuration to remove this message"
time="2024-04-15T08:24:53Z" level=warning msg="Configuration: configuration key 'authentication_backend.ldap.url' is deprecated in 4.38.0 and has been replaced by 'authentication_backend.ldap.address': you are not required to make any changes as this has been automatically mapped for you, but to stop this warning being logged you will need to adjust your configuration, and this configuration key and auto-mapping is likely to be removed in 5.0.0"
time="2024-04-15T08:24:53Z" level=warning msg="Configuration: configuration key 'jwt_secret' is deprecated in 4.38.0 and has been replaced by 'identity_validation.reset_password.jwt_secret': you are not required to make any changes as this has been automatically mapped for you, but to stop this warning being logged you will need to adjust your configuration, and this configuration key and auto-mapping is likely to be removed in 5.0.0"
time="2024-04-15T08:24:53Z" level=warning msg="Configuration: configuration key 'authentication_backend.ldap.mail_attribute' is deprecated in 4.38.0 and has been replaced by 'authentication_backend.ldap.attributes.mail': you are not required to make any changes as this has been automatically mapped for you, but to stop this warning being logged you will need to adjust your configuration, and this configuration key and auto-mapping is likely to be removed in 5.0.0"
time="2024-04-15T08:24:53Z" level=warning msg="Configuration: configuration key 'authentication_backend.ldap.group_name_attribute' is deprecated in 4.38.0 and has been replaced by 'authentication_backend.ldap.attributes.group_name': you are not required to make any changes as this has been automatically mapped for you, but to stop this warning being logged you will need to adjust your configuration, and this configuration key and auto-mapping is likely to be removed in 5.0.0"
time="2024-04-15T08:24:53Z" level=warning msg="Configuration: configuration key 'authentication_backend.ldap.username_attribute' is deprecated in 4.38.0 and has been replaced by 'authentication_backend.ldap.attributes.username': you are not required to make any changes as this has been automatically mapped for you, but to stop this warning being logged you will need to adjust your configuration, and this configuration key and auto-mapping is likely to be removed in 5.0.0"
time="2024-04-15T08:24:53Z" level=warning msg="Configuration: configuration keys 'server.host', 'server.port', and 'server.path' are deprecated in 4.38.0 and has been replaced by 'server.address' in the format of '[tcp[(4|6)]://]<hostname>[:<port>][/<path>]' or 'tcp[(4|6)://][hostname]:<port>[/<path>]': you are not required to make any changes as this has been automatically mapped for you to the value 'tcp://0.0.0.0:9091/', but to stop this warning being logged you will need to adjust your configuration, and this configuration key and auto-mapping is likely to be removed in 5.0.0"
time="2024-04-15T08:24:53Z" level=info msg="Authelia v4.38.8 is starting"
time="2024-04-15T08:24:53Z" level=info msg="Log severity set to debug"

If someone have some idea why the container keep stopping

[glime-ai[bot]]

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 logs you provided, it appears that your Authelia container is not crashing but is instead exiting normally after starting up. The logs do not show any errors that would cause a crash. However, there are several warnings about deprecated configuration keys, which suggest that your configuration file might be outdated or not fully compatible with the version of Authelia you are using (v4.38.8).

Here are a few steps you can take to troubleshoot and potentially resolve the issue:

1. Update Configuration File: Ensure that your configuration.yml file uses the latest configuration keys as per the Authelia documentation. For example, replace deprecated keys like jwt_secret, authentication_backend.ldap.url, and others with their updated counterparts. This might not solve the exiting issue but will help avoid future problems and eliminate the warnings.

2. Check Docker Compose Settings: Verify that your docker-compose.yml file is correctly set up to keep the container running. Although it looks correct in your description, double-check for any typos or misconfigurations.

3. Examine Exit Reasons: Since the logs do not indicate a crash, add the following environment variable to your Docker Compose service to potentially catch more detailed logs or errors:

   environment:
     - LOG_LEVEL=debug

   This will ensure that all debug logs are captured.

4. Persistent Storage Issues: Ensure that the mounted volumes (/app/authelia/config and /app/authelia/log) have the correct permissions and that Authelia can write to these directories. Incorrect permissions can sometimes cause the application to fail silently.

5. Docker Logs: After making the above changes, if the issue persists, check the Docker container logs immediately after the container stops with the command:

   docker logs authelia

   This might provide more insights into why the container is stopping.

6. Resource Constraints: Check if there are any resource constraints on your Docker host that might be causing the container to stop. For example, low memory or CPU availability can sometimes cause issues.

If after following these steps the issue still persists, consider reaching out to the Authelia community or support with detailed logs and configuration for further assistance.

This comment was generated by Glime.

[james-d-elliott]

Where did you obtain these logs from, have you checked the log file you specified? When does it exit? Does any other process perform a kill on authelia? How are you deploying it?

[Marc-Proux]

I've obtain the log with the command docker container logs authelia
The container is created but exit about 2 second after it start
No I've checked there nothing else that kill authelia. My server is a fresh install of ubuntu 22.04 with only docker and openldap

[james-d-elliott]

Check the log file you configured (or set keep_stdout to true).

[Marc-Proux]

time="2024-04-15T07:03:14Z" level=fatal msg="One or more providers had fatal failures performing startup checks, for more detail check the error level logs" providers="[user]"
 stack="github.com/authelia/authelia/v4/internal/commands/root.go:150 doStartupChecks\ngithub.com/authelia/authelia/v4/internal/commands/root.go:88
 (*CmdCtx).RootRunE\ngithub.com/spf13/cobra@v1.8.0/command.go:983                  (*Command).execute\ngithub.com/spf13/cobra@v1.8.0/command.go:1115
                 (*Command).ExecuteC\ngithub.com/spf13/cobra@v1.8.0/command.go:1039                 (*Command).Execute\ngithub.com/authelia/authelia/v4/cmd/authelia/main.go:10
       main\nruntime/internal/atomic/types.go:194                          (*Uint32).Load\nruntime/asm_amd64.s:1695                                      goexit"

It's seems that the error is with the ldap access. I will manage to solve it. Thanks for the help !

[james-d-elliott]

No worries!