Docker update v13 database access deny

Seafile Server
,
1

Since upgrade to server 13 i got error with mysql

seafile-mysql | 2026-01-09 20:44:51 359 [Warning] Access denied for user ‘seafile’@‘172.20.1.6’ (using password: NO)
seafile-mysql | 2026-01-09 20:44:51 360 [Warning] Access denied for user ‘root’@‘172.20.1.6’ (using password: NO)

The password is set in the env and on 12 it works fine since i switch to 13 i got this error ans sehub and seafile doenst start

2

There are some database configuration changes in v13.0 : Upgrade Seafile Docker - Seafile Admin Manual

I suggest you remove old configurations in seafile.conf and make sure the configuration in .env file are correct.

3

Hi @daniel.pan ,

i backuped ans removed the old config ans modified it like in the docs, but i still get the access denied error

4

You are encountering a “database access denied” error with the message “using password: NO” after upgrading Seafile Docker to version 13.

This strongly suggests that the Seafile container is attempting to connect to MySQL without providing any password, even though it’s purportedly set in the .env file. This is a critical authentication failure.

Here are some points to check to help resolve this issue:

  1. Verify Environment Variable Propagation Inside the Container:
  • The primary suspect is that the SEAFILE_MYSQL_DB_PASSWORD from your .env file is not being correctly passed into the Seafile container, or the Seafile application within the container is failing to read it.
  • You should access the running Seafile container (e.g., docker exec -it <container_id> bash) and use env | grep SEAFILE_MYSQL_DB_PASSWORD (or env | grep DB_PASSWORD) to confirm if the variable exists and holds the correct password. If it’s missing or incorrect, the problem lies in how the .env file is loaded or how variables are passed to the container.
  1. Review the yml files:
  • Ensure your the yml files are correctly configured to use the .env file or explicitly passes the database environment variables to the Seafile service. Look for environment: sections within your seafile or seahub services and ensure they reference your .env variables correctly (e.g., SEAFILE_MYSQL_DB_PASSWORD: ${SEAFILE_MYSQL_DB_PASSWORD}).
  1. Examine Seafile Configuration Files (seafile.conf``, ``seahub_settings.py``) within the Container:
  • Check the database configuration in seafile.conf and seahub_settings.py inside the running Seafile container. Ensure they are removed.
5

Hi @daniel.pan

i passed the .env in the seafile-server.yml und samoe on notification…yml and now it works again.

i didn’t have an docker-comnpose file anymore only your provided yml file and the .env

6

Glad to see the problem has been solved.

This is my mistake. I have corrected the above reply.