We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please answer these questions before submitting your issue. Thanks!
latest 0.9.3
windows 11 x64 (client) + Synology DSM (server)
trying to connect to netease music server (or any other servers) via my remote SSR server
normal conenction
ssr-client 2022/09/06 11:15 info ShadowsocksR native client ssr-client 2022/09/06 11:15 info remote server nas.************:7080 ssr-client 2022/09/06 11:15 info method aes-256-cfb ssr-client 2022/09/06 11:15 info password Zl******** ssr-client 2022/09/06 11:15 info protocol auth_sha1_v4 ssr-client 2022/09/06 11:15 info protocol_param 32 ssr-client 2022/09/06 11:15 info obfs http_simple ssr-client 2022/09/06 11:15 info udp relay no ssr-client 2022/09/06 11:15 info listening on 0.0.0.0:1080 ssr-client 2022/09/06 11:16 info ==== tunnel created count 1 ==== ssr-client 2022/09/06 11:16 info tunnel_stage_handshake -- Client App S5 handshake coming. ssr-client 2022/09/06 11:16 info socks5 handshake normal style called ssr-client 2022/09/06 11:16 info tunnel_stage_handshake_replied -- Start waiting for request data. ssr-client 2022/09/06 11:16 info tunnel_stage_s5_request_from_client_app -- SOCKS5 Request data from client app. ssr-client 2022/09/06 11:16 info tunnel_stage_s5_response_done ssr-client 2022/09/06 11:16 info tunnel_stage_client_first_pkg ssr-client 2022/09/06 11:16 info ++++ connecting "103.126.92.132:80" ... ++++ ssr-client 2022/09/06 11:16 info tunnel_stage_resolve_ssr_server_host_done -- Upstream hostname DNS lookup has completed. ssr-client 2022/09/06 11:16 error connect failed about _server_ "103.126.92.132:80": connection timed out - tunnel_stage_resolve_ssr_server_host_done -- Upstream hostname DNS lookup has completed. ssr-client 2022/09/06 11:16 info ---- disconnected "103.126.92.132:80" ---- ssr-client 2022/09/06 11:16 info ==== tunnel destroyed count 0 ====
There is an error after it successfully looked up a DNS request.
{ "password": "Zl********", "method": "aes-256-cfb", "protocol": "auth_sha1_v4", // "origin", // "protocol_param": "32", "obfs": "http_simple", // "plain", // "obfs_param": "", "udp": false, "idle_timeout": 300, "connect_timeout": 6, "udp_timeout": 6, "server_settings": { "listen_address": "0.0.0.0", "listen_port": 12475 }, "client_settings": { "server": "nas.************", "server_port": 7080, "listen_address": "0.0.0.0", "listen_port": 1080 }, "over_tls_settings": { "enable": false, "server_domain": "goodsitesample.com", "path": "/udg151df/", "root_cert_file": "" } }
The text was updated successfully, but these errors were encountered:
I hope you use SSRoT protocol instead of traditional SSR that is hacked by GFW.
Sorry, something went wrong.
No branches or pull requests
Please answer these questions before submitting your issue. Thanks!
What version of shadowsocks-native are you using?
latest 0.9.3
What operating system are you using?
windows 11 x64 (client) + Synology DSM (server)
What did you do?
trying to connect to netease music server (or any other servers) via my remote SSR server
What did you expect to see?
normal conenction
What did you see instead?
There is an error after it successfully looked up a DNS request.
What is your config in detail (with all sensitive info masked)?
The text was updated successfully, but these errors were encountered: