Closed keytouch closed 8 years ago
You need to post the detailed configuration.
uh, configuration on the client?
Right.
I can't give you the screenshot as I'm using cellphone. configurations are like this: basic address and port num, with aes-256-cfb encryption. No ota.
And other configuration?
uh, normally, I will turn on ipv6, but not this time for the issue. And the rest below such as udp,kcp are off because of it.
As I mentioned above, you need to post all the configurations, including specific numbers, settings, etc.
remote port is above 20000, i don't want to give it out so clearly, local port:1080(default)
with 3.1.0 and the same settings, it works.
What is your config in detail (with all sensitive info masked)?
Btw have you read FAQ before posting this issue?
I'm now using web-based page to post this issue, sorry for that
If so, I cannot reproduce your issue with your provided configurations. I tried exactly the same config on my side, everything works well.
If you're using shadowsocks-libev as the server, make sure the DNS config is correct.
let me test again. Because I knew that,miui is a little different.
It didn't work, still showing"ssl handshake timed out" Is there any other way to feed you the screenshot?
You don't need to post screenshots, but post every detailed config of your client (without hostname and password).
Also, what's your server version? Could you also post your server's log here?
I use breakwa11's ssr-python, and I ensure that there is nothing wrong with my server configuration. There exist two reasons,
For the configuration, just A minute.
name: omitted hostname: remote port: 20020 local port: 1080 passwd:
slip of hand just now. I will feed the configuration to u immediately
encyption: aes-256-cfb ota: no strategy(?I can't tell that exactly): go through ss except lan addresses and mainland addresses. ipv6: on(it's also on on the server) udp: off kcp: off
shadowsocks-android only works with the server of original protocol. If you're connecting to a "compatible" server like ssr, no guarantee here.
The known working servers supporting your config include:
github.com/shadowsocks/shadowsocks github.com/shadowsocks/shadowsocks-go github.com/shadowsocks/shadowsocks-libev
I suggest you switch to the above servers and try again.
Btw have you tried resetting, etc?
yep
I have tried original ss, I tried xxx''s free one.
I cleaned the app data for several times.
reseting ,also
Tip: You can edit your previous post.
If so, could you post logcat and/or the log on your server as well?
2016-09-14 14:11:06 ERROR tcprelay.py:825 [Errno 104] Connection reset by peer 2016-09-14 14:11:06 ERROR tcprelay.py:826 exception from ::ffff:101.90.126.170:54708 2016-09-14 14:13:15 ERROR tcprelay.py:825 [Errno 110] Connection timed out 2016-09-14 14:13:15 ERROR tcprelay.py:826 exception from ::ffff:101.90.126.170:54713 2016-09-14 14:13:20 ERROR tcprelay.py:825 [Errno 110] Connection timed out 2016-09-14 14:13:20 ERROR tcprelay.py:826 exception from ::ffff:101.90.126.170:54718 2016-09-14 14:13:25 ERROR tcprelay.py:825 [Errno 110] Connection timed out 2016-09-14 14:13:25 ERROR tcprelay.py:826 exception from ::ffff:101.90.126.170:54724 2016-09-14 14:13:31 ERROR tcprelay.py:825 [Errno 110] Connection timed out 2016-09-14 14:13:31 ERROR tcprelay.py:826 exception from ::ffff:101.90.126.170:54726
this is the stderr, for I used supervisor
stdout is empty. (just A little confused, maybe the info are treated as stderr,)(of course it's unnecessary to the issue.)
these errors seem not to be abnormal.
above these are the initiating info, so omitted.
Please try this server https://github.com/shadowsocks/shadowsocks/archive/master.zip and post all the logs from the command line.
ok, hold on
The command line for this server is:
python shadowsocks/server.py -s 0.0.0.0 -p 20020 -k test -m aes-256-cfb
From other users' feedbacks, 3.1.4 works well on Xiaomi Mi 5 with Android 6.0 (MIUI 8).
ok, it works. I will turn to the ssr side. thanks. And sorry for disturbing you.
Please answer these questions before submitting your issue. Thanks!
What version of Shadowsocks are you using?
3.1.4
What Android OS version and device are you using?
6.0.1(miui8)
What did you do?
normal usage
What did you expect to see?
use smoothly
What did you see instead?
ssl handshake timed out
What is your config in detail (with all sensitive info masked)?
normal settings, for testing this, i turn off some sections like kcp which may cause trouble. And with the same configuration, i connected smoothly on the ssr-android or an earlier ss-android client with original protocol. I believe that there is something to do with the new ss-android version.