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

Too much errors with obfs plugin #1443

Closed
LexterS999 opened this issue Apr 12, 2017 · 26 comments
Closed

Too much errors with obfs plugin #1443

LexterS999 opened this issue Apr 12, 2017 · 26 comments

Comments

@LexterS999
Copy link

What version of shadowsocks-libev are you using?

What operating system are you using?

server Ubuntu 16.10 x86 and client win10 x64

What did you do?

Installed ss-libev with obfs plugin (tls encryption)

What did you expect to see?

Work without errors

What did you see instead?

It's always shows me this with -u argument
2017-04-12 13:50:32 INFO: plugin "obfs-server" enabled
2017-04-12 13:50:32 INFO: UDP relay enabled
2017-04-12 13:50:32 INFO: initializing ciphers... aes-256-cfb
2017-04-12 13:50:32 INFO: tcp server listening at 127.0.0.1:46719
2017-04-12 13:50:32 INFO: udp server listening at 0.0.0.0:996
2017-04-12 13:50:32 INFO: running from root user
2017-04-12 13:50:32 [simple-obfs] INFO: obfuscating enabled
2017-04-12 13:50:32 [simple-obfs] INFO: obfuscating hostname: cloudfront.net
2017-04-12 13:50:32 [simple-obfs] INFO: tcp port reuse enabled
2017-04-12 13:50:32 [simple-obfs] INFO: listening at 0.0.0.0:996
2017-04-12 13:50:32 [simple-obfs] INFO: running from root user
2017-04-12 13:50:33 [simple-obfs] ERROR: server recv: Connection reset by peer
2017-04-12 13:50:34 [simple-obfs] ERROR: server recv: Connection reset by peer

And with -U argument

2017-04-12 13:52:53 INFO: plugin "obfs-server" enabled
2017-04-12 13:52:53 INFO: UDP relay enabled
2017-04-12 13:52:53 INFO: TCP relay disabled
2017-04-12 13:52:53 INFO: initializing ciphers... aes-256-cfb
2017-04-12 13:52:53 INFO: udp server listening at 0.0.0.0:996
2017-04-12 13:52:53 INFO: running from root user
2017-04-12 13:52:53 [simple-obfs] INFO: obfuscating enabled
2017-04-12 13:52:53 [simple-obfs] INFO: obfuscating hostname: cloudfront.net
2017-04-12 13:52:53 [simple-obfs] INFO: tcp port reuse enabled
2017-04-12 13:52:53 [simple-obfs] INFO: listening at 0.0.0.0:996
2017-04-12 13:52:53 [simple-obfs] INFO: running from root user
2017-04-12 13:52:54 [simple-obfs] ERROR: getpeername: Transport endpoint is not connected

What is your config in detail (with all sensitive info masked)?

{
"server":"0.0.0.0",
"server_port":996,
"password":"***",
"method":"aes-256-cfb",
"plugin":"obfs-local",
"plugin_opts":"obfs=tls"
}

and on client side
{
"server":"",
"server_port":996,
"local_port":1080,
"password":"
",
"method":"aes-256-cfb",
"plugin":"obfs-local",
"plugin_opts":"obfs=tls;obfs-host=cloudfront.net"
}

@LexterS999
Copy link
Author

Still have the same problem after re-installation on pure Ubuntu 16.10 x86 kernel is 4.10

@madeye
Copy link

madeye commented Apr 17, 2017

Try port 443.

@LexterS999
Copy link
Author

@madeye i did everything and tried different port's too. -U and -u too. Nothing.

@madeye
Copy link

madeye commented Apr 17, 2017

When you say errors, does simple-obfs work for you? Or you are just reporting there are errors in the log?

@LexterS999
Copy link
Author

LexterS999 commented Apr 17, 2017

Yes obfs working and it's only in obfs log showing errors in real-time. Without obfs there is absent any error. But all mo config setup properly like in manual. And i'm using tls-obfs cause http-obfs doesnt work for me.

@madeye
Copy link

madeye commented Apr 17, 2017

I don't think these errors matter. You may try enlarging the timeout of your obfs plugin by adding this option: t=3600 to both your server and client.

@LexterS999
Copy link
Author

Yes i did that too. Doesnt help.

@madeye
Copy link

madeye commented Apr 17, 2017

Yes obfs working and it's only in obfs log showing errors in real-time

You may add vto your plugin opts and post the full log here.

@LexterS999
Copy link
Author

2017-04-17 15:06:14 INFO: plugin "obfs-server" enabled
2017-04-17 15:06:14 INFO: UDP relay enabled
2017-04-17 15:06:14 INFO: TCP relay disabled
2017-04-17 15:06:14 INFO: initializing ciphers... aes-256-cfb
2017-04-17 15:06:14 INFO: udp server listening at 0.0.0.0:996
2017-04-17 15:06:14 INFO: running from root user
2017-04-17 15:06:14 [simple-obfs] INFO: obfuscating enabled
2017-04-17 15:06:14 [simple-obfs] INFO: tcp port reuse enabled
2017-04-17 15:06:14 [simple-obfs] INFO: listening at 0.0.0.0:996
2017-04-17 15:06:14 [simple-obfs] INFO: running from root user
2017-04-17 15:06:15 [simple-obfs] ERROR: getpeername: Transport endpoint is not connected

@madeye
Copy link

madeye commented Apr 17, 2017

I only see one ERROR in your log, which also looks irrelevant.

@LexterS999
Copy link
Author

One error cause i'm cut other.. it's just repeating every few seconds

@madeye
Copy link

madeye commented Apr 17, 2017

it's just repeating every few seconds

If so, just ignore them. It means you're visiting some website that is not reachable by your server. To figure out what the site is, you could add -v to your command line.

@LexterS999
Copy link
Author

But it wasnt before. And this error doesnt appear without obfs-plugin. Also all sites working well and fast. No one of them is broke. I did that -v So now what to do?

@madeye
Copy link

madeye commented Apr 17, 2017

Just post you FULL log here with -v.

@LexterS999
Copy link
Author

Here is it:

2017-04-17 15:20:25 INFO: plugin "obfs-server" enabled
2017-04-17 15:20:25 INFO: UDP relay enabled
2017-04-17 15:20:25 INFO: TCP relay disabled
2017-04-17 15:20:25 INFO: initializing ciphers... aes-256-cfb
2017-04-17 15:20:25 INFO: udp server listening at 0.0.0.0:996
2017-04-17 15:20:25 INFO: running from root user
2017-04-17 15:20:25 [simple-obfs] INFO: obfuscating enabled
2017-04-17 15:20:25 [simple-obfs] INFO: tcp port reuse enabled
2017-04-17 15:20:25 [simple-obfs] INFO: listening at 0.0.0.0:996
2017-04-17 15:20:25 [simple-obfs] INFO: running from root user
2017-04-17 15:20:27 [simple-obfs] ERROR: getpeername: Transport endpoint is not connected
The same. Cut repeated [simple-obfs] ERROR: getpeername: Transport endpoint is not connected

@madeye
Copy link

madeye commented Apr 17, 2017

Obviously, you didn't add -v to your command line, as there is no "verbose" log here.

@LexterS999
Copy link
Author

Yes i did
ss-server -c /etc/shadowsocks-libev/config.json -U -v

@madeye
Copy link

madeye commented Apr 17, 2017

You should not add -U to your command line. It means you only forward UDP traffic...

@LexterS999
Copy link
Author

LexterS999 commented Apr 17, 2017

But ss-server -c /etc/shadowsocks-libev/config.json -u -v show's almost the same error. Time to time.

@LexterS999
Copy link
Author

2017-04-17 15:33:25 INFO: plugin "obfs-server" enabled
2017-04-17 15:33:25 INFO: UDP relay enabled
2017-04-17 15:33:25 INFO: initializing ciphers... aes-256-cfb
2017-04-17 15:33:25 INFO: tcp server listening at 127.0.0.1:41883
2017-04-17 15:33:25 INFO: udp server listening at 0.0.0.0:996
2017-04-17 15:33:25 INFO: running from root user
2017-04-17 15:33:25 [simple-obfs] INFO: obfuscating enabled
2017-04-17 15:33:25 [simple-obfs] INFO: tcp port reuse enabled
2017-04-17 15:33:25 [simple-obfs] INFO: listening at 0.0.0.0:996
2017-04-17 15:33:25 [simple-obfs] INFO: running from root user
2017-04-17 15:33:58 INFO: accept a connection
2017-04-17 15:33:58 INFO: connect to 31.13.93.3:443
2017-04-17 15:33:58 INFO: remote connected
2017-04-17 15:33:58 INFO: accept a connection
2017-04-17 15:33:58 INFO: connect to 64.233.166.188:443
2017-04-17 15:33:58 INFO: accept a connection
2017-04-17 15:33:58 INFO: connect to 64.233.166.188:443
2017-04-17 15:33:58 INFO: remote connected
2017-04-17 15:33:58 INFO: remote connected
2017-04-17 15:33:59 INFO: server_recv close the connection
2017-04-17 15:33:59 INFO: current remote connection: 2
2017-04-17 15:33:59 INFO: current server connection: 2
2017-04-17 15:34:01 INFO: accept a connection
2017-04-17 15:34:01 INFO: connect to 31.13.92.51:443
2017-04-17 15:34:01 INFO: remote connected
2017-04-17 15:34:01 INFO: accept a connection
2017-04-17 15:34:01 INFO: connect to 31.13.93.2:443
2017-04-17 15:34:02 INFO: remote connected
2017-04-17 15:34:02 INFO: accept a connection
2017-04-17 15:34:02 INFO: connect to 173.252.113.9:443
2017-04-17 15:34:02 INFO: remote connected
2017-04-17 15:34:06 INFO: accept a connection
2017-04-17 15:34:06 INFO: connect to 173.252.113.9:443
2017-04-17 15:34:06 INFO: remote connected
2017-04-17 15:34:07 [simple-obfs] ERROR: server recv: Connection reset by peer
2017-04-17 15:34:07 INFO: server_recv close the connection
2017-04-17 15:34:07 INFO: current remote connection: 5
2017-04-17 15:34:07 INFO: current server connection: 5
2017-04-17 15:34:50 INFO: remote_recv close the connection
2017-04-17 15:34:50 INFO: current remote connection: 4
2017-04-17 15:34:50 INFO: current server connection: 4
2017-04-17 15:35:08 INFO: server_recv close the connection
2017-04-17 15:35:08 INFO: current remote connection: 3
2017-04-17 15:35:08 INFO: current server connection: 3
2017-04-17 15:35:10 INFO: accept a connection
2017-04-17 15:35:10 INFO: connect to 64.233.166.188:5228
2017-04-17 15:35:10 INFO: remote connected
2017-04-17 15:35:10 ERROR: remote recv: Connection reset by peer
2017-04-17 15:35:10 INFO: current remote connection: 3
2017-04-17 15:35:10 INFO: current server connection: 3
2017-04-17 15:35:17 INFO: accept a connection
2017-04-17 15:35:17 INFO: connect to 66.102.1.188:5228
2017-04-17 15:35:17 INFO: remote connected

@madeye
Copy link

madeye commented Apr 17, 2017

According to your latest log, everything works well. Just ignore any "reset" in your log. They are expected.

@LexterS999
Copy link
Author

LexterS999 commented Apr 17, 2017

Just worried that something strange happened with my config setup but if it's ok... Anyway errors means that something wrong. Maybe in code? And what's better to setup if i wanna use torrent downloading? -U or -u?

@madeye
Copy link

madeye commented Apr 17, 2017

It's not a real ERROR. Actually, shadowsocks always closes connections with TCP reset, which is expected.

@LexterS999
Copy link
Author

Okay then last question: what's better to setup if i wanna use torrent downloading? -U or -u?

@madeye
Copy link

madeye commented Apr 17, 2017

Only -u.

@LexterS999
Copy link
Author

O, thanks.

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

No branches or pull requests

2 participants