xray问题排查，curl: (35) Encountered end of file（已解决）

最新推荐文章于 2024-05-18 16:30:00 发布
最新推荐文章于 2024-05-18 16:30:00 发布
阅读量717 收藏 7
点赞数 9
文章标签： java 开发语言
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/liu289747235/article/details/136771694
版权

经过了好几次排查，都没找到问题，先说问题的排查过程，多次确认了user信息，包括用户id和alterid，都没问题，头大的一逼

问题排查过程

确保本地的xray服务是正常的

[root@k8s-master01 xray]# systemctl status xray
● xray.service - Xray Service
   Loaded: loaded (/etc/systemd/system/xray.service; enabled; vendor preset: disabled)
   Active: active (running) since 六 2024-03-16 22:12:12 CST; 16min ago
 Main PID: 16207 (xray)
   CGroup: /system.slice/xray.service
           └─16207 /usr/local/xray/xray -config /usr/local/xray/config.json

3月 16 22:12:12 k8s-master01 systemd[1]: Started Xray Service.
3月 16 22:12:12 k8s-master01 xray[16207]: Xray 1.8.6 (Xray, Penetrates Everything.) Custom (go1.21.4 linux/amd64)
3月 16 22:12:12 k8s-master01 xray[16207]: A unified platform for anti-censorship.
3月 16 22:12:12 k8s-master01 xray[16207]: 2024/03/16 22:12:12 [Info] infra/conf/serial: Reading config: /usr/local/xray/config.json

从这一步看上去没问题，接着又开始第二步，通过journalctl排查

[root@k8s-master01 xray]# journalctl -f -xu xray
-- Logs begin at 一 2024-03-04 18:07:02 CST. --
3月 16 22:12:07 k8s-master01 systemd[1]: Started Xray Service.
-- Subject: Unit xray.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit xray.service has finished starting up.
-- 
-- The start-up result is done.
3月 16 22:12:07 k8s-master01 xray[16057]: Xray 1.8.6 (Xray, Penetrates Everything.) Custom (go1.21.4 linux/amd64)
3月 16 22:12:07 k8s-master01 xray[16057]: A unified platform for anti-censorship.
3月 16 22:12:07 k8s-master01 xray[16057]: 2024/03/16 22:12:07 [Info] infra/conf/serial: Reading config: /usr/local/xray/config.json
3月 16 22:12:12 k8s-master01 systemd[1]: Stopping Xray Service...
-- Subject: Unit xray.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit xray.service has begun shutting down.
3月 16 22:12:12 k8s-master01 systemd[1]: Stopped Xray Service.
-- Subject: Unit xray.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit xray.service has finished shutting down.
3月 16 22:12:12 k8s-master01 systemd[1]: Started Xray Service.
-- Subject: Unit xray.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit xray.service has finished starting up.
-- 
-- The start-up result is done.
3月 16 22:12:12 k8s-master01 xray[16207]: Xray 1.8.6 (Xray, Penetrates Everything.) Custom (go1.21.4 linux/amd64)
3月 16 22:12:12 k8s-master01 xray[16207]: A unified platform for anti-censorship.
3月 16 22:12:12 k8s-master01 xray[16207]: 2024/03/16 22:12:12 [Info] infra/conf/serial: Reading config: /usr/local/xray/config.json

也没看出什么问题，windows上测试几次都是正常的

为了保持统一，已经把windows上的config.json的内容复制粘贴到centos上了

现在开始接下来操作就是配日志（服务端和客户端都配置了）

  "log": {
    "access": "/var/log/xray/access.log",
    "error": "/var/log/xray/error.log",
    "loglevel": "debug"
  },

然后通过tail命令查看

服务端日志是这个

2024/03/16 14:10:09 [Info] [4164381125] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:11:01 [Info] [634757384] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:14:01 [Info] [1120841913] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:14:57 [Info] [1537117142] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:14:57 [Info] [549166064] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:15:05 [Info] [1278316473] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:15:15 [Info] [1619787935] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:16:07 [Info] [336587068] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:19:14 [Info] [3178032418] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:20:02 [Info] [1422900044] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:20:19 [Info] [2559318044] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:20:22 [Info] [1461925477] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:21:16 [Info] [850676330] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist

 客户端日志是这个

3月 04 18:16:00 k8s-master01 xray[1346]: 2024/03/04 18:16:00 [Warning] [2403275693] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:16:02 k8s-master01 xray[1346]: 2024/03/04 18:16:02 127.0.0.1:46674 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:16:10 k8s-master01 xray[1346]: 2024/03/04 18:16:10 [Warning] [2594380722] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:16:12 k8s-master01 xray[1346]: 2024/03/04 18:16:12 127.0.0.1:46770 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:16:20 k8s-master01 xray[1346]: 2024/03/04 18:16:20 [Warning] [1302667946] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:16:22 k8s-master01 xray[1346]: 2024/03/04 18:16:22 127.0.0.1:46874 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:16:30 k8s-master01 xray[1346]: 2024/03/04 18:16:30 [Warning] [2697733957] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:16:32 k8s-master01 xray[1346]: 2024/03/04 18:16:32 127.0.0.1:46966 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:16:38 k8s-master01 xray[1346]: 2024/03/04 18:16:38 websocket: failed to close network connection: close tcp 192.168.10.10:43776->8.210.103.219:443: use of closed network connection
3月 04 18:16:40 k8s-master01 xray[1346]: 2024/03/04 18:16:40 websocket: failed to close network connection: close tcp 192.168.10.10:43786->8.210.103.219:443: use of closed network connection
3月 04 18:16:40 k8s-master01 xray[1346]: 2024/03/04 18:16:40 [Warning] [1423899102] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:16:42 k8s-master01 xray[1346]: 2024/03/04 18:16:42 127.0.0.1:47070 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:16:50 k8s-master01 xray[1346]: 2024/03/04 18:16:50 [Warning] [3280367621] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:16:50 k8s-master01 xray[1346]: 2024/03/04 18:16:50 websocket: failed to close network connection: close tcp 192.168.10.10:43890->8.210.103.219:443: use of closed network connection
3月 04 18:16:52 k8s-master01 xray[1346]: 2024/03/04 18:16:52 127.0.0.1:47164 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:16:58 k8s-master01 xray[1346]: 2024/03/04 18:16:58 websocket: failed to close network connection: close tcp 192.168.10.10:43974->8.210.103.219:443: use of closed network connection
3月 04 18:17:00 k8s-master01 xray[1346]: 2024/03/04 18:17:00 [Warning] [2142162998] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:17:10 k8s-master01 xray[1346]: 2024/03/04 18:17:10 [Warning] [1406668282] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:17:53 k8s-master01 xray[1346]: 2024/03/04 18:17:53 127.0.0.1:47750 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:18:03 k8s-master01 xray[1346]: 2024/03/04 18:18:03 127.0.0.1:47840 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:18:06 k8s-master01 xray[1346]: 2024/03/04 18:18:06 [Warning] [4145448540] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:18:13 k8s-master01 xray[1346]: 2024/03/04 18:18:13 127.0.0.1:47942 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:18:16 k8s-master01 xray[1346]: 2024/03/04 18:18:16 [Warning] [1365796855] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:18:23 k8s-master01 xray[1346]: 2024/03/04 18:18:23 127.0.0.1:48032 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:18:26 k8s-master01 xray[1346]: 2024/03/04 18:18:26 [Warning] [2392807403] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:18:33 k8s-master01 xray[1346]: 2024/03/04 18:18:33 127.0.0.1:48136 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:18:36 k8s-master01 xray[1346]: 2024/03/04 18:18:36 [Warning] [2814008583] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:18:46 k8s-master01 xray[1346]: 2024/03/04 18:18:46 [Warning] [2119998531] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:20:09 k8s-master01 xray[1346]: 2024/03/04 18:20:09 127.0.0.1:49040 accepted //registry-1.docker.io:443 [http -> proxy]

说实话，看了上面两个日志，我是摸不着头，因为userid和alterid都确认过都不知道多少次了，都感觉没问题

一度怀疑是xray的问题，于是换了一个客户端，采用v2ray的客服端

于是用v2ray进行本地服务配置，可还是出现同样的问题

后面网上说通过alter为0可以解决，然后还有其它乱七八着的解决方法，还是不行

终于，看到一条有用的信息，时间差

于是，更新centos的时间

 ntpdate time.windows.com

 再次查看

[root@k8s-master01 ~]# curl -x http://127.0.0.1:10809 https://www.google.com -v
* About to connect() to proxy 127.0.0.1 port 10809 (#0)
*   Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 10809 (#0)
* Establish HTTP proxy tunnel to www.google.com:443
> CONNECT www.google.com:443 HTTP/1.1
> Host: www.google.com:443
> User-Agent: curl/7.29.0
> Proxy-Connection: Keep-Alive
> 
< HTTP/1.1 200 Connection established
< 
* Proxy replied OK to CONNECT request
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* SSL connection using TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
* Server certificate:
*       subject: CN=www.google.com
*       start date: 2月 19 08:19:14 2024 GMT
*       expire date: 5月 13 08:19:13 2024 GMT
*       common name: www.google.com
*       issuer: CN=GTS CA 1C3,O=Google Trust Services LLC,C=US
> GET / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: www.google.com
> Accept: */*
> 
< HTTP/1.1 302 Found
< Location: https://www.google.com.hk/url?sa=p&hl=zh-CN&pref=hkredirect&pval=yes&q=https://www.google.com.hk/&ust=1710600070261911&usg=AOvVaw1xFQ6FZSUAQ0p_KF1PPren
< Cache-Control: private
< Content-Type: text/html; charset=UTF-8
< Content-Security-Policy-Report-Only: object-src 'none';base-uri 'self';script-src 'nonce-zeU1oF1mM8-Ul5Hpk8GhNw' 'strict-dynamic' 'report-sample' 'unsafe-eval' 'unsafe-inline' https: http:;report-uri https://csp.withgoogle.com/csp/gws/other-hp
< P3P: CP="This is not a P3P policy! See g.co/p3phelp for more info."
< Date: Sat, 16 Mar 2024 14:40:40 GMT
< Server: gws
< Content-Length: 372
< X-XSS-Protection: 0
< X-Frame-Options: SAMEORIGIN
< Set-Cookie: 1P_JAR=2024-03-16-14; expires=Mon, 15-Apr-2024 14:40:40 GMT; path=/; domain=.google.com; Secure
< Set-Cookie: AEC=Ae3NU9PNmRL7EUmFbkfvziLkI-U_QJBZOxNBfkb0OXkO9kOOvAlHiX_gSQ; expires=Thu, 12-Sep-2024 14:40:40 GMT; path=/; domain=.google.com; Secure; HttpOnly; SameSite=lax
< Set-Cookie: NID=512=A4a6jbVPAvqT8ipYJhTvbuS-FsX-hDEA90zLI0FhkT3oDJKoMsYaqQlRyllu2wH_Bw-_nTgAwCrvr4TogqxEOfh77CPlxc4A9jRMmHQBpWjqF7yFiByuBB6O6vgmQNDGALw5zZue0O8irX7h_2w4zRNUrOEZVA32rSLmYoJpl1s; expires=Sun, 15-Sep-2024 14:40:40 GMT; path=/; domain=.google.com; HttpOnly
< Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
< 
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>302 Moved</TITLE></HEAD><BODY>
<H1>302 Moved</H1>
The document has moved
<A HREF="https://www.google.com.hk/url?sa=p&amp;hl=zh-CN&amp;pref=hkredirect&amp;pval=yes&amp;q=https://www.google.com.hk/&amp;ust=1710600070261911&amp;usg=AOvVaw1xFQ6FZSUAQ0p_KF1PPren">here</A>.
</BODY></HTML>
* Connection #0 to host 127.0.0.1 left intact

成功解决

问题排查方向

VMess: Invalid User 可能的原因：

    1、客户端和服务器端的用户 ID 不匹配；
    2、客户端和服务器端的用户 alterId 不匹配；
    3、客户端与服务器的时间不匹配，误差不能超过90秒钟；
流光影下
关注
  • 9
    点赞
  • 踩
  • 7
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
关于使用v2rayn开启服务时报Failed to start的错误解决方法(亲测可用)
萧海的博客
05-28 1万+
点击参数设置：
Xray-yes:Xray安装脚本Xray安装脚本（VLESS + tcp + xtls）
03-07
X射线是的！ 又一个安装Xray的shell脚本 VLESS TCP XTLS + NGINX 需要root权限 Xray回落到nginx，nginx作为布局，放置一个静态网站 使用 一致 bash -c "$(curl -L git.io/xray-yes)" 安装 bash -c "$(curl -L git.io/xray-yes)" - install 更新 bash -c "$(curl -L git.io/xray-yes)" - update 卸载 bash -c "$(curl -L git.io/xray-yes)" - remove 功能 全自动安装nginx，配置静态页面，申请证书，安装Xray X射线是的！ 另一个安装Xray的Shell脚本 VLESS TCP XTLS + NGINX 需要root权限 Xray退回到nginx，后者用作存储静态网站的后端。
android手机访问app网页报错：net::ERR_PROXY_CONNECTION_FAILED
reblue520的专栏
10-26 2581
手机访问网页报错：net::ERR_PROXY_CONNECTION_FAILED 手机访问app中嵌入的html网页报错： net::ERR_PROXY_CONNECTION_FAILED 原来是手机网络设置了代理, 只要把代理去掉就ok了 ...
xray工具保姆级的安装与使用教程（非常详细）零基础入门到精通，收藏这一篇就够了
最新发布
2201_75362610的博客
05-18 838
提示：工具需要合理使用，读者使用不当与本作者无关，以下案例仅供参考。xray是一款辅助评估的扫描工具，不带有攻击。且支持 Windows / macOS / Linux 多种操作系统，本文中主要介绍他的安装以及使用。
解析 curl 命令错误：（35）Encountered end of file
十年运维开发经验的王义杰在此分享自己的知识和经验
09-21 5134
（35）Encountered end of file” 是一个常见的curl错误，通常表示在与服务器进行 SSL/TLS 握手或数据传输过程中，连接意外地关闭了。通过了解这个错误的常见原因和解决方案，我们可以更有效地避免和解决这种问题。这篇文章希望能帮助你理解这个问题，并提供了一系列解决方案和预防措施。通过这些方法，我们能确保网络请求更加稳定和可靠。希望这篇文章能帮助你解决遇到的问题，或者至少给你提供一个解决问题的方向。如果你有其他问题或需要进一步的解释，欢迎留言或咨询。我们会尽最大努力来帮助你。
Failed to start: app/proxyman/inbound: failed to listen TCP on 10808 ＞ transport/internet: failed
weixin_43874114的博客
04-12 2万+
启动服务器或者代理时出现监听TCP端口失败，可能是该端口被占用，已经存在了；需要先杀死该端口所用的进程再进行运行； 查看端口所在进程：netstat -ano|findstr “:10808” 运行结果： TCP 0.0.0.0:10808 0.0.0.0:0 LISTENING 1104 杀掉所在进程： taskkill /pid 1104 /f 之后再进行访问就行 ...
使用curl命令出现错误curl: (35) Encountered end of file的解决方法
~~~~~~~BUG FLY~~~~~~~~~
06-27 3623
使用curl命令下载文件时，出现报错。
Failed to start: app/proxyman/inbound: failed to listen TCP on 10808
Running_Wang的博客
08-03 2390
Failed to start: app/proxyman/inbound: failed to listen TCP on 10808 > transport/internet: failed to listen on address: 127.0.0.1:10808 > transport/internet/tcp: failed to listen TCP on 127.0.0.1:10808 > listen tcp 127.0.0.1:10808: bind: An attempt was mad
Xray-install:安装和升级Xray的最简单方法
03-20
用于在支持systemd的操作系统（例如CentOS / Debian / OpenSUSE）中安装Xray的Bash脚本。 installed: /etc/systemd/system/xray.service installed: /etc/systemd/system/xray@.service installed: /usr/local/bin/...
Xray-examples:Xray-core用法的一些示例
03-11
X射线示例从
protractor-xray-reporter:生成用于Xira的Jira测试执行以进行量角器测试
05-09
如何使用使用npm安装protractor-xray-reporter npm install --save-dev protractor-xray-reporter 更新您的protractor.conf.js文件const XrayReporter = require ( 'protractor-xray-reporter' ) ;// Jasmine does ...
xray-poc-generation::dna: 辅助生成 XRay YAML POC
05-06
:dna: XRay POC Generation XRay安全评估 > POC辅助生成工具。 关于XRay: 访问 即可直接使用。 :laptop: 本地运行 本地运行XRay POC Generation： git clone https://github.com/phith0n/xray-poc-generation cd ...
程序运行错误
fleaxin的博客
03-31 1932
重启“Internet Connection Sharing(ICS)”服务，再启动程序，问题解决。
Xray 安装与使用心得
diaobusi的博客
06-14 4585
存中…(img-kZZrq75U-1686719487446)]在burp suite上配置好我们刚才在xary设置的Ip和端口，点击run运行[外链图片转存中…(img-e9HVVsk2-1686719487447)]当我们访问我自己的靶机的时候，xray的被动扫描就已经开始了[外链图片转存中…(img-rpL1taDX-1686719487447)]已经被动扫描到多条漏洞，我们在看看保存的文件有哪些内容[外链图片转存中…(img-x9GGihkP-1686719487447)]
Xray的安装与使用（超详细）
热门推荐
qq_45157535的博客
02-22 2万+
本文章主要描述了Xray工具的安装与使用，超详细版本。
解决 curl: (35) Encountered end of file 问题
chunheli的博客
12-12 1万+
问题 在 Linux 服务器上（Centos 7）安装 docker-compose 时安装失败了，执行的安装命令为： curl -L "https://github.com/docker/compose/releases/download/1.28.6/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose 报错如下： 解决 定位发现是服务器的 443 端口未打开，执行以下命令： # 需要开启防火墙 system
【linux错误】HTTPS无法打开：curl: (35) Encountered end of file 和 linux上安装composer
西瓜的博客
04-01 1万+
需求：在linux上安装composer（该指令是tp5手册上的）[root@iz2zega6kootlf88q568d2z wx.xiyang66.top]# curl -sS https://getcomposer.org/installer | phpcurl: (35) Encountered end of file原因：服务器443端口未对外开放！建议使用：https://pkg.php...
centos7 letsencrypt curl: (35) Encountered end of file
____
04-24 5506
curl https://xxx.com/ -vvvletsencrypt curl: (35) Encountered end of file查看 nginx error日志no "ssl_certificate" is defined in server listening on SSL port while SSL handshaking, client: xxx.xxx.xxx.xxx, s
华为云安装docker compose curl: (35) Encountered end of file
m0_37121695的博客
05-20 511
在安装docker compose时 curl -SL https://github.com/docker/compose/releases/download/v2.5.0/docker-compose-linux-x86_64 -o /usr/local/bin/docker-compose 出现错误curl: (35) Encountered end of file 原因时因为华为云默认没有开始443端口，开启之后即可正常安装。 ...
./xray: error while loading shared libraries: libpcap.so.0.8: cannot open shared object file: No such file or directory
09-05
这个错误提示是由于缺少 libpcap.so.0.8 共享库文件导致的。libpcap 是一个用于网络数据包捕获的库，xray 可能依赖于该库文件进行工作。你可以尝试按照以下步骤来解决这个问题： 1. 确认 libpcap 是否已安装：运行命令 `dpkg -l | grep libpcap` 或 `yum list installed | grep libpcap` 来检查系统中是否已安装 libpcap。 2. 如果 libpcap 未安装，根据你使用的操作系统，可以运行以下命令之一进行安装： - Ubuntu/Debian：`sudo apt-get install libpcap0.8` - CentOS/RHEL：`sudo yum install libpcap` 3. 如果 libpcap 已安装但仍然出现该错误，可以尝试重新安装 libpcap： - Ubuntu/Debian：`sudo apt-get --reinstall install libpcap0.8` - CentOS/RHEL：`sudo yum reinstall libpcap` 4. 如果你仍然遇到问题，可能需要手动下载并安装 libpcap.so.0.8。你可以在网上搜索 libpcap.so.0.8 下载链接，并按照指示进行安装。 5. 安装完成后，确保 libpcap.so.0.8 被正确加载。你可以尝试重新运行 xray 程序，应该不再出现相应的错误。 请注意，以上步骤可能因操作系统和软件版本而略有不同。如果问题仍然存在，建议查阅相关文档或寻求更详细的技术支持。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值