Cannot establish connection
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- authentication, networking
Research direction
The report names the remote and local init.sh entry points and shows client, server, TLS, WebSocket, relay, and shell-server errors, but no source files or tests. Reproduce the connection using the shown commands, then trace the authentication and direct-connection handshake from the client and server logs. Done means the peers connect without the authentication or unexpected-close errors.
Written by the indexing model from the issue text.
Description
On the server (remote):
wget https://lets.tunshell.com/init.sh -O - 2> /dev/null | sh -s -- T XXXX XXXX eu.relay.tunshell.com
cut: the delimiter must be a single character
Try 'cut --help' for more information.
Installing client...
Connecting to relay server...
[2026-07-28T08:41:39Z ERROR tunshell_client::server::dual_stream] Failed to connect via TLS, falling back to websocket: deadline has elapsed
Waiting for peer to join...
XX.XX.XX.XX joined the session
Negotiating connection...
Attempting direct connection to XX.XX.XX.XX
[2026-07-28T08:42:38Z ERROR client] Error occurred: Unexpected response returned by server: Close
On the client (local):
curl -sSf https://lets.tunshell.com/init.sh -o ${TMPDIR:=/tmp}/tunshell.sh && sh ${TMPDIR:=/tmp}/tunshell.sh L XXXX XXXX eu.relay.tunshell.com
Client already installed...
Connecting to relay server...
Waiting for peer to join...
XX.XX.XX.XX joined the session
Negotiating connection...
Attempting direct connection to XX.XX.XX.XX
Direct connection to peer established
[2026-07-28T08:40:15Z ERROR client] Error occurred: Error while authenticating with shell server
- Dominant language
- Rust
- Stars
- 818
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from TimeToogo/tunshell
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
Pty on androidOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in TimeToogo/tunshell
Similar issues
-
contribution
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tree-sitter/tree-sitter#6005 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
maplibre/maplibre-tile-spec#1844 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rust-windowing/winit#4731 ·
Maintainers usually reply within 2 days