Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tor Error (Connection refused) #248

Closed
star-buck opened this issue Jan 28, 2016 · 2 comments
Closed

Tor Error (Connection refused) #248

star-buck opened this issue Jan 28, 2016 · 2 comments

Comments

@star-buck
Copy link

Hi,

I followed the instructions for installing zeronet and tor on debian, but still get Tor error when I start zeronet:

python zeronet.py --tor always --ui_ip 0.0.0.0

  • Starting ZeroNet...
    [14:00:58] - OpenSSL loaded, version: 01000205F
    [14:00:58] - Patching sockets to tor socks proxy: 127.0.0.1:9050
    [14:00:58] - Version: 0.3.5 r859, Python 2.7.11 (default, Jan 11 2016, 21:04:40)
    [GCC 5.3.1 20160101], Gevent: 1.0.1
    [14:00:59] - Creating FileServer....
    [14:00:59] TorManager Tor controller connect error: [Errno 111] Connection refused
    [14:00:59] - Creating UiServer....
    [14:01:00] - Removing old SSL certs...
    [14:01:00] - Starting servers....
    [14:01:00] Ui.UiServer --------------------------------------
    [14:01:00] Ui.UiServer Web interface: http://0.0.0.0:43110/
    [14:01:00] Ui.UiServer --------------------------------------
    [14:01:04] FileServer Checking port 15441 using portchecker.co...
    [14:01:04] Site:14kr6q..T2Ag Announce to 0 trackers in 0.042s, failed

Port 15441 is open, on the Stats page it says:
rev859 | False | Opened: False | Crypt: ['tls-rsa'] | In: 0.00MB, Out: 0.00MB | Peerid: -ZN0035-aegwVkCOPMiG |
Connections (0, total made: 23):
Tor hidden services (status: Error ([Errno 111] Connection refused)):

Any idea what could be the reason?

@HelloZeroNet
Copy link
Owner

Verify if your tor controll port is opened: sudo netstat -anp | grep LISTEN | grep 9051 and nc 127.0.0.1 9051

@star-buck
Copy link
Author

thanks for the quick respond, i figured out that
/etc/init.d/tor (re-)start
as mentioned in the docu here seems on my system (debian sid) to actually not get tor running, besides the message saying that it started.

Simply "tor" worked fine though. So ticket can be closed, maybe update the docs or I still doing something wrong here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants