留言板
你不说我怎么知道你想干嘛？
你说了我也不一定知道你想干嘛。
那你是说还是不说呢？
如果是遇到什么问题需要咨询，那么请先简要描述一下遇到了什么问题！！！
如果觉得问题可能有点复杂，可以在下方评论区简要描述问题之后再留个QQ号。
联系邮箱：admin#eveaz.com(“#”改成”@”)
本站采用了非常严格的留言过滤，如果提交之后未显示，请勿多次提交。
写写自己的故事，想想自己的未来！
你不说我怎么知道你想干嘛？
你说了我也不一定知道你想干嘛。
那你是说还是不说呢？
如果是遇到什么问题需要咨询，那么请先简要描述一下遇到了什么问题！！！
如果觉得问题可能有点复杂，可以在下方评论区简要描述问题之后再留个QQ号。
联系邮箱：admin#eveaz.com(“#”改成”@”)
本站采用了非常严格的留言过滤，如果提交之后未显示，请勿多次提交。
298 thoughts on “留言板”
你好，我早你这边看了VPS服务器，然后买好了 不过好像被墙了 能联系下你帮忙购买下域名吗
@杰哥 可以在评论区留下你的QQ号，我加你。
不方便的话，可以参考这篇文章自己买也行。
https://eveaz.com/1108.html
抱歉，前段时间太忙了，没空打理网站。
第五步：过渡固件恢复出厂
打开网页http://www.routerlogin.net/进入网件后台
步骤：高级→管理→备份设置→擦除（恢复出厂设置）
这个恢复出厂固件版本是V1.0.3.24_1.1.20。到这一步都没有任何问题，但是固件升级为正常的官方固件时，所有固件都提示：此固件文件不正确！请再次获取固件文件，确定是用于此产品的正确固件。 从官网下载版本号最近的也不行。。。 求指导！
@好几个柠檬 如果严格按文章操作是没有问题的，刷了过渡固件Merling-R7000-back-to-ofw.trx之后，还原一次固件，再刷R7000-V1.0.9.42_10.2.44.chk，之后再刷你自己需要的固件。
你好，我按照被封（11）的操作，网页显示内容为Bad Request。
但是输入v2ray显示
V2Ray 4.45.2 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.18.3 linux/amd64)A unified platform for anti-censorship.
2023/09/26 11:51:26 Using config from STDIN
2023/09/26 11:51:26 [Info] main/jsonem: Reading config: stdin:
输入v2ray就是出来这个。用客户端连接，测速提示远程服务器返回错误：（500）内部服务器错误。
VPS时间是正确的，v2ray启动状态是active (running) ，怀疑是v2ray安装有问题
@hon 抱歉，日志过于简洁，算不出来出了什么问题。
查看v2ray状态命令：systemctl status v2ray
大神求助，搬瓦工手机连上wifi就用不了，切换回移动网络又可以使用，请问这个能怎么解决吗？
@min 排除法：手机移动网络是哪个运营商？其它运营商移动网络有没有问题？WIFI又是哪个运营商？其它WIFI有没有问题？
@言小五 手机移动网络的移动和联通都可以，电信的没试过，wifi的移动联通电信都不行，台式接宽带的，移动试了可以，电信的不行
@言小五 手机移动网络的三大运营商都可以，wifi的三大都不行，宽带的目前电信的不行，移动的可以，联通的不知道，搬瓦工方面没问题。
I can confirm that currently we are not experiencing any service interruptions; all our equipment and network are functioning normally.
1. Please kindly check ports at: http://port.ping.pe
for all your applications, and change ports if necessary.
(If you’re using Shadowsocks, you might try changing Shadowsocks ports, this seem to help in many cases, according to our clients feedback).
2. Alternatively, if your current plan supports migration, and your IP is not blocked, please try “Migrate to another DC”. This will change the IP.
Please kindly note that all our services are self-managed. While we invest heavily into making sure all our equipment and networks are kept in the best possible shape, we do not manage or offer support for customer’s applications. In other words, we do not assist with installing and configuring applications, troubleshooting, recovering from backups, etc. – these are the sole responsibility of the Customer. Should you need assistance of such level, then we highly recommend hiring a Linux administrator who can help you with these tasks.
@言小五
配置成功报错这样子Vmess-233v2.com_v2ray.*****.xyz(v2ray***xyz:443)
启动服务(2023/4/11/周二 0:00:02)......
V2Ray 4.18.0 (Po) 20190228
A unified platform for anti-censorship.
2023/04/11 00:00:03 [Warning] v2ray.com/core: V2Ray 4.18.0 started
2023/04/11 00:00:10 tcp:127.0.0.1:52343 accepted tcp:b1.nel.goog:443
2023/04/11 00:00:17 tcp:127.0.0.1:52346 accepted tcp:accounts.google.com:443
2023/04/11 00:00:30 tcp:127.0.0.1:52354 accepted tcp:www.google.com:443
2023/04/11 00:00:40 tcp:127.0.0.1:52359 accepted tcp:beacons.gcp.gvt2.com:443
2023/04/11 00:00:41 tcp:127.0.0.1:52361 accepted tcp:optimizationguide-pa.googleapis.com:443
@min 这个日志没有任何报错信息，这就是常规日志。
你客户端v2ray版本太低了，升级v4.45.2试试。
@言小五 好的，太感谢帮忙啦！！
@言小五
2023/04/12 02:25:08 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://v2ray.******.xyz/): > write tcp 192.168.5.16:52521->104.21.9.62:443: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://v2ray.******.xyz/): > write tcp 192.168.5.16:52525->104.21.9.62:443: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://v2ray.******.xyz/): > write tcp 192.168.5.16:52550->104.21.9.62:443: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://v2ray.******.xyz/): > write tcp 192.168.5.16:52575->104.21.9.62:443: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://v2ray.******.xyz/): > write tcp 192.168.5.16:52615->104.21.9.62:443: i/o timeout] > v2ray.com/core/common/retry: all retry attempts failed大神，刚刚弄了一会出现这个问题了，这个是报错了吗 🙁
@min 你这个Cloudflare的IP被部分地区/运营商屏蔽了。
很简单的判断方式，你网页打开https://v2ray.******.xyz/ 就知道了，能打开，上网就无问题。
@言小五 确实打不开，Bad Request，这个有什么办法解决吗？有没有傻瓜式教程的那些吗？包括更新v2ray那个都不懂这些:(
@min 不，400 Bad Request代表WebSocket服务没问题，这就是我所说的能打开。打不开是提示超时啊什么的。
如果显示Bad Request，是没有类似之前你回复的报错日志的。只有在打不开的情况下，才会有那些日志。
@言小五 一直说文件名不正确
@烦躁 抱歉，不知道你在说什么。
r8000 软件中心一直在显示之中怎么破大神！梅林版本380.65_X7.4
@john 按 https://eveaz.com/1087.html 一文准备工作7.6步骤操作。
大神， 我按照你的操作后可以访问google等网站了， 十分感谢！！ 最近在玩chatgpt, 我发现还是没法链接到chatgpt.openai.com; Access denied!! 有什么办法破解吗？
@yuntao Access denied代表VPS的IP段被OpenAI封禁了，可以试一下Cloudflare的WARP IPv6。
好的，大神，谢谢你的指点，辛苦了！！！我再试试你的方法，期待有奇迹发生。谢谢！~~~
刚用了两天的搬运工IP被封了，哭死，买了一年
所以最后的解决方案其实就是SS了对吧,白白研究了V2RAY搭建…
@阿乐 链接：https://eveaz.com/1106.html
@言小五 看到你的文章，让我十分佩服，目前我的被墙ip连接不上，我也用我本地的桥ping过被墙的ip，是通的，另外我的数据设置基本都没问题，但我还是没有脸上被墙的服务器，请求帮助，有偿
@Tongsaiv2 已经再相关文章评论区回复你了，这里不再赘述。
感谢分享梅林系列文章，受益匪浅！
祝兔年万事顺意！
博主你好。小白想学习并购，但是不知道怎么选择。如方便请联系我谢谢！
@小白 你好，
博客关于页面留有博主邮箱，直接邮箱联系即可。
2022/11/03 10:57:51 [Warning] [1581744479] app/proxyman/inbound: connection ends > proxy/http: failed to read http request > read tcp 127.0.0.1:10809->127.0.0.1:56875: wsarecv: An existing connection was forcibly closed by the remote host.2022/11/03 11:08:42 [Warning] [1216983921] proxy/http: failed to read response from 43.154.130.190 > io: read/write on closed pipe
2022/11/03 11:08:42 [Warning] [1216983921] app/proxyman/inbound: connection ends > proxy/http: connection ends > proxy/http: failed to write response > write tcp 127.0.0.1:10809->127.0.0.1:57112: wsasend: An established connection was aborted by the software in your host machine.
2022/11/03 11:49:35 [Warning] [4248763394] app/proxyman/inbound: connection ends > proxy/http: failed to read http request > parse "http://chat\\filetype\\fileicon_xls.png/": invalid character "\\" in host name
2022/11/03 12:02:09 [Warning] failed to handler mux client connection > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://us04.xxx.com/): > dial tcp 104.21.19.100:443: i/o timeout] > common/retry: all retry attempts failed
2022/11/03 12:02:18 [Warning] failed to handler mux client connection > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://us04.xxx.com/): > dial tcp 104.21.19.100:443: i/o timeout] > common/retry: all retry attempts failed
2022/11/03 12:02:39 [Warning] failed to handler mux client connection > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://us04.xxx.com/): > dial tcp 104.21.19.100:443: i/o timeout] > common/retry: all retry attempts failed
2022/11/03 12:02:39 [Warning] [1839808856] proxy/http: failed to read response from www.gstatic.com > unexpected EOF
2022/11/03 14:05:38 [Warning] [3228217983] app/proxyman/inbound: connection ends > proxy/http: failed to read http request > parse "http://chat\\filetype\\fileicon_zip.png/": invalid character "\\" in host name
2022/11/03 14:31:20 [Warning] [3287135648] app/proxyman/inbound: connection ends > proxy/http: failed to read http request > parse "http://chat\\filetype\\fileicon_zip.png/": invalid character "\\" in host name
2022/11/03 14:56:51 [Warning] failed to handler mux client connection > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://us04.xxx.com/): > dial tcp 172.67.185.190:443: i/o timeout] > common/retry: all retry attempts failed
2022/11/03 14:56:51 [Warning] [3905370847] proxy/http: failed to read response from x1.c.lencr.org > unexpected EOF
2022/11/03 14:56:51 [Warning] [3905370847] app/proxyman/inbound: connection ends > proxy/http: connection ends > proxy/http: failed to write response > write tcp 127.0.0.1:10809->127.0.0.1:61996: wsasend: An existing connection was forcibly closed by the remote host.
2022/11/03 14:57:11 [Warning] failed to handler mux client connection > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://us04.xxx.com/): > dial tcp 172.67.185.190:443: i/o timeout] > common/retry: all retry attempts failed
2022/11/03 14:57:12 [Warning] failed to handler mux client connection > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://us04.xxx.com/): > dial tcp 172.67.185.190:443: i/o timeout] > common/retry: all retry attempts failed
2022/11/03 14:57:12 [Warning] [107826236] proxy/http: failed to read response from x1.c.lencr.org > unexpected EOF
2022/11/03 14:57:12 [Warning] [97662048] proxy/http: failed to read response from www.gstatic.com > unexpected EOF
2022/11/03 14:57:12 [Warning] [265235697] proxy/http: failed to read response from ctldl.windowsupdate.com > unexpected EOF
2022/11/03 14:57:12 [Warning] [265235697] app/proxyman/inbound: connection ends > proxy/http: connection ends > proxy/http: failed to write response > write tcp 127.0.0.1:10809->127.0.0.1:62038: wsasend: An existing connection was forcibly closed by the remote host.
帮我看下这个是什么原因导致的，用的 WebSocket + TLS + CF，感谢作者。
@key
failed to find an available destinationfailed to dial WebSocket
检查这两项，一是本地与CDN之间网络是否正常，二是服务端WS环境是否OK。
@言小五 用的你的教程一键搭建，套了个cf，怎么测试
@k ???你想咋测试???
博主您好，请问一下，路由器R8000P,固件版本384 r7900p，能否往386刷？感谢
@春卷的春卷 如果你能找到适配了软件中心的386固件，或者压根就不需要软件中心，可以尝试。
毕竟KoolCenter没有对该型号适配任何380/384/386固件。
求新的购买网站
@莱曼 抱歉，不知道你指的什么。
请仔细看本页面描述。
高手您好，2-3年之前手里有R7000的时候学习了您的文章《Netgear网件R7000路由器折腾日记》，受益匪浅，再次感谢。今天换了rax120，兴冲冲刷梅林固件，结果悲剧变砖了。可否请教一下如何抢救回来哦，哪怕先抢救回到网件固件哦。我当时是参考了下面这个链接的教程：“网件RAX120刷机教程_paldier的博客-CSDN博客_网件rax120 ”https://blog.csdn.net/paldier/article/details/120219735?spm=1001.2014.3001.5502
跪求高手指导一下哦，有偿也没问题啊
@June0602 路由器电源灯能不能亮？如果能亮的话，用nmrpflash试一下，之前有个网友华硕AC86U刷机断电变砖，我用这个帮他救回来了。
https://github.com/jclehner/nmrpflash
@言小五 感谢指点，已经救回至官方固件了。没看到您这里有rax120的相关文章或者梅林固件，请教一下：可否用R7000或者koolshare rax80的固件并大致参考《Netgear网件R7000路由器折腾日记》来折腾？
@June0602 不管是华硕还是网件，刷机方法都是差不多的，唯一要注意的就是对应型号的固件和刷机过程中的一些注意事项。
但是KoolCenter目前没有RAX120的梅林固件。
@言小五 大神你好，看了你那篇网件R7000的刷机教程，我现在的问题是，刷了过渡件后，恢复出厂设置，再重启路由器，到这个环节后，路由器就会变成砖头，无限重启，是不是重启的时间要等好长一段时间 的啊，求解！！！谢谢！
@温柔一刀劈 R7000刷回原厂的文章中，我没写过手动重启吧，恢复出厂设置之后是自动重启。
原厂固件重启完成大概需要两分钟。
无限重启的时候，你要观察几个指示灯是什么情况。你没说，我也就不清楚现在是啥状况。
尝试30-30-30复位方法：按住reset 30秒，按住reset拔电源后等30秒，插入电源并按住reset等30秒后松开。也就是说一直按住reset90秒。
正常情况下，复位之后，恢复你最后一次刷入的原厂固件。30-30-30复位方法有个很重要的前提，你没刷过CFE。