conn#1: Remote failed
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
I am getting the following error when trying to run behind an nginx proxy with letsencrypt:
2019/10/30 23:48:14 client: Connecting to wss://[...]:443/chisel
2019/10/30 23:48:15 client: Handshaking...
2019/10/30 23:48:15 client: Fingerprint ee:8f[...]
2019/10/30 23:48:15 client: Sending config
2019/10/30 23:48:15 client: Connected (Latency 37.957001ms)
2019/10/30 23:48:15 client: conn#1: Remote failed (dial tcp 0.0.0.0:6002: connect: connection refused)
2019/10/30 23:48:15 client: conn#2: Remote failed (dial tcp 0.0.0.0:6002: connect: connection refused)
[...]
Any ideas why this happens?
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
No repository files, tests, or entry points are named. Start by reproducing the nginx and Let's Encrypt proxy setup, then trace why the remote connection attempts 0.0.0.0:6002 despite the WebSocket connection succeeding. Done means identifying the cause and documenting or fixing the relevant configuration or behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, nginx
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100