rustdesk / rustdesk/rustdesk-server
Unable to establish encrypted transmission
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10.4k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
`
version: '3.6'
services:
rustdesk-server:
container_name: rustdesk-server
ports:
- 23565:21115
- 23566:21116
- 23566:21116/udp
- 23567:21117
- 23568:21118
- 23569:21119
image: rustdesk/rustdesk-server-s6:latest
environment:
- "RELAY=x.x.x.x:23567"
- "ENCRYPTED_ONLY=1"
- "DB_URL=/db/db_v2.sqlite3"
volumes:
- ./db:/db
restart: unless-stopped
secrets:
- key_pub
- key_priv
secrets:
key_pub:
file: /root/rustdesk/secrets/pub
key_priv:
file: /root/rustdesk/secrets/priv
`
Unable to establish encrypted transmission.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the supplied Docker Compose configuration, especially ENCRYPTED_ONLY=1, RELAY, and the key_pub/key_priv secrets used by rustdesk/rustdesk-server-s6:latest. Reproduce the encrypted-transmission failure and verify the configuration or server behavior that allows encrypted transmission to establish successfully; no test file is mentioned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, rust
- Domain
- backend, networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100