RustDesk Self-Hosted: Client Fails to Connect Despite Open Ports

[electriquo]

Describe the bug

Relates to #643 (the discussion holds more detailed information, including screenshots and outputs)

• HBBS and HBBR Containers start correctly
• Ports are open and reachable
• Client can connect to the server socket
• However, the client never becomes "ready"
• Connections are immediately dropped by the server

Describe the environment

• Install environment: docker

services:
  hbbs:
    container_name: hbbs
    image: docker.io/rustdesk/rustdesk-server:1.1.15
    command: hbbs
    volumes:
      - ./data:/root
    depends_on:
      - hbbr
    restart: unless-stopped
    environment:
      - RUST_LOG=debug
      - ALWAYS_USE_RELAY=Y
      - RELAY-SERVERS=localhost
      - RENDEZVOUS-SERVERS=localhost
    network_mode: host

  hbbr:
    container_name: hbbr
    image: docker.io/rustdesk/rustdesk-server:1.1.15
    command: hbbr
    volumes:
      - ./data:/root
    restart: unless-stopped
    environment:
      - RUST_LOG=debug
    network_mode: host

How to Reproduce the bug

Steps to reproduce the behavior:

1. Started the Server and Relay containers (see Running the Services at RustDesk Self-Hosted: Client Fails to Connect Despite Open Ports #643)

   docker compose run --rm --service-ports --pull always hbbs

2. On another terminal, verify all required ports appear reachable locally (see Port Connectivity Test at RustDesk Self-Hosted: Client Fails to Connect Despite Open Ports #643), E.g.

   nc -v -w 1 localhost 21115

3. Configured the client manually using ID Server and Key (see Client Configuration at RustDesk Self-Hosted: Client Fails to Connect Despite Open Ports #643)

4. Client UI shows "Connecting to the RustDesk network..." then "Not ready. Please check your connection"

Additional context

Relates to #643

experiencing the similar issue, havent came across the solution yet

[electriquo]

Hi @ghost, please upvote the issue.

[radroxx]

It worked on my server at first, but after I reinstalled Linux and restarted it, the clients no longer connect to the same server, with same error.