近期一些现象的提示

本文转载自:https://v2raytech.com/hints-on-recent-cases/,如文中内容有错误请到原文查看原始版(最新版)

最近是敏感时期,部分人会发现平时好好能上外网,突然就不行了!这又是怎么一回事呢?

443端口被封现象:平时用的好好的,突然出现这样的报错:

app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp xxx.xxx.x.xx:443: i/o timeout dial tcp xxx.xxx.x.xx:443: operation was canceled] > common/retry: all retry attempts failed

正如 别太把自己当回事 中所说,平时大家成群结队闯红灯没人管,一到上面来检查或者搞文明城市等活动,被抓到那就认了吧。并不是针对你,而是特殊时期,总是需要一些炮灰祭天,让其他猴子安分点。所以敏感时期,安分点或者谨慎点。

收手吧阿祖,外面全是警察

收手吧阿祖,外面全是警察

OK,再回到技术选择上。敏感时期,什么协议最稳呢?个人推荐VMESS+WS+TLS,或者VLESS+WS+TLS。为什么呢?因为本站一件脚本中,这两种协议按照常规方式搭建了一个网站。没错,是一个完整的、和正经网站没区别的网站。不管是GFW主动探测,还是科学上网,完全按照浏览网站的方式来,基本上不存在额外的特征,被针对的可能性就小很多。本人一直用的这两种,没出现过问题。

没看过XTLS和trojan/trojan-go的代码,不能说他们存在问题,只是在有的选择的情况下,本人还是会优先选用WS+TLS的方式。对现在的设备和VPS来说,性能不是问题。WS+TLS方式,稳定好用,退一步来说被墙了套上CF也直接能用,个人是推荐使用的。

另外一点是,建议使用一键脚本安装时选择“允许搜索引擎爬取网站”:

允许爬虫访问网站

允许爬虫访问网站

选择允许,百度、搜过、360等网站的爬虫也许就会去爬你的网站,给你的VPS和IP带来许多正常流量。有正常流量掩护,你个人的流量也就更安全。

脚本默认是不允许爬虫访问,意味着绝大多数情况下,只有你的设备和服务器有通信流量,单个IP频繁访问一个不知名国外网站,就算被封了也不会有什么影响,GFW也就能放心的封你的IP或者443端口了。

为什么脚本不设置为允许呢?因为开启会消耗额外的流量,也可能一天几M,也可能一天几G,有些人看到产生莫名的流量会觉得脚本有问题等。为了避免这种扯淡的事情,自然是不能默认开启的。

所以,要想稳,推荐使用VMESS/VLESS+WS+TLS方式,并且允许爬虫访问。就本人观测,开启允许爬虫,一天消耗不了多少额外的流量,基本上不用担心。如果真的消耗很多额外流量,重新运行一键脚本关闭就是了。

最后,IP或者443端口被封了怎么办?IP被封可以换、重新买VPS,或者套CF;443端口被封,重新运行一键脚本,换其他端口,比如8443、12345等端口就可以了。

不要慌,现在遇到的问题都好解决。也被太蹦跶,更艰难的时刻正在前方等着你。

参考

V2ray一键脚本

Xray一键脚本

trojan一键脚本

《近期一些现象的提示》上有6条评论

  1. 您好,本人采用的是VLESS+TCP+XTLS,前几天443端口用站长之家查显示关闭,感觉是443被搞了,随后更改为433端口,能正常翻墙了,但是感觉速度下降,今天更改回443发现能用,想问下443端口是不是对于直接访问HTTPS来说有速度提升呢?

  2. 6月底开始发现手机用移动网络能连接正常,笔记本用电信宽带连不上,提示:配置成功
    [VLESS] yun-clone(185***143:8443)
    启动服务(2021-7-20 13:27:48)…
    Xray 1.4.2 (Xray, Penetrates Everything.) Custom (go1.16.2 windows/amd64)
    A unified platform for anti-censorship.
    2021/07/20 13:27:49 [Info] infra/conf/serial: Reading config: C:\Users\Administrator\Desktop\v2rayN-Core\config.json
    2021/07/20 13:27:49 [Warning] core: Xray 1.4.2 started
    2021/07/20 13:27:58 127.0.0.1:60962 accepted //www.google.com:443 [http -> proxy]
    2021/07/20 13:27:59 127.0.0.1:59860 accepted //www.google.com:443 [http -> proxy]
    2021/07/20 13:28:00 127.0.0.1:61236 accepted //www.google.com:443 [http -> proxy]
    2021/07/20 13:28:00 127.0.0.1:52386 accepted //www.google.com:443 [http -> proxy]
    2021/07/20 13:28:00 127.0.0.1:59083 accepted //www.google.com:443 [http -> proxy]
    2021/07/20 13:28:00 127.0.0.1:64680 accepted //www.google.com:443 [http -> proxy]
    2021/07/20 13:28:03 127.0.0.1:54249 accepted //gmail.com:443 [http -> proxy]
    2021/07/20 13:28:03 127.0.0.1:57458 accepted //gmail.com:443 [http -> proxy]
    2021/07/20 13:28:14 127.0.0.1:63069 accepted //qny.smzdm.com:443 [http >> proxy]
    2021/07/20 13:28:15 127.0.0.1:63073 accepted http://www.51nbgu.com/qinxu.jsp [http >> proxy]
    2021/07/20 13:28:19 127.0.0.1:55643 accepted //qny.smzdm.com:443 [http >> proxy]
    2021/07/20 13:28:31 [Warning] [2272351557] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp 185.245.1.143:8443: i/o timeout dial tcp 185.245.1.143:8443: operation was canceled] > common/retry: all retry attempts failed
    2021/07/20 13:28:32 [Warning] [1826772594] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp 185.245.1.143:8443: i/o timeout dial tcp 185.245.1.143:8443: operation was canceled] > common/retry: all retry attempts failed
    2021/07/20 13:28:33 [Warning] [342691728] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp 185.245.1.143:8443: i/o timeout dial tcp 185.245.1.143:8443: operation was canceled] > common/retry: all retry attempts failed
    2021/07/20 13:28:33 [Warning] [2507916222] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp 185.245.1.143:8443: i/o timeout dial tcp 185.245.1.143:8443: operation was canceled] > common/retry: all retry attempts failed
    2021/07/20 13:28:33 [Warning] [4004047718] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp 185.245.1.143:8443: i/o timeout dial tcp 185.245.1.143:8443: operation was canceled] > common/retry: all retry attempts failed
    2021/07/20 13:28:33 [Warning] [1276542472] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp 185.245.1.143:8443: i/o timeout dial tcp 185.245.1.143:8443: operation was canceled] > common/retry: all retry attempts failed
    2021/07/20 13:28:34 127.0.0.1:56785 accepted //gmail.com:443 [http -> proxy]
    2021/07/20 13:28:34 127.0.0.1:64424 accepted //gmail.com:443 [http -> proxy]
    2021/07/20 13:28:36 [Warning] [1767573927] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp 185.245.1.143:8443: i/o timeout dial tcp 185.245.1.143:8443: operation was canceled] > common/retry: all retry attempts failed
    2021/07/20 13:28:36 [Warning] [2873109190] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp 185.245.1.143:8443: i/o timeout dial tcp 185.245.1.143:8443: operation was canceled] > common/retry: all retry attempts failed
    2021/07/20 13:28:38 127.0.0.1:58897 accepted //qny.smzdm.com:443 [http >> proxy]
    2021/07/20 13:28:47 [Warning] [1932947768] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp 185.245.1.143:8443: i/o timeout dial tcp 185.245.1.143:8443: operation was canceled] > common/retry: all retry attempts failed
    2021/07/20 13:28:52 [Warning] [3801610939] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp 185.245.1.143:8443: i/o timeout dial tcp 185.245.1.143:8443: operation was canceled] > common/retry: all retry attempts failed

    已重装系统和脚本,端口也换过了。都没有解决。

  3. 你好请问我的服务器是centos7.6的然后用了脚本安装到默认重启步骤之后,就无法启动网卡了,在Centos7.5也测试过 一样无法启动网卡

发表评论

您的电子邮箱地址不会被公开。 必填项已用*标注