The "deadline has elapsed" error occurs for the connection after KEY is forcibly specified.

I'm new here and my English isn't very good. I can only describe my deployment process completely

Server system：CentOS7.6-Docker24
RustDesk Version：1.1.10-3

Approach:：Docker deployment
Reproduce the process：
1、docker installation
curl -fsSL https://get.docker.com/ | bash -s docker --mirror Aliyun
yum install docker-compose-plugin
systemctl start docker
systemctl enable docker
2、Create configuration file
mkdir -p /root/rustdesk
touch /root/rustdesk/docker-compose.yml（Add the official configuration here）
3、Execute the download image and start docker container
cd /root/rustdesk
docker compose up -d
4, test whether the normal connection: the connection is normal.
5、Configuration file hbbs and hbbr add -k _ parameter behind
6, reload the container:
cd /root/rustdesk/
docker compose pull
docker compose up -d
7、View the public key
8,、Execute reboot
9、test whether the normal connection: connection error, ["deadline has elapsed"]. There is always a connection in progress, triggering ["deadline has elapsed"] every 15 seconds or so (triggering 0.5 seconds)

Start with the official configuration in docker-compose.yml and compare the hbbs and hbbr settings before and after adding the -k _ parameter. Reproduce the restart and inspect the resulting connection behavior and logs around the repeated "deadline has elapsed" errors; done means the server accepts connections normally with the key setting enabled.