HelloZeroNet/ZeroNet

Tor Always Mode Sometimes Hangs

Open

#1228 opened on Dec 29, 2017

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (18,200 stars) (2,245 forks)batch import
help wanted

Description

Step 1: Please describe your environment

  • ZeroNet version: 0.6.0 rev3161
  • Operating system: Mac OS Sierra
  • Web browser: Tor Browser
  • Tor status: always
  • Opened port: no
  • Special configuration: none

Step 2: Describe the problem:

Sometimes I get this message repeatedly when I look at Tor in terminal

[warn] Socks version -125 not recognized. (Tor is not an http proxy.)

When this happens, ZeroNet begins to hang and stops updating sites. If I look at the stats page I usually see a bunch of nodes where connection status under open is n/a. Some nodes have a larger ping than normal, but eventually most nodes end up with a n/a state after a while.

Steps to reproduce:

Sometimes this happens the moment I start ZeroNet, while other times it happens after a while. It seems to happen randomly, and I've experienced this problem in earlier versions. When I try to restart ZeroNet after this happens to fix it, the same problem usually happens again.

Contributor guide

Tech stack
python
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
PythonTorZeroNet architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Investigate the Tor connection handling in ZeroNet's source code, likely in the 'Tor.py' or similar file. The SOCKS version error suggests a protocol mismatch during proxy setup. Review issue #1228 comments for any additional context. Reproduce the issue by running ZeroNet with Tor always mode and monitoring logs. Look for patterns in the SOCKS handshake to identify the root cause.