Although I have specified the MySQL port in the environment variables, I still observe in the logs that it tries to access the MySQL server through the default MySQL port.
ENV
SEAFILE_MYSQL_DB_PORT=13306
DB_PORT=13306
notification-server.log
[2025-03-14 04:39:16] [ERROR] Failed to connected to mysql: dial tcp 172.22.1.181:3306: connect: connection timed out
During the Docker image of the notification server being updated, I believe the issue persists. What I mean to say is that if the server supports custom database ports, then components which sharing the same environment variable file should also support it, as it is only reasonable.
We don’t have plan to support custom MySQL port for notification server yet.