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

Connection reset by peer #8

Open
KHN190 opened this issue Apr 30, 2016 · 4 comments
Open

Connection reset by peer #8

KHN190 opened this issue Apr 30, 2016 · 4 comments

Comments

@KHN190
Copy link

KHN190 commented Apr 30, 2016

I've followed https://github.com/Yawning/obfs4 installation instructions but seemed unable to run obfuscation plugs. Problem:

# on remote machine
$ obfs4proxy -logLevel=ERROR -enableLogging=true
[ERROR]: obfs4proxy - must be run as a managed transport

Any suggestions or alternative commands?


Edit:
Now I have a local proxy listening on 1080, sending to remote machine port 23456. With a remote server listening on 0.0.0.0:23456, forwarding to local 1080.

But I have a connect reset by peer problem on local machine. Is this normal for pluggable transports (interrupted)? Or am I having problem with setup?

@KHN190
Copy link
Author

KHN190 commented Apr 30, 2016

OK. I made my way. The problem is in my tor log,

Apr 30 15:09:18.000 [warn] Could not launch managed proxy executable at '/usr/local/bin/obfsproxy' ('Permission denied').
Apr 30 15:44:03.000 [warn] Could not launch managed proxy executable at '/usr/local/bin/obfsproxy' ('Permission denied').
Apr 30 15:44:03.000 [warn] Could not launch managed proxy executable at '/usr/local/bin/obfs4proxy' ('Permission denied').
Apr 30 16:19:24.000 [warn] Could not launch managed proxy executable at '/usr/local/bin/obfsproxy' ('Permission denied').
Apr 30 16:19:24.000 [warn] Could not launch managed proxy executable at '/usr/local/bin/obfs4proxy' ('Permission denied').

So I added sudo so it looks like:

ServerTransportPlugin obfs4 exec sudo /usr/local/bin/obfs4proxy

Now it works.

@KHN190 KHN190 closed this as completed Apr 30, 2016
@KHN190 KHN190 changed the title obfs4proxy - must be run as a managed transport Connection reset by peer Apr 30, 2016
@KHN190 KHN190 reopened this Apr 30, 2016
@KHN190
Copy link
Author

KHN190 commented Apr 30, 2016

@gumblex sorry to reopen this issue. I do have a problem now.

@gumblex
Copy link
Owner

gumblex commented May 2, 2016

Sorry, but I can't understand what you are trying to do. Are you trying to use obfs4 with Tor, independently or with ptproxy?

@KHN190
Copy link
Author

KHN190 commented May 2, 2016

@gumblex I'm using with ptproxy.

Configure for client (local machine):

{
    "role": "client",
    "state": ".",
    "local": "127.0.0.1:1080",
    "server": "x.x.x.x:23456", # remote server, configured as tor bridge, and is running a ptproxy server
    "ptexec": "obfs4proxy -logLevel=ERROR -enableLogging=true", # like this
    "ptname": "obfs4",
    "ptargs": "cert=.....;iat-mode=0",
    "ptserveropt": "",
    "ptproxy": ""
}

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