执行报错

[chenxudong2020]

服务端报错：

[2024-01-18T14:58:44Z DEBUG overtls::server] 127.0.0.1:50816 <> 20.189.173.16:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:58:45Z DEBUG overtls::server] 127.0.0.1:50820 <> 51.105.71.136:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:58:52Z DEBUG overtls::server] 127.0.0.1:50838 <> 52.182.143.211:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:58:52Z DEBUG overtls::server] 127.0.0.1:50844 <> 52.182.143.211:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:58:54Z DEBUG overtls::server] 127.0.0.1:50848 <> 51.105.71.136:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:58:54Z DEBUG overtls::server] 127.0.0.1:50852 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:00Z DEBUG overtls::server] 127.0.0.1:50862 <> 52.182.143.211:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:01Z DEBUG overtls::server] 127.0.0.1:50866 <> 52.182.143.211:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:07Z DEBUG overtls::server] 127.0.0.1:50878 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:08Z DEBUG overtls::server] 127.0.0.1:50884 <> 52.182.143.211:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:14Z DEBUG overtls::server] 127.0.0.1:50892 <> 52.182.143.211:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:14Z DEBUG overtls::server] 127.0.0.1:50896 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:20Z DEBUG overtls::server] 127.0.0.1:50908 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:20Z DEBUG overtls::server] 127.0.0.1:50912 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:27Z DEBUG overtls::server] 127.0.0.1:50932 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:28Z DEBUG overtls::server] 127.0.0.1:50936 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:33Z DEBUG overtls::server] 127.0.0.1:50942 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:34Z DEBUG overtls::server] 127.0.0.1:50946 <> 20.42.73.28:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:41Z DEBUG overtls::server] 127.0.0.1:50960 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:42Z DEBUG overtls::server] 127.0.0.1:50964 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:47Z DEBUG overtls::server] 127.0.0.1:50978 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:48Z DEBUG overtls::server] 127.0.0.1:50982 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:54Z DEBUG overtls::server] 127.0.0.1:50988 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T14:59:54Z DEBUG overtls::server] 127.0.0.1:50992 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T15:00:00Z DEBUG overtls::server] 127.0.0.1:51002 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T15:00:00Z DEBUG overtls::server] 127.0.0.1:51006 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T15:00:07Z DEBUG overtls::server] 127.0.0.1:51016 <> 20.42.73.28:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T15:00:07Z DEBUG overtls::server] 127.0.0.1:51022 <> 20.189.173.23:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T15:00:14Z DEBUG overtls::server] 127.0.0.1:51040 <> 20.42.73.28:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T15:00:14Z DEBUG overtls::server] 127.0.0.1:51032 <> 34.107.221.82:80 connection closed error: tungstenite::error::Error WebSocket protocol error: Connection reset without closing handshake
[2024-01-18T15:00:14Z DEBUG overtls::server] 127.0.0.1:51032: tungstenite::error::Error WebSocket protocol error: Connection reset without closing handshake
[2024-01-18T15:00:14Z DEBUG overtls::server] 127.0.0.1:51044 <> 51.105.71.136:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T15:00:16Z DEBUG overtls::server] 127.0.0.1:51058 <> 51.105.71.136:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T15:00:17Z DEBUG overtls::server] 127.0.0.1:51064 <> 20.42.73.28:443 outgoing connection closed "Connection reset by peer (os error 104)"
[2024-01-18T15:00:19Z DEBUG overtls::server] 127.0.0.1:51048 <> 34.107.221.82:80 connection closed error: tungstenite::error::Error WebSocket protocol error: Connection reset without closing handshake
[2024-01-18T15:00:19Z DEBUG overtls::server] 127.0.0.1:51048: tungstenite::error::Error WebSocket protocol error: Connection reset without closing handshake

config的配置：

root@16c2f4b154fc:/default# cat config.json

{
  "remarks": "nickname of this config",
  "method": "none",
  "password": "password",
  "tunnel_path": "/secret-tunnel-path123/",
  "server_settings": {
    "disable_tls": false,
    "manage_clients": {
      "enabled": false,
      "node_id": 1,
      "api_update_time": 60,
      "webapi_url": "https://sspanelhost.com:443/",
      "webapi_token": "secret-token"
    },
    "forward_addr": "http://127.0.0.1:80",
    "listen_host": "0.0.0.0",
    "listen_port": 10000
  },

  "client_settings": {
    "disable_tls": false,
    "client_id": "33959370-71e0-401d-9746-cda471fc5926",
    "server_host": "123.45.67.89",
    "server_port": 443,
    "server_domain": "example.com",
    "cafile": "",
    "listen_user": "",
    "listen_password": "",
    "listen_host": "127.0.0.1",
    "listen_port": 1080
  }
}

nginx配置文件
root@16c2f4b154fc:/etc/nginx/conf.d# cat overtls.conf

  server {
        listen 80 default_server;
        listen [::]:80 default_server;
        server_name 域名已经隐藏;
        index index.php index.html index.htm index.nginx-debian.html;
        root  /web;
    }
     server {
        listen 443 ssl default_server;
        listen [::]:443 ssl default_server;
        ssl_certificate       /cert/fullchain.pem;
        ssl_certificate_key   /cert/privkey.pem;
        ssl_protocols         TLSv1 TLSv1.1 TLSv1.2;
        ssl_ciphers           HIGH:!aNULL:!MD5;
        server_name           域名已经隐藏;
        index index.php index.html index.htm index.nginx-debian.html;
        root  /web;
        error_page 400 = /400.html;

        location ~ \.php$ {
            
        }

        location /secret-tunnel-path123/ {
            proxy_redirect off;
            proxy_pass http://127.0.0.1:10000;
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
            proxy_set_header Host $http_host;
        }
    }

网页 https://我的域名 一切正常

[ssrlive]

妨礙翻牆嗎？如果不妨礙，就是正常的。

[chenxudong2020]

不行的，我用SSR win全局代理，浏览器打不开百度 如果用over tls当默认https服务器在443端口时候可以打开 非443则打不开 所以我就全部切到nginx 测试nginx默认端口443 

[ssrlive]

從輸出日誌看，是目標服務器強行切斷了連接，這似乎不是 overtls 的責任，它都把數據送達目標了。

如果實在搞不定，就格了這個機子，重裝系統，重裝 overtls 看看。

[chenxudong2020]

这就奇怪了 反正我用over tls当https服务器 不用443就是不行 换了nginx用443也是不行  配置文件是抄你的安装脚本的

[ssrlive]

那似乎是 你機子的 防火牆設定的問題，只開放了 80 和 443 端口。

[chenxudong2020]

全部开放的 我检查过了

…

---原始邮件--- 发件人: ***@***.***> 发送时间: 2024年1月19日(周五) 中午12:29 收件人: ***@***.***>; 抄送: ***@***.******@***.***>; 主题: Re: [ShadowsocksR-Live/overtls] 执行报错 (Issue #41) 那似乎是 你機子的 防火牆設定的問題，只開放了 80 和 443 端口。 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[ssrlive]

實在找不出啥問題了，只能懷疑到這個上面了。

overtls/install/overtls-install.sh

Lines 456 to 457 in 164216d

         ssl_certificate       ${site_cert_dir}/chained_cert.pem; 
         ssl_certificate_key   ${site_cert_dir}/private_key.pem; 

現在的 證書生成的腳本，只使用這個證書文件和 私鈅 文件。

[chenxudong2020]

實在找不出啥問題了，只能懷疑到這個上面了。

overtls/install/overtls-install.sh

Lines 456 to 457 in 164216d

         ssl_certificate       ${site_cert_dir}/chained_cert.pem; 
         ssl_certificate_key   ${site_cert_dir}/private_key.pem; 

我把腾讯云服务的发给你 你xhell检查下吧

[ssrlive]

不了，國內的機子會出賣我的IP的。

[chenxudong2020]

能解释下全部参数吗

{
    "remarks": "nickname of this config",
    "method": "none",
    "password": "password",
    "tunnel_path": "/secret-tunnel-path123/",
    "server_settings": {
        "disable_tls": false,
        "manage_clients": {
            "enabled": false,
            "node_id": 1,
            "api_update_time": 60,
            "webapi_url": "https://sspanelhost.com:443/",
            "webapi_token": "secret-token"
        },
        "certfile": "/web/fullchain.pem",
        "keyfile": "/web/privkey.pem",
        "forward_addr": "http://127.0.0.1:80",
        "listen_host": "0.0.0.0",
        "listen_port": 443
    },
    "client_settings": {
        "disable_tls": false,
        "client_id": "33959370-71e0-401d-9746-cda471fc5926",
        "server_host": "123.45.67.89",
        "server_port": 443,
        "server_domain": "example.com",
        "cafile": "",
        "listen_user": "",
        "listen_password": "",
        "listen_host": "127.0.0.1",
        "listen_port": 1080
    }
}

[chenxudong2020]

method 参数是做啥用的

[ssrlive]

method 和 password 是爲兼容 ss 保留的，但現在看來意義不大。因爲 tls 已經強加密數據了，沒必要再加密一遍。

manage_clients 字段是爲 機場準備的，方便機場管理 overtls 的各個服務端。

[chenxudong2020]

刚测试了ssrwin客户端 method选了 把这个设置none 就可以了

[ssrlive]

...