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

Websocket error on armv7 device ssr-client #214

Open
shangjiaxuan opened this issue Jan 23, 2022 · 2 comments
Open

Websocket error on armv7 device ssr-client #214

shangjiaxuan opened this issue Jan 23, 2022 · 2 comments

Comments

@shangjiaxuan
Copy link

Please answer these questions before submitting your issue. Thanks!

What version of shadowsocks-native are you using?

Checked out from latest repo, updated all submodules.

What operating system are you using?

Raspberry-Pi lite+OpenMediaVault (Debian based)

What did you do?

Test ssr-client for use in LAN to bridge ssrot to normal socks5. Both LAN and local connection fail. Used the same config.json
as the working instance on my laptop.
Log message:

ssr-client 2022/01/22 10:17  info  ==== tunnel created     count   1 ====
ssr-client 2022/01/22 10:17  info  tunnel_stage_handshake -- Client App S5 handshake coming.
ssr-client 2022/01/22 10:17  info  tunnel_stage_handshake_replied -- Start waiting for request data.
ssr-client 2022/01/22 10:17  info  tunnel_stage_s5_request_from_client_app -- SOCKS5 Request data from client app.
ssr-client 2022/01/22 10:17  info  tunnel_stage_s5_response_done
ssr-client 2022/01/22 10:17  info  tunnel_stage_client_first_pkg
ssr-client 2022/01/22 10:17  info  ++++ connecting  "151.101.230.217:80" ... ++++
ssr-client 2022/01/22 10:17 error  [TLS] websocket error at "151.101.230.217:80" with status: (null)
ssr-client 2022/01/22 10:17  info  ---- disconnected  "151.101.230.217:80" ----
ssr-client 2022/01/22 10:17  info  ==== tunnel destroyed   count   0 ====

Compilation seemed to be OK, but libsodium seems to generate a lot of warnings (seems to be compiling aesni related files, which is not present in arm devices, I believe...)

What did you expect to see?

As what I have seen in using my laptop PC in windows environment. Normal connection.

What did you see instead?

The given log in ssr-client output, and failed connection.

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

{
    "password": "xxxxxxxxxxxx",
    "method": "xxxx",
    "protocol": "xxxx",
    "protocol_param": "",
    "obfs": "xxxx",
    "obfs_param": "",

    "udp": true,
    "timeout": 300,

    "server_settings": {
        "listen_address": "0.0.0.0",
        "listen_port": 36158
    },

    "client_settings": {
        "server": "xxx.xxx.xxx.xxx",
        "server_port": 443,
        "listen_address": "0.0.0.0",
        "listen_port": 3090
    },

    "over_tls_settings": {
        "enable": true,
        "server_domain": "xxxxxx",
        "path": "/xxxxxx/",
        "root_cert_file": ""
    }
}
@ssrlive
Copy link
Member

ssrlive commented Jan 23, 2022

what is your "method": "xxxx", ?

@shangjiaxuan
Copy link
Author

@ssrlive aes-256-ctr

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