TimeToogo / TimeToogo/tunshell
Cannot establish connection
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 818
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
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
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
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.
Assessment
- Tech stack
- rust, shell
- Domain
- authentication, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100