Rustdesk with custom port

Default port docker compose file

  services:
    hbbs:
      image: rustdesk/rustdesk-server:latest
      container_name: hbbs
      restart: unless-stopped
      environment:
        - RUST_LOG=info
        # Default ports, no need to override HBBS_PORT/HBBR_PORT
      command: hbbs
      ports:
        - "21115:21115"         # TCP ID/Signaling
        - "21116:21116/udp"     # UDP NAT traversal
        - "21117:21117"         # TCP relay coordination
      volumes:
        - ./data:/root/.config/rustdesk
  
    hbbr:
      image: rustdesk/rustdesk-server:latest
      container_name: hbbr
      restart: unless-stopped
      environment:
        - RUST_LOG=info
        # Default HBBR_PORT=21118 automatically
      command: hbbr
      ports:
        - "21118:21118"         # TCP relay
        - "21118:21118/udp"     # UDP relay
      volumes:
        - ./data:/root/.config/rustdesk

this works perfectly

but if I set custom port the client not connecting to the server below is my code

    services:
      hbbs:
        image: rustdesk/rustdesk-server:latest
        container_name: hbbs
        restart: unless-stopped
        command: hbbs
        ports:
          - "8188:21115"         # TCP for ID/Signaling
          - "8187:21116"         # TCP for ID registration and heartbeat
          - "8187:21116/udp"     # UDP for ID registration and heartbeat
          - "8189:21118"         # TCP for web client support
        volumes:
          - ./data:/root/.config/rustdesk
    
      hbbr:
        image: rustdesk/rustdesk-server:latest
        container_name: hbbr
        restart: unless-stopped
        command: hbbr
        ports:
          - "8190:21117"         # TCP relay
          - "8191:21119"         # TCP relay for web client
        volumes:
          - ./data:/root/.config/rustdesk

what I did wrong ?

No source files or tests are named. Start by comparing the default and custom Docker Compose port mappings, then inspect the RustDesk server container logs and client endpoint configuration. Done means the custom-port deployment accepts client connections and the mapped services are reachable.