Skip to content

RustDesk Server: SSO/OAuth login breaks connectivity (WebSocket/secure tcp timeout) after successful installΒ #12079

@HoBeom

Description

@HoBeom

βœ… Have you read and understood the above guidelines?

yes

πŸ”Ž Did you run the script with verbose mode enabled?

No (this issue will likely be closed automatically)

πŸ“œ What is the name of the script you are using?

RustDesk Server

πŸ“‚ What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/rustdeskserver.sh)"

βš™οΈ What settings are you using?

  • Default Settings
  • Advanced Settings

πŸ–₯️ Which Linux distribution are you using?

Debian 12

πŸ“ˆ Which Proxmox version are you on?

8.4.16

πŸ“ Provide a clear and concise description of the issue.

The rustdeskserver LXC script installs successfully (hbbs/hbbr + rustdesk-api), but after enabling SSO/OAuth login via rustdesk-api and logging in from RustDesk Desktop, remote connectivity breaks.

  • Logged out: remote connections work normally.
  • After SSO/OAuth login succeeds: clients frequently become offline / rendezvous fails, with errors like:
    "Failed to secure tcp: deadline has elapsed"
    "Rendezvous server connection failed, try later"

This makes the login feature unusable even though installation completes without errors.

I suspect a WebSocket / reverse-proxy related issue triggered after login (client starts using ws endpoints), and/or a compatibility mismatch between rustdesk-api (lejianwen) and hbbs/hbbr packages installed by the script.

πŸ”„ Steps to reproduce the issue.

Step 1: Install the container using the community-scripts rustdeskserver LXC script.
Step 2: Configure RustDesk Desktop clients to use the self-hosted ID/Relay server (works normally while logged out).
Step 3: Install/enable rustdesk-api (installed by the script) and open the admin UI.
Step 4: Configure OAuth/SSO (tested with Google and GitHub) and login successfully from the RustDesk Desktop client.
Step 5: After login succeeds, try remote control: connections fail and/or clients become offline.

❌ Paste the full error output (if available).

RustDesk Desktop client errors after successful login:

  • "Failed to secure tcp: deadline has elapsed"
  • "Rendezvous server connection failed, try later"

WebSocket endpoints behind Nginx Proxy Manager (OpenResty) behave inconsistently:

  • HTTP/2 requests return 502
  • Forcing HTTP/1.1 shows WebSocket upgrade (101 Switching Protocols)

πŸ–ΌοΈ Additional context (optional).

Related upstream discussion that seems relevant:
lejianwen/rustdesk-api#396

  • Please confirm whether this is a known issue / incompatibility when combining rustdesk-api (lejianwen) with hbbs/hbbr packages installed by the script.
  • Alternatively, consider installing a compatible hbbs/hbbr build set when rustdesk-api is installed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions