极简一键脚本 自定义端口 NaiveProxy 与 Caddy V2 前置的 VLESS/Vmess V2Ray 共存 可开 CDN
* 推荐使用
1. 极简一键脚本搭 Caddy V2 前置的 VLESS 或 Vmess+WebSocket+TLS
设置好域名解析, 如 vless.mydomain.com, CDN
bash <(curl -L https://github.com/crazypeace/v2ray_wss/raw/main/install.sh)
搭完自己检查一下是否能正常使用
CDN
2. 搭建 NaiveProxy
2.1 设置域名解析, 如 np.mydomain.com, CDN 关掉
-update-
所有以下这些步骤,我做成了一个一键脚本。执行这个脚本,以下步骤都不用手搓了。
bash <(curl -L https://github.com/crazypeace/naive/raw/main/install.sh)
2.2 用 Caddy 官方脚本安装 Caddy
来源: https://caddyserver.com/docs/install#debian-ubuntu-raspbian
sudo apt install -y debian-keyring debian-archive-keyring apt-transport-httpscurl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpgcurl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.listsudo apt updatesudo apt install caddy
2.3 下载 NaiveProxy 作者编译的 caddy
https://github.com/klzgrad/forwardproxy/releases 找最新的版本
cd /tmp
wget https://github.com/klzgrad/forwardproxy/releases/download/caddy2-naive-20221007/caddy-forwardproxy-naive.tar.xz
tar -xf caddy-forwardproxy-naive.tar.xz
cd caddy-forwardproxy-naive
2.4 替换 caddy 程序
service caddy stop
cp caddy /usr/bin/
2.5 修改 Caddfile 添加 NaiveProxy 的配置部分
在
{order forward_proxy before file_server}:443, np.mydomain.com {tls e16d9cb045d7@gmail.comforward_proxy {basic_auth 用户名 密码hide_iphide_viaprobe_resistance}file_server {root /var/www/html}}
也可以在撰写窗格里执行
sed -i '1i {\order forward_proxy before file_server\}\:443, np.mydomain.com {\tls e16d9cb045d7@gmail.com\forward_proxy {\basic_auth 用户名 密码\hide_ip\hide_via\probe_resistance\}\file_server {\root /var/www/html\}\}' /etc/caddy/Caddyfile
2.6 写个简单的 html 页面
mkdir -p /var/www/html
echo "hello world" > /var/www/html/index.html
2.7 启动 NaiveProxy
service caddy start
测试一下你的
3. [可选项] 自定义 NaiveProxy 端口
编辑
像下面这样
重启
service caddy restart
检查一下工作正常
4. [可选项] NaiveProxy 屏蔽墙内流量
NaiveProxy 没有路由模块,需要用 “外部” 方案处理墙内流量问题
========
正常操作日志
root@391932510hax:~# bash <(curl -L https://github.com/crazypeace/naive/raw/main/install.sh)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 12136 100 12136 0 0 19797 0 --:--:-- --:--:-- --:--:-- 796k
_ ___
___ ___ __ __ ___ _| | _|___ __ __ _ ___
|-_ |_ | | |-_ | _ | |- _| | |_| |_ |
|___|___| _ |___|___|_|_|___| _ |___|___|
|_____| |_____|
此脚本仅兼容于Debian 10+ 系统. 如果你的系统不符合, 请 Ctrl+C 退出脚本
可以去 https://github.com/crazypeace/naive 查看脚本整体思路和关键命令, 以便针对你自己的系统做出调整.
有问题加群 https://t.me/+ISuvkzFGZPBhMzE1
本脚本支持带参数执行, 在参数中输入域名, 网络栈, 端口, 用户名, 密码. 详见GitHub.
----------------------------------------------------------------
按 Enter 回车键 继续....或按 Ctrl + C 取消.
Hit:1 http://deb.debian.org/debian bullseye InRelease
Get:2 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Get:3 http://security.debian.org/debian-security bullseye-security InRelease [48.4 kB]
Get:4 https://dl.cloudsmith.io/public/caddy/stable/deb/debian any-version InRelease [7505 B]
Get:5 http://security.debian.org/debian-security bullseye-security/main amd64 Packages [226 kB]
Get:6 http://security.debian.org/debian-security bullseye-security/main Translation-en [147 kB]
Get:7 https://dl.cloudsmith.io/public/caddy/stable/deb/debian any-version/main amd64 Packages [2200 B]
Fetched 475 kB in 2s (230 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
21 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
jq is already the newest version (1.6-2.1).
qrencode is already the newest version (4.1.1-1).
wget is already the newest version (1.21-1+deb11u1).
curl is already the newest version (7.74.0-1.3+deb11u5).
sudo is already the newest version (1.9.5p2-3+deb11u1).
The following additional packages will be installed:
git-man libcurl3-gnutls liberror-perl
Suggested packages:
git-daemon-run | git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb git-cvs git-mediawiki git-svn
The following NEW packages will be installed:
git git-man libcurl3-gnutls liberror-perl
0 upgraded, 4 newly installed, 0 to remove and 21 not upgraded.
Need to get 7717 kB of archives.
After this operation, 38.7 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 liberror-perl all 0.17029-1 [31.0 kB]
Get:2 http://security.debian.org/debian-security bullseye-security/main amd64 libcurl3-gnutls amd64 7.74.0-1.3+deb11u5 [343 kB]
Get:3 http://security.debian.org/debian-security bullseye-security/main amd64 git-man all 1:2.30.2-1+deb11u1 [1829 kB]
Get:4 http://security.debian.org/debian-security bullseye-security/main amd64 git amd64 1:2.30.2-1+deb11u1 [5514 kB]
Fetched 7717 kB in 1s (6070 kB/s)
Selecting previously unselected package libcurl3-gnutls:amd64.
(Reading database ... 28564 files and directories currently installed.)
Preparing to unpack .../libcurl3-gnutls_7.74.0-1.3+deb11u5_amd64.deb ...
Unpacking libcurl3-gnutls:amd64 (7.74.0-1.3+deb11u5) ...
Selecting previously unselected package liberror-perl.
Preparing to unpack .../liberror-perl_0.17029-1_all.deb ...
Unpacking liberror-perl (0.17029-1) ...
Selecting previously unselected package git-man.
Preparing to unpack .../git-man_1%3a2.30.2-1+deb11u1_all.deb ...
Unpacking git-man (1:2.30.2-1+deb11u1) ...
Selecting previously unselected package git.
Preparing to unpack .../git_1%3a2.30.2-1+deb11u1_amd64.deb ...
Unpacking git (1:2.30.2-1+deb11u1) ...
Setting up libcurl3-gnutls:amd64 (7.74.0-1.3+deb11u5) ...
Setting up liberror-perl (0.17029-1) ...
Setting up git-man (1:2.30.2-1+deb11u1) ...
Setting up git (1:2.30.2-1+deb11u1) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+deb11u5) ...
安装Caddy 最新版本
----------------------------------------------------------------
sudo: unable to resolve host 391932510hax.localdomain: Name or service not known
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
apt-transport-https is already the newest version (2.2.4).
debian-archive-keyring is already the newest version (2021.1.1).
debian-keyring is already the newest version (2021.07.26).
0 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.
sudo: unable to resolve host 391932510hax.localdomain: Name or service not known
sudo: unable to resolve host 391932510hax.localdomain: Name or service not known
# Source: Caddy
# Site: https://github.com/caddyserver/caddy
# Repository: Caddy / stable
# Description: Fast, multi-platform web server with automatic HTTPS
deb [signed-by=/usr/share/keyrings/caddy-stable-archive-keyring.gpg] https://dl.cloudsmith.io/public/caddy/stable/deb/debian any-version main
deb-src [signed-by=/usr/share/keyrings/caddy-stable-archive-keyring.gpg] https://dl.cloudsmith.io/public/caddy/stable/deb/debian any-version main
sudo: unable to resolve host 391932510hax.localdomain: Name or service not known
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Get:4 https://dl.cloudsmith.io/public/caddy/stable/deb/debian any-version InRelease [7505 B]
Fetched 7505 B in 2s (4931 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
21 packages can be upgraded. Run 'apt list --upgradable' to see them.
sudo: unable to resolve host 391932510hax.localdomain: Name or service not known
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
caddy
1 upgraded, 0 newly installed, 0 to remove and 20 not upgraded.
Need to get 14.8 MB of archives.
After this operation, 13.3 kB of additional disk space will be used.
Get:1 https://dl.cloudsmith.io/public/caddy/stable/deb/debian any-version/main amd64 caddy amd64 2.6.4 [14.8 MB]
Fetched 14.8 MB in 2s (7787 kB/s)
(Reading database ... 29568 files and directories currently installed.)
Preparing to unpack .../archives/caddy_2.6.4_amd64.deb ...
Unpacking caddy (2.6.4) over (2.6.3) ...
Setting up caddy (2.6.4) ...
Processing triggers for man-db (2.9.4-2) ...
本系统架构是amd64, 你同意直接下载 Na?veProxy 作者编译好的 Caddy 吗?
Y, 使用编译好的Caddy; n, 重新编译. (直接回车默认 Y)
(Y/n):
下载Na?veProxy 作者编译的 Caddy
----------------------------------------------------------------
rm: cannot remove 'caddy-forwardproxy-naive.tar.xz': No such file or directory
rm: cannot remove 'caddy-forwardproxy-naive': No such file or directory
--2023-02-15 22:14:57-- https://github.com/klzgrad/forwardproxy/releases/download/caddy2-naive-20221007/caddy-forwardproxy-naive.tar.xz
Resolving github.com (github.com)... 140.82.113.4
Connecting to github.com (github.com)|140.82.113.4|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://objects.githubusercontent.com/github-production-release-asset-2e65be/266250280/efa18c3e-4192-4207-a14f-1de0a8446975?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20230215%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230215T151448Z&X-Amz-Expires=300&X-Amz-Signature=7747661ab99f9064919d1b7ef410e660d9ce560008f4de6bde2adaae0dfea246&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=266250280&response-content-disposition=attachment%3B%20filename%3Dcaddy-forwardproxy-naive.tar.xz&response-content-type=application%2Foctet-stream [following]
--2023-02-15 22:14:58-- https://objects.githubusercontent.com/github-production-release-asset-2e65be/266250280/efa18c3e-4192-4207-a14f-1de0a8446975?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20230215%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230215T151448Z&X-Amz-Expires=300&X-Amz-Signature=7747661ab99f9064919d1b7ef410e660d9ce560008f4de6bde2adaae0dfea246&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=266250280&response-content-disposition=attachment%3B%20filename%3Dcaddy-forwardproxy-naive.tar.xz&response-content-type=application%2Foctet-stream
Resolving objects.githubusercontent.com (objects.githubusercontent.com)... 185.199.108.133, 185.199.109.133, 185.199.110.133, ...
Connecting to objects.githubusercontent.com (objects.githubusercontent.com)|185.199.108.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10192968 (9.7M) [application/octet-stream]
Saving to: 'caddy-forwardproxy-naive.tar.xz'
caddy-forwardproxy-naive.tar.xz 100%[====================================================================================================>] 9.72M 3.74MB/s in 2.6s
2023-02-15 22:15:01 (3.74 MB/s) - 'caddy-forwardproxy-naive.tar.xz' saved [10192968/10192968]
v2.6.1 h1:EDqo59TyYWhXQnfde93Mmv4FJfYe00dO60zMiEt+pzo=
替换Caddy 可执行文件
----------------------------------------------------------------
xkcd密码生成器页面
----------------------------------------------------------------
rm: cannot remove '/var/www/xkcdpw-html': No such file or directory
Cloning into '/var/www/xkcdpw-html'...
remote: Enumerating objects: 13, done.
remote: Counting objects: 100% (13/13), done.
remote: Compressing objects: 100% (11/11), done.
remote: Total 13 (delta 0), reused 7 (delta 0), pack-reused 0
Receiving objects: 100% (13/13), 143.65 KiB | 1.46 MiB/s, done.
请输入一个 正确的域名 Input your domain
(例如: mydomain.com): nphax.tzzhu.gq
你的域名Domain = nphax.tzzhu.gq
----------------------------------------------------------------
如果你的小鸡是双栈(同时有 IPv4 和 IPv6 的 IP),请选择你把 v2ray 搭在哪个'网口'上
如果你不懂这段话是什么意思, 请直接回车
Input 4 for IPv4, 6 for IPv6: 6
域名解析 = 我确定已经有解析了
----------------------------------------------------------------
请输入 端口 [1-65535], 不能选择 80端口
(默认端口port: 443):
端口Port = 443
----------------------------------------------------------------
请输入 用户名 Input your username
(默认: 10dfbe08d85c5aa5):
你的用户名Username = 10dfbe08d85c5aa5
----------------------------------------------------------------
请输入 密码 Input your password
(默认: a8d68ff63b647aff):
你的密码Password = a8d68ff63b647aff
----------------------------------------------------------------
修改Caddyfile
----------------------------------------------------------------
启动Na?veProxy 服务端 (Caddy)
----------------------------------------------------------------
Na?veProxy配置参数
----------------------------------------------------------------
域名Domain: nphax.tzzhu.gq
端口Port: 443
用户名Username: 10dfbe08d85c5aa5
密码Password: a8d68ff63b647aff
https://MTBkZmJlMDhkODVjNWFhNTphOGQ2OGZmNjNiNjQ3YWZmQG5waGF4LnR6emh1LmdxOjQ0Mw==
以下两个二维码完全一样的内容
█████████████████████████████████████████████
█████████████████████████████████████████████
████ ▄▄▄▄▄ █▀▄█▀ ▀▀▄ █▀▄▀▀▀ ▀▀█ ▄▄▄▄▄ ████
████ █ █ █▄ ▄ ▀▀▄▄ ▀▀█ ▀▀▀ █▄█ █ █ ████
████ █▄▄▄█ █ ▀█▀█ █▄▄ ▀ ▀█▀▄▄ ▄█ █▄▄▄█ ████
████▄▄▄▄▄▄▄█ ▀▄█ █ █▄▀ █▄▀▄▀▄█ ▀ █▄▄▄▄▄▄▄████
████▄▄█▄▀▀▄ ▀▀ ▀██▀ █▀█▄▀▀▀▀▀▀ █▀▀ ▄▄▀ ▄▀████
████▄ █ ▄▄▄█▀▀███▀▀▄██ █▀▀▀█ ▄▀▀██▄ ▀▄▀ ████
████▄▄▀▄█ ▄▄ ▀▀ ██▀▄▄▀ ▀▀██▄ ▀█ ▀▄███ ████
████▄▀██▄█▄█ ▀▄█ ▀▀▄ ▄▀ ▀ █ ██ ▄▀▄▀ █▀▄████
█████▀▄█▄▄▄▄ ██▄█▄▄ ▄▀█▄▄ ▀█▀▄▀ ▀▄▄▄ █ ▀ ████
██████▀▄▀▄▄▄▄▀▄▀█ █▀▀ ▀▀ ▀██▄▄▀▀ ▄▀▀ ▄▀ ▄████
████ █▄█ ▄▄▄█▄ ▀▄▀ ███▄ ▀█ ▀▄▄ ▀▄█▄█ █ ████
█████▀▄█▄▀▄███▄ ▄▄▀▄▄▄ ▀ ▀██▀▄▄ █▄█▄▄████
████▄ █ ▀▄█▄██ █▀ ▀▀█▀ ▀ ▀▀▀▄▄▄▀▄▄ ▄ ████
████▄▀ ▀▀▄▄▄▀▄▀ █▄▄▀▀ █▀▀ █ ██▀▀ ▄▀█▄▀▄████
████▄▄████▄▄▀▀▀█ ▀▄▄▄ █▄▀▄ █▀█ ▄▄▄ ▀██▀████
████ ▄▄▄▄▄ █▄▀▀▄ █ ▀█▀▄█ ██ █▀█ █▄█ █▀ ▄████
████ █ █ █▀██▀██▀▄█▄█ ▀▀█▀ █▄▀ ▄▄ ▀▀▄▄████
████ █▄▄▄█ █▀ ████▀█ █▀ ▄ ▄▀▄▀▀ ▄█▀▀▄▄▄▄▄████
████▄▄▄▄▄▄▄█▄▄██▄████▄███▄▄▄▄▄█▄▄████▄▄▄▄████
█████████████████████████████████████████████
█████████████████████████████████████████████
你好,我用的是 hax eu7,我是用了 hax 的一个 ipv4 端口来在我的 mac 电脑 termius 使用,在我搭建完 v2ray 后:bash <(curl -L https://github.com/crazypeace/v2ray_wss/raw/main/install.sh)。我在审查的过程中发现 https://lokou.lokou.cf/ 是没有伪装站的,然后我把 ipv4 和 ipv6 都添加到 cloudflare 后,我的 ipv 的 80 和 443 端口都不同,只有 ipv6 通了,我是先添加 ipv6 运行完后发现 curl https://lokou.lokou.cf/ 没有回应,但后来添加了 ipv4 才有反应,但是我仍然无法使用这个节点,那需要能用这个节点再搭建 naiveproxy 还是直接用呢?不然的话该怎么解决呢?我的 cdn 没开的
回复删除4
hax 上面还有 ipv4 吗? naive 和 v2ray 的域名要不一样。这样 v2ray 的那个可以开 CDN,naive 的这个不能开 CDN. naive 的这个也不能加 websocket.
搭
我只用了一个 ipv4:94.23.116.85 来映射 ipv6 的地址
删除你这个 94.23.116.85 是哪里来的呢? 我在 ping.pe 上测试全世界都不通呀,这个 IP 开机了吗?
删除我的 ipv4 是在 hax 那个 ipv4toipv6 拿到的
IPv4 IPv6
1 94.23.116.185:1110 [2a01:4f8:151:24e7:face:0754:d8a3:0001]:22
端口映射开了,1110 端口是好的。不过 国内访问不了。你自己看一下
https://tcp.ping.pe/94.23.116.185:1110
但是也不可能 ipv4 的 443 和 80 都不通只有 ipv6 的通,而且伪装网站完全打不开,这应该也是不可能的,会不会是我的 ipv6 和 ipv4 都用了同一个域名 lokou.lokou.cf 所导致的?
删除忘记说了,由于 hax 在 termius 运行你的脚本 command 是 are not find,所以我是用了 warp ipv4 到 ipv6 才运行的
回复删除你能把出错的日志原本发出来吗?不然,不知道发生了什么。
删除这是 caddy 日志
root@1444685184hax:~# journalctl -f -u caddy.service
-- Journal begins at Mon 2021-08-16 02:09:33 EDT. --
Nov 15 02:54:36 1444685184hax.localdomain caddy[3437]: {"level":"info","ts":1668498876.844435,"logger":"http","msg":"served key authentication","identifier":"lokou.lokou.cf","challenge":"http-01","remote":"[2600:1f16:269:da01:628b:b21a:42da:72fd]:61278","distributed":false}
Nov 15 02:54:36 1444685184hax.localdomain caddy[3437]: {"level":"info","ts":1668498876.8684793,"logger":"http","msg":"served key authentication","identifier":"lokou.lokou.cf","challenge":"http-01","remote":"[2600:1f14:804:fd01:b96f:6817:d2d0:d3b6]:13258","distributed":false}
Nov 15 02:54:36 1444685184hax.localdomain caddy[3437]: {"level":"info","ts":1668498876.9013581,"logger":"http","msg":"served key authentication","identifier":"lokou.lokou.cf","challenge":"http-01","remote":"[2600:3000:1511:200::1d]:44254","distributed":false}
Nov 15 02:54:37 1444685184hax.localdomain caddy[3437]: {"level":"info","ts":1668498877.4294505,"logger":"http.acme_client","msg":"authorization finalized","identifier":"lokou.lokou.cf","authz_status":"valid"}
Nov 15 02:54:37 1444685184hax.localdomain caddy[3437]: {"level":"info","ts":1668498877.4301648,"logger":"http.acme_client","msg":"validations succeeded; finalizing order","order":"https://acme-v02.api.letsencrypt.org/acme/order/824832727/144217110277"}
Nov 15 02:54:38 1444685184hax.localdomain caddy[3437]: {"level":"info","ts":1668498878.5559826,"logger":"http.acme_client","msg":"successfully downloaded available certificate chains","count":2,"first_url":"https://acme-v02.api.letsencrypt.org/acme/cert/04f601e16bdc375194d69b47635898b38452"}
Nov 15 02:54:38 1444685184hax.localdomain caddy[3437]: {"level":"info","ts":1668498878.5571318,"logger":"tls.obtain","msg":"certificate obtained successfully","identifier":"lokou.lokou.cf"}
Nov 15 02:54:38 1444685184hax.localdomain caddy[3437]: {"level":"info","ts":1668498878.5573256,"logger":"tls.obtain","msg":"releasing lock","identifier":"lokou.lokou.cf"}
Nov 16 02:54:34 1444685184hax.localdomain caddy[3437]: {"level":"info","ts":1668585274.3396575,"logger":"tls","msg":"cleaning storage unit","description":"FileStorage:/var/lib/caddy/.local/share/caddy"}
Nov 16 02:54:34 1444685184hax.localdomain caddy[3437]: {"level":"info","ts":1668585274.3404493,"logger":"tls","msg":"finished cleaning storage units"}
你这里面一切正常。没有看到 command are not find。
删除因为我是用了 warp 跑你的脚本的,不用的话是 command are not found
所以接下来该怎么做呢?需要重新运行脚本吗
回复删除ipv6 和 ipv4 都没有开小云朵
删除ipv480 和 443 是不通的
Canada, BC, Vancouver Shaw Connection to 94.23.116.185:80 failed
回复删除USA, CA, Fremont Hurricane FMT2 Connection to 94.23.116.185:80 failed
USA, CA, Fremont Linode Connection to 94.23.116.185:80 failed
USA, CA, San Francisco Digital Ocean Connection to 94.23.116.185:80 failed
USA, CA, Los Angeles Vultr Connection to 94.23.116.185:80 failed
USA, CA, Seattle Google Connection to 94.23.116.185:80 failed
USA, CO, Denver Cogent Connection to 94.23.116.185:80 failed
USA, TX, Dallas Softlayer Connection to 94.23.116.185:80 failed
USA, IL, Chicago Cogent Connection to 94.23.116.185:80 failed
USA, VA, Vint Hill OVH Connection to 94.23.116.185:80 failed
USA, NY, New York Telehouse/RamNode Connection to 94.23.116.185:80 failed
Canada, QC, Montreal OVH Connection to 94.23.116.185:80 failed
UK, London Cogent Connection to 94.23.116.185:80 failed
France, Paris Online.net Connection to 94.23.116.185:80 failed
Netherlands, Amsterdam Online.net Connection to 94.23.116.185:80 failed
Netherlands, Nuland WeservIT/RamNode Connection to 94.23.116.185:80 failed
Nigeria, Lagos Terrahost Connection to 94.23.116.185:80 failed
Norway, Sandefjord Terrahost Connection to 94.23.116.185:80 failed
Germany, Nuremberg Hetzner Connection to 94.23.116.185:80 failed
Italy, Milan Prometeus Connection to 94.23.116.185:80 failed
Turkey, Bursa Oneprovider Connection to 94.23.116.185:80 failed
Egypt, Cairo Binaryracks Connection to 94.23.116.185:80 failed
Cyprus, Limassol CL8 Connection to 94.23.116.185:80 failed
Israel, Tel Aviv Oneprovider Connection to 94.23.116.185:80 failed
Saudi Arabia, Riyadh Cloudsigma Connection to 94.23.116.185:80 failed
Saudi Arabia, Riyadh Buzinessware Connection to 94.23.116.185:80 failed
UAE, Dubai Bamboozle Connection to 94.23.116.185:80 failed
UAE, Dubai Buzinessware Connection to 94.23.116.185:80 failed
Iran, Tehran Green Web Connection to 94.23.116.185:80 failed
India, Mumbai Vultr Connection to 94.23.116.185:80 failed
India, Bengaluru Digital Ocean Connection to 94.23.116.185:80 failed
Singapore Digital Ocean Connection to 94.23.116.185:80 failed
Japan, Tokyo Vultr Connection to 94.23.116.185:80 failed
Australia, Sydney Vultr Connection to 94.23.116.185:80 failed
Taiwan, Taichung Google Connection to 94.23.116.185:80 failed
China, Shenzhen Aliyun Connection to 94.23.116.185:80 failed
China, Guangzhou Tencent Connection to 94.23.116.185:80 failed
China, Beijing Aliyun Connection to 94.23.116.185:80 failed
China, Beijing Tencent Connection to 94.23.116.185:80 failed
China, Quanzhou China Telecom CN2 Connection to 94.23.116.185:80 failed
China, Jiangsu China Telecom Connection to 94.23.116.185:80 failed
China, Jiangsu China Mobile Connection to 94.23.116.185:80 failed
China, Jiangsu China Unicom Connection to 94.23.116.185:80 failed
China, Hangzhou Aliyun Connection to 94.23.116.185:80 failed
China, Qingdao Aliyun Connection to 94.23.116.185:80 failed
China, Zhejiang China Telecom Connection to 94.23.116.185:80 failed
China, Shanghai Aliyun Connection to 94.23.116.185:80 failed
China, Shanghai Aliyun Connection to 94.23.116.185:80 failed
anada, BC, Vancouver Shaw Connection to 94.23.116.185:443 failed
USA, CA, Fremont Hurricane FMT2 Connection to 94.23.116.185:443 failed
USA, CA, Fremont Linode Connection to 94.23.116.185:443 failed
USA, CA, San Francisco Digital Ocean Connection to 94.23.116.185:443 failed
USA, CA, Los Angeles Vultr Connection to 94.23.116.185:443 failed
USA, CA, Seattle Google Connection to 94.23.116.185:443 failed
USA, CO, Denver Cogent Connection to 94.23.116.185:443 failed
USA, TX, Dallas Softlayer Connection to 94.23.116.185:443 failed
USA, IL, Chicago Cogent Connection to 94.23.116.185:443 failed
USA, VA, Vint Hill OVH Connection to 94.23.116.185:443 failed
USA, NY, New York Telehouse/RamNode Connection to 94.23.116.185:443 failed
Canada, QC, Montreal OVH Connection to 94.23.116.185:443 failed
UK, London Cogent Connection to 94.23.116.185:443 failed
France, Paris Online.net Connection to 94.23.116.185:443 failed
Netherlands, Amsterdam Online.net Connection to 94.23.116.185:443
94.23.116.185 你这个 IP 是哪来的? IPv4 - IPv6 映射?那你认真看一下是把哪个端口映射到哪个端口。
删除我用的是 debian11
我现在该怎么解决呢
回复删除你现在是想单独安装 naive 还是想共存? v2ray 的部分搭成功,检验使用没问题再去搭 naive.
如果是想共存,你先把
我是按照你上面的步骤来先安装 v2ray 脚本,应该是共存的
回复删除但重点是我安装的 v2ray 的 ipv4 不通和 ipv6 是通的,会不会是我把它们都放在同一个域名 lokou.lokou.cf 所导致的,还是我生成不了伪装站所导致的?
回复删除naive 和 v2ray 不要共用 域名,一个不能套 CDN, 一个可以套 CDN.
删除aaa.mydomain.com 和 bbb.mydomain.com 是不同的域名。
如果是这样的话要删除那个呢?我都用了上面的 v2ray 脚本来解析 ipv6 了,而我是用的是 termius,没有 ipv4 无法辨认机器的信息来源
回复删除如果你的 v2ray 是搭好了的。那你就给 naive 重新设置一个域名,然后再执行 naive 的脚本安装就行了。
删除但我这个 v2ray 是上不了网的,那这样可以搭 naive 吗
回复删除你单独搭 naive 用这个脚本也是可以的。
删除如果可以,那我的 ipv4 开 cdn 呢还是 ipv6 套 cdn 呢?我是用了 warp 出站的
回复删除你如果是用的 woiden,本身只有 ipv6 入站,你的域名应该解析到 ipv6 上面。
删除因为我把 hax 的 ipv4 映射地址和它的 ipv6 的地址都用在了 cloudflare 的同一个域名 lokou.lokou.cf 上,已经没有地址给 naive 了
回复删除你不应该这样设置域名解析。warp 的 ipv4 只能用于出站,不能用于入站
删除你用不同的域名分别解析到 IPv4 和 IPv6 地址上
删除那我该怎么办呢
回复删除而且我用的 termius 是在电脑上用的,我的电脑是没有 ipv6 的,那我的域名解析和 warp 也是 ipv6 入站吗
回复删除电脑没有 IPv6,想 SSH 登录看这篇 https://zelikk.blogspot.com/2022/08/ipv4ssh-hax-woiden.html
你好,我这个出了问题,该怎么办呢
root@1444685184hax:/tmp/caddy-forwardproxy-naive# mkdir -p /var/www/html
root@1444685184hax:/tmp/caddy-forwardproxy-naive# echo "hello world" > /var/www/html/index.html
root@1444685184hax:/tmp/caddy-forwardproxy-naive# service caddy start
Job for caddy.service failed because the control process exited with error code.
See "systemctl status caddy.service" and "journalctl -xe" for details.
你在手搓替换 Caddy 执行文件和 Caddyfile 之前,要先用 Caddy 官方的脚本安装一下。把相关的设置都弄好。这样我们才能只替换执行文件和配置文件。
删除我找不到 caddfile 在我的 termius 电脑
回复删除你好,我现在需要重装系统吗?究竟是哪里出错了呢
回复删除你需要先用 Caddy 官方的脚本安装一下。我更新了本教程,请再看一下。
删除请问一下,用你的一键脚本安装 naiveproxy,安装后无法使用,tcping 域名的 443 端口,显示不通,而且网站也打不开,这是什么原因呢?
回复删除系统能装的话,最好装 Debian11。有些 Debian10 apt update 更新的时候会报错。 apt update 的时候不报错,那下面这两行不需要执行。
教程:https://zelikk.blogspot.com/2021/11/racknerd-vps-v2ray-1g-1t-12g-768mb-1088.html
中间一段。
删除当然如果你
apt-get --allow-releaseinfo-change update
apt-get dist-upgrade
用一键脚本安装 v2ray 也是用不了,有点奇怪了。用的是全新的 vultr vps,系统是 Debian 10。
回复删除vultr 默认开了防火墙. 要把 80 443 端口打开。
教程
https://zelikk.blogspot.com/2022/04/setup-v2ray-websocket-tls-troubleshoot.html
ufw allow 80
ufw allow 443
你好,为什么我安装 caddy 后还是找不到 caddyfile,是不是需要自己新建 caddyflie 文件呢
回复删除你使用官方脚本安装完之后,是会自动生成 Caddyfile 的。
https://caddyserver.com/docs/install#debian-ubuntu-raspbian
你好,我在使用上面那条 bash <(curl -L https://github.com/crazypeace/v2ray_wss/raw/main/install.sh) 后无法启动 caddy,
root@1444685184woiden:~# service caddy status
● caddy.service - Caddy
Loaded: loaded (/lib/systemd/system/caddy.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2022-11-25 18:00:37 PST; 1min 10s ago
Docs: https://caddyserver.com/docs/
Process: 3746 ExecStart=/usr/bin/caddy run --environ --config /etc/caddy/Caddyfile (code=exited, status=1/FAILURE)
Main PID: 3746 (code=exited, status=1/FAILURE)
Status: "loading new config: http app module: start: listening on :80: listen tcp :80: bind: address already in use"
Nov 25 18:00:37 1444685184woiden.localdomain caddy[3746]: {"level":"info","ts":1669428037.3438597,"logger":"http","msg":"server is l>
Nov 25 18:00:37 1444685184woiden.localdomain caddy[3746]: {"level":"info","ts":1669428037.3439593,"logger":"http","msg":"enabling au>
Nov 25 18:00:37 1444685184woiden.localdomain caddy[3746]: {"level":"info","ts":1669428037.3451614,"logger":"http","msg":"enabling HT>
Nov 25 18:00:37 1444685184woiden.localdomain caddy[3746]: {"level":"info","ts":1669428037.3453958,"logger":"http.log","msg":"server >
Nov 25 18:00:37 1444685184woiden.localdomain caddy[3746]: {"level":"info","ts":1669428037.3459947,"logger":"tls.cache.maintenance",">
Nov 25 18:00:37 1444685184woiden.localdomain caddy[3746]: {"level":"info","ts":1669428037.3460944,"logger":"tls.cache.maintenance",">
Nov 25 18:00:37 1444685184woiden.localdomain caddy[3746]: Error: loading initial config: loading new config: http app module: start:>
Nov 25 18:00:37 1444685184woiden.localdomain systemd[1]: caddy.service: Main process exited, code=exited, status=1/FAILURE
Nov 25 18:00:37 1444685184woiden.localdomain systemd[1]: caddy.service: Failed with result 'exit-code'.
Nov 25 18:00:37 1444685184woiden.localdomain systemd[1]: Failed to start Caddy.
我在排错中还发现 443 没有反应
root@1444685184woiden:~# lsof -i:80
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
apache2 247 root 4u IPv6 2303827524 0t0 TCP *:http (LISTEN)
apache2 248 www-data 4u IPv6 2303827524 0t0 TCP *:http (LISTEN)
root@1444685184woiden:~# lsof -i:443
root@1444685184woiden:~# lsof -i:443
是啊, 80 端口被 apache2 占用了,所以 caddy 没跑起来。所以 443 端口没人用。
删除root@1444685184woiden:~# journalctl -f -u caddy.service
-- Journal begins at Wed 2021-10-06 04:42:28 PDT. --
Nov 25 18:00:37 1444685184woiden.localdomain caddy[3746]: {"level":"info","ts":1669428037.3438597,"logger":"http","msg":"server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS","server_name":"srv0","https_port":443}
Nov 25 18:00:37 1444685184woiden.localdomain caddy[3746]: {"level":"info","ts":1669428037.3439593,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}
Nov 25 18:00:37 1444685184woiden.localdomain caddy[3746]: {"level":"info","ts":1669428037.3451614,"logger":"http","msg":"enabling HTTP/3 listener","addr":":443"}
Nov 25 18:00:37 1444685184woiden.localdomain caddy[3746]: {"level":"info","ts":1669428037.3453958,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
Nov 25 18:00:37 1444685184woiden.localdomain caddy[3746]: {"level":"info","ts":1669428037.3459947,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc000291260"}
Nov 25 18:00:37 1444685184woiden.localdomain caddy[3746]: {"level":"info","ts":1669428037.3460944,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":"0xc000291260"}
Nov 25 18:00:37 1444685184woiden.localdomain caddy[3746]: Error: loading initial config: loading new config: http app module: start: listening on :80: listen tcp :80: bind: address already in use
Nov 25 18:00:37 1444685184woiden.localdomain systemd[1]: caddy.service: Main process exited, code=exited, status=1/FAILURE
Nov 25 18:00:37 1444685184woiden.localdomain systemd[1]: caddy.service: Failed with result 'exit-code'.
Nov 25 18:00:37 1444685184woiden.localdomain systemd[1]: Failed to start Caddy.
Error: loading initial config: loading new config: http app module: start: listening on :80: listen tcp :80: bind: address already in use
端口被人占用了。你 lsof -i:80 看是谁在用。
删除80
这是我的 80 情况
root@1444685184woiden:~# lsof -i:80
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
apache2 247 root 4u IPv6 2303827524 0t0 TCP *:http (LISTEN)
apache2 248 www-data 4u IPv6 2303827524 0t0 TCP *:http (LISTEN)
说明 apache2 占用了 80 端口
删除這是我的 caddy
path
回复删除root@1444685184woiden:~# cat /etc/caddy/Caddyfile
lokou.lokou.cf
{
tls Y3JhenlwZWFjZQ@gmail.com
encode gzip
# 多用戶多
# import Caddyfile.multiuser
handle_path /8f660521d320 {
reverse_proxy localhost:59440
}
handle {
reverse_proxy https://zelikk.blogspot.com {
trusted_proxies 0.0.0.0/0
header_up Host {upstream_hostport}
}
}
}
root@1444685184woiden:~#
我不清楚为什么用这条指令 caddy 运行不了
回复删除会不会是我用了 warp input ipv4 进行操作所导致的呢
回复删除你好,我在检查的时候发现 ipv6 的 80 和 443 是通的,但是我的 ipv4 的 443 和 80 是 ping 不通的,我现在仍然用不了上面那条 v2ray:bash <(curl -L https://github.com/crazypeace/v2ray_wss/raw/main/install.sh) 来上网
回复删除你的 ipv4 并不是独享的 你从申请 IPv4 的地方就能看出来,也能从 woiden VPS 的名称上看出来 SharedIPv4+DedicatedIPv6
所以你的 ipv4 上面的 80 和 443 你用不了。
删除这是我的 ipv6
2a01:4f8:202:1002:1111:1111:3152:0001
这是我的公共 IPv4 148.251.50.26
我是用我的公共 IPv4 148.251.50.26 在我的没有 ipv6 的电脑来连接 ssh termius 来搭建 naiveproxy 的
回复删除是的。公共 IPv4 上面有一个端口是让你用来 SSH 登录你的 vps 的,换句话,还有好多其它端口是让其它人去 SSH 登录他们的 woiden VPS 的。
删除你好,我的 caddy 说有损毁,打不开修改
回复删除也许你 wget 下载的时候出了问题所以压缩包有问题?
删除你可以把之前下载的压缩包删除。再下载试试。
这是我的安装指令 root@1444685184woiden:/tmp# tar -xf caddy-forwardproxy-naive.tar.xz
root@1444685184woiden:/tmp# cd caddy-forwardproxy-naive
root@1444685184woiden:/tmp/caddy-forwardproxy-naive# service caddy stop
root@1444685184woiden:/tmp/caddy-forwardproxy-naive# cp caddy /usr/bin/
root@1444685184woiden:/tmp/caddy-forwardproxy-naive# root@1444685184woiden:~# cd /tmp
root@1444685184woiden:/tmp# wget https://github.com/klzgrad/forwardproxy/releases/download/caddy2-naive-20221007/caddy-forwardproxy-naive.tar.xz
该怎么办呢
回复删除那我该怎么删除呢
回复删除你需要 google "linux 删除 文件"
删除我是装了 v2ray 能用后再安装 naive 和 caddy 的
回复删除这是我的安装 root@1444685184woiden:~# curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
sudo: unable to resolve host 1444685184woiden.localdomain: Name or service not known
File '/usr/share/keyrings/caddy-stable-archive-keyring.gpg' exists. Overwrite? (y/N) y
root@1444685184woiden:~# curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list
sudo: unable to resolve host 1444685184woiden.localdomain: Name or service not known
# Source: Caddy
# Site: https://github.com/caddyserver/caddy
# Repository: Caddy / stable
# Description: Fast, multi-platform web server with automatic HTTPS
接下来是这个 root@1444685184woiden:~# sudo apt install caddy
sudo: unable to resolve host 1444685184woiden.localdomain: Name or service not known
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
caddy is already the newest version (2.6.2).
0 upgraded, 0 newly installed, 0 to remove and 105 not upgraded.
然后是这个 root@1444685184woiden:/tmp# tar -xf caddy-forwardproxy-naive.tar.xz
root@1444685184woiden:/tmp# cd caddy-forwardproxy-naive
root@1444685184woiden:/tmp/caddy-forwardproxy-naive# service caddy stop
root@1444685184woiden:/tmp/caddy-forwardproxy-naive# cp caddy /usr/bin/
还有这个 root@1444685184woiden:~# cd /tmp
root@1444685184woiden:/tmp# wget https://github.com/klzgrad/forwardproxy/releases/download/caddy2-naive-20221007/caddy-forwardproxy-naive.tar.xz
最後我用這個來找 caddyfile 的:
回复删除root@1444685184woiden:/tmp/caddy-forwardproxy-naive# find / -name "Caddyfile"
/etc/caddy/Caddyfile
find: '/proc/1/map_files': Operation not permitted
find: '/proc/2/map_files': Operation not permitted
find: '/proc/3/map_files': Operation not permitted
root@1444685184woiden:/tmp/caddy-forwardproxy-naive#
我的 Caddyfile 仍然下载不了。不清楚这是怎么回事
回复删除wget https://github.com/klzgrad/forwardproxy/releases/download/caddy2-naive-20221007/caddy-forwardproxy-naive.tar.xz
这个是下载压缩包
tar -xf caddy-forwardproxy-naive.tar.xz
这个是解开压缩包
删除我在这个 /tmp/caddy-forwardproxy-naive 找的 caddyfile 正确吗
回复删除这一句是你找到的 Caddyfile
/etc/caddy/Caddyfile
你好,我这个 caddy 启动出问题
Job for caddy.service failed because the control process exited with error code.
See "systemctl status caddy.service" and "journalctl -xe" for details.
root@1444685184woiden:~# service caddy start
Job for caddy.service failed because the control process exited with error code.
See "systemctl status caddy.service" and "journalctl -xe" for details.
我该怎么做呢
回复删除但是我只有两个域名,一个是用了 v2ray,另一个用来解析 naive 的域名,难道还需要制作第三个吗
回复删除我要删掉是吧后面的删掉吗
path
# _naive_config_begin_
{
order forward_proxy before file_server
}
:443, naive.lokou.cf:443 {
tls e16d9cb045d7@gmail.com
forward_proxy {
basic_auth 24da4add546bbd4d b462c3374fbc22b3
hide_ip
hide_via
probe_resistance
}
file_server {
root /var/www/xkcdpw-html
}
}
# _naive_config_end_
lokou.lokou.cf
{
tls Y3JhenlwZWFjZQ@gmail.com
encode gzip
# 多用户 多
# import Caddyfile.multiuser
handle_path /3d9e3e0c54c5 {
reverse_proxy localhost:41431
}
handle {
reverse_proxy https://zelikk.blogspot.com {
trusted_proxies 0.0.0.0/0
header_up Host {upstream_hostport}
}
}
}
你把这两个之间的部分删掉
再后面是给 v2ray 用的。
删除# _naive_config_begin_
# _naive_config_end_
你自己阅读一下配置文件,看看里面写的什么域名。
你好,我的 caddy 似乎启动成功了,怎么用 naiveproxy 这个节点呢,我只有 v2ray 的脚本文本
回复删除你需要 google "naiveproxy 节点如何使用" repo 的 readme 里面写了基本的用法
https://github.com/klzgrad/naiveproxy#client-setup
作者的
下面描述了 forwardproxy 設置的原始分支。
他这个需要设置吗在我运行完 caddyfile 之后
回复删除建造:
go install github.com/caddyserver/xcaddy/cmd/xcaddy@latest
~/go/bin/xcaddy build --with github.com/caddyserver/forwardproxy@caddy2=github.com/klzgrad/forwardproxy@naive
你说的那是搭服务端。
Client setup
你需要的是这部分
Run ./naive with the following config.json to get a SOCKS5 proxy at local port 1080.
{
"listen": "socks://127.0.0.1:1080",
"proxy": "https://user:pass@example.com"
}
Or quic://user:pass@example.com, if it works better. See also parameter usage and performance tuning.
此评论已被作者删除。
回复删除Client setup
这个是服务端吗?写在哪个文件呢?
回复删除Run ./naive with the following config.json to get a SOCKS5 proxy at local port 1080.
{
"listen": "socks://127.0.0.1:1080",
"proxy": "https://user:pass@example.com"
}
Or quic://user:pass@example.com, if it works better. See also parameter usage and performance tuning.
然后我发现启动 caddy 后在 google 输入我的 naive 域名是没有反应的,是 caddy 运行不成功吗
回复删除我用的的是 macbook m 系列的,只能用小火箭,v2rayu 没有 naiveproxy 协议
回复删除如果用的是小火箭,那这个 Run ./naive with the following config.json to get a SOCKS5 proxy at local port 1080.
放在哪里
回复删除{
"listen": "socks://127.0.0.1:1080",
"proxy": "https://user:pass@example.com"
}
Or quic://user:pass@example.com, if it works better. See also parameter usage and performance tuning.
你自己 google 一下 shadowrocket 如何使用 naiveproxy
你好,我下载的客户端文件没法用在 v2yaryu,每次都显示 vmess adress out,小火箭也显示超时,这个到底该怎么用呢
回复删除这是你的 vmess 节点没搭好吧。
删除而且我运行的 sudo setcap cap_net_bind_service=+ep ./caddy 这条指令显示 error ./caddy,该怎么办呢
回复删除./caddy start
我的脚本里没有这一句吧。你在哪里看到的,要问那个作者啊。
删除不对啊我的 vmess 是可以正常用的,不太可能影响 naiveproxy 的 config。json 的吧?
回复删除sudo setcap cap_net_bind_service=+ep ./caddy 这条指令是上面发给我的那个 github 的指令,那个好像是服务端的指令
https://github.com/klzgrad/naiveproxy#client-setup
./caddy start
不过我用的小火箭还需要用客户端那个 config。json 的文件吗?我是下载 linux 的还是 macos 的文件呢
回复删除我 google 的 shadowrocket 如何使用 naiveproxy 里面的博主都用他们的二维码来扫码,但是我用你的脚本好像是没有二维码的,那我该怎么搭建 shadowrocket 呢
回复删除"小火箭是可以连接上 naiveproxy 服务器,type 里选择 h2 或者 https 就可以" - 这是我搜索得到的答案 https://github.com/klzgrad/naiveproxy/issues/39
你把 shadowrocket 打开, 点右上角 + 号,再点击 “类型” 你应该能看到 HTTPS, HTTP2 下面写了 naiveproxy 的小字。然后你只需要填写 地址,端口,用户,密码 这四项就可以了。
删除而且我在上面测试 “测试一下你的 VLESS/Vmess 和 NaiveProxy” 的时候发现 naiveproxy 的域名是没有任何伪装网站,只是 google 说我搜索的字体有错别字
回复删除配置文件里这一段是伪装站
如果你没有在 VPS 的 /var/www/html 这个位置放一个 index.html 那么访问 https:// 你的 naive 的域名: 端口 就会什么都没有
删除file_server {
root /var/www/html
}
我查过是有这个文件的,/var/www/html 这个位置放一个 index.html,因为是按上面操作 mkdir -p /var/www/html
来进行的,但就是 google 域名报错
回复删除echo "hello world" > /var/www/html/index.html
用你的浏览器访问 https:// 你的域名: 端口
删除就像我访问 https://npp.tzzhu.gq:14443 一样
而且我加载的 naiveproxy 在小火箭中测试超时,用不了,该怎么办呢
回复删除你先测试 https:// 你的域名: 端口 能出来伪装网页再说。只有这样才说明你的服务器搭好了。 naive 节点搭好了没有。排除掉你自己网络的原因。
删除同样的,你也可以通过 https://www.uptrends.com/tools/uptime 这个第三方来测试你的
你好,我通过 https://www.uptrends.com/tools/uptime 这个第三方来测试你的 naive 节点,全都是红色,写着 DNS LOOKUP ERROR
你测试的 https://npp.tzzhu.gq:14443 这个吗?
删除我的意思是仅输入 https://npp.tzzhu.gq:14443 没有其它部分
删除不是,我是输入我的域名·和 caddyfile 的端口:443
但是我完全没有效果
回复删除你提到的错误信息 “DNS LOOKUP ERROR” 说明域名解析有问题。建议你去查一下。你可以用 ping.pe 第三方检查你的域名解析的结果。
删除这是我查到的结果
Query: ping naive.lokou.cf, interval: 5s, dense mode: no
回复删除Probing 2a01:4f8:202:1002:1111:1111:3152:1 – RIPENCC /32 AS24940 HETZNER – Germany [hosting] MAP
Geo ISP Loss Sent Last Avg Best Worst StDev MTR Chart
USA, CA, Fremont Linode 0% 4 160.2 160.71 159.93 162.56 1.07 ...
USA, CA, San Francisco Digital Ocean 0% 4 165.45 165.46 165.08 165.76 0.25 ...
USA, CA, Los Angeles Vultr 0% 4 148.46 148.59 148.13 149.08 0.35 ...
USA, IL, Chicago Cogent 0% 4 117.89 117.34 116.73 117.97 0.59 ...
USA, NY, New York Telehouse/RamNode 0% 4 88.79 89.25 88.79 89.61 0.3 ...
Canada, QC, Montreal OVH 0% 4 100.71 100.33 100.15 100.71 0.22 ...
UK, London Cogent 0% 4 25.45 24.82 24.24 25.45 0.47 ...
Netherlands, Amsterdam Online.net 0% 4 19.28 19.29 18.87 19.74 0.31 ...
Netherlands, Nuland WeservIT/RamNode 0% 4 14.03 14.15 13.94 14.66 0.3 ...
Norway, Sandefjord Terrahost 0% 4 34.31 34 33.76 34.31 0.22 ...
Germany, Nuremberg Hetzner 0% 4 5.73 4.22 3.29 5.73 0.96 ...
Italy, Milan Prometeus 0% 4 20.85 20.72 20.59 20.85 0.1 ...
India, Mumbai Vultr 0% 4 118.71 120.31 118.71 121.96 1.2 ...
India, Bengaluru Digital Ocean 0% 4 263.59 263.82 263.43 264.28 0.33 ...
Singapore Digital Ocean 0% 4 165.52 166.53 164.92 168.32 1.37 ...
Japan, Tokyo Vultr 0% 4 250.34 250.9 250.34 251.26 0.34 ...
Australia, Sydney Vultr 0% 4 274.07 274.93 273.99 277.24 1.34 ...
你确认这个解析出来的 IP 地址是否正确。 是不是通的。
删除如果是正确的,那么你接下来可以使用 ping.pe 检测你的 域名:端口 tcp
似乎这个是有一半是运行的
回复删除域名好像可以,我也 ping 过了,有延迟
回复删除你好,我测过我的域名 naive.lokou.cf 的 443 和 80 都是通的
回复删除Query: tcp naive.lokou.cf:80 [2a01:4f8:202:1002:1111:1111:3152:1]
Location ISP TCP port check result
USA, CA, Fremont Linode Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
USA, CA, San Francisco Digital Ocean Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
USA, CA, Los Angeles Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
USA, CO, Denver Cogent Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 failed
USA, IL, Chicago Cogent Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
USA, NY, New York Telehouse/RamNode Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
Canada, QC, Montreal OVH Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
UK, London Cogent Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
Netherlands, Amsterdam Online.net Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
Netherlands, Nuland WeservIT/RamNode Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
Norway, Sandefjord Terrahost Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
Germany, Nuremberg Hetzner Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
Italy, Milan Prometeus Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
India, Mumbai Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
India, Bengaluru Digital Ocean Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
Singapore Digital Ocean Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
Japan, Tokyo Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
Australia, Sydney Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:80 successful
Query: tcp naive.lokou.cf:443 [2a01:4f8:202:1002:1111:1111:3152:1]
Location ISP TCP port check result
USA, CA, Fremont Linode Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
USA, CA, San Francisco Digital Ocean Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
USA, CA, Los Angeles Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
USA, CO, Denver Cogent Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
USA, IL, Chicago Cogent Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
USA, NY, New York Telehouse/RamNode Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
Canada, QC, Montreal OVH Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
UK, London Cogent Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
Netherlands, Amsterdam Online.net Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
Netherlands, Nuland WeservIT/RamNode Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
Norway, Sandefjord Terrahost Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
Germany, Nuremberg Hetzner Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
Italy, Milan Prometeus Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
India, Mumbai Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
India, Bengaluru Digital Ocean Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
Singapore Digital Ocean Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
Japan, Tokyo Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
Australia, Sydney Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:1]:443 successful
China-based test nodes are disabled due to DDoS attacks. Will be re-enabled once attacks stop.
你在你自己的 VPS 上访问你的 https:// 域名:端口
curl -L htttps:// 域名:端口
删除好像我的域名端口都是通的
回复删除那究竟是什么问题呢
回复删除不行,这个有问题 root@1444685184woiden:~# curl -L htttps://naive.lokou.cf
curl: (1) Protocol "htttps" not supported or disabled in libcurl
curl -L https://naive.lokou.cf
没有 3 个 t
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
你好,他好像一直在运行,没有显示
回复删除permitted by applicable law.
Last login: Mon Dec 5 21:57:35 2022 from 111.65.48.160
root@1444685184woiden:~# curl -L https://naive.lokou.cf
root@1444685184woiden:~# curl -L https://naive.lokou.cf
回复删除curl: (6) Could not resolve host: naive.lokou.cf
root@1444685184woiden:~#
这个错误是说域名不能解析。我不知道你把网络环境配置成什么样子了。 hello world 的结果的,说明搭好了呀。
我测试你的域名是可以出来
~# curl -L https://naive.lokou.cf
hello world
会不会是我的 v2ray 和 naiveproxy 并存,然后用了 v2ray 后不能用 naiveproxy 了?
回复删除又或者说 naiveproxy 只适合 ipv6 而不适合 ipv4 的?
回复删除naive 不能过 cdn, 你有 ipv6 环境吗?能 tcp 连通 woiden 的 ipv6 地址吗?
删除还是说 caddy 需要另一条指令启动吗,因为我是用那个 service caddy start
然后我配置的内容是根据 etc/caddy/caddyfile 这个内容去配置的
回复删除我只有 v2ray 的域名过 cdn,naive 的没开小云朵,只是 dns 解析
回复删除我这个 woiden ipv6 的 443 和 80 是显示无效代码
[ 2a01:4f8:202:1002:1111:1111:3152:0001 ]:443
! Invalid command: [
Query format:
QUERY: ping IP
EXAMPLES: ping 1.2.3.4
ping example.com
ping6 google.com
DESCRIPTION: Full ping and mtr test. Use ping6 alias to force ipv6.
QUERY: mtr IP
EXAMPLES: mtr 1.2.3.4
mtr example.com
mtr6 google.com
DESCRIPTION: Just the mtr test. Use mtr6 alias to force ipv6.
QUERY: chart IP
EXAMPLES: chart 1.2.3.4
chart example.com
chart6 example.com
DESCRIPTION: Ping with less text, more charting. Use chart6 alias to force ipv6.
QUERY: tcp IP:PORT
EXAMPLES: tcp 1.2.3.4:80
tcp example.com:443
tcp6 google.com:443
DESCRIPTION: TCP port accessibility test. Make sure something is LISTENING for incoming connections on that port on target machine. PORT can be omitted, then default 80 will be used. Use tcp6 alias to force ipv6.
QUERY: port IP:PORT
EXAMPLES: port 1.2.3.4:80
port example.com:443
DESCRIPTION: Alias of tcp command.
QUERY: dig HOST:TYPE:NAMESERVER
EXAMPLES: dig example.com:A:8.8.8.8
dig 1.2.3.4:PTR:1.0.0.1
dig example.com:AAAA
dig example.com
DESCRIPTION: DNS record lookup. Supported TYPEs: A, AAAA, CNAME, TXT, MX, NS, PTR. TYPE can be omitted, then default A will be used. NAMESERVER can be omitted, then default 8.8.8.8 will be used.
QUERY: set variable=value
EXAMPLES: set interval=4 (default:5)
set dense_mode=1 (default:0)
DESCRIPTION: Configure ping.pe default values like Interval (in seconds) and Dense mode (0/1).
In some cases COMMAND can be omitted and ping.pe will figure it out automatically.
For example, when a query contains just one IP or DOMAIN, then omitted 'ping' command will be implied. If there is a single semicolon in the query, 'tcp' command will be implied etc.
Additionally, you can use domain name to indicate COMMAND:
ping.pe/SUBJECT – assumed command: ping
ping6.ping.pe/SUBJECT – assumed command: ping6
chart.ping.pe/SUBJECT – assumed command: chart
chart6.ping.pe/SUBJECT – assumed command: chart6
tcp.ping.pe/SUBJECT – assumed command: tcp
tcp6.ping.pe/SUBJECT – assumed command: tcp6
port.ping.pe/SUBJECT – assumed command: tcp
dig.ping.pe/SUBJECT – assumed command: dig
或者你那边也测下,它的代码太多我发布了
回复删除我没有能力连 woiden 的 ipv6
发布了也被删
回复删除你可以上 github 发 issue 那里不夹代码。
删除我这里查的时候显示命令无效,查不到
回复删除不太懂哪个 github 呢?是自己的吗
回复删除https://github.com/crazypeace/naive
这里就是这个脚本的 github 项目 issue 你可以提问题,贴代码不会被夹。
删除里面有个
要不我把 caddfile 的配置文件发给你,然后用小火箭看看那边能不能用?
回复删除你发给我也没用。我不能 ipv6 访问 woiden 的 ipv6 地址。
删除我已经传输上去了
回复删除因为我的 v2ray 是用 warp 出站的,不知道 naive 的并存是否也可以用 warp 出站
回复删除你把 naive 后面接上 v2ray 就肯定走 v2ray 的出站出去了。
https://zelikk.blogspot.com/2022/11/naiveproxy-socks5-v2ray-cn-ip-domain-route.html
你好,尝试很多次,似乎都是连接失败
回复删除你好,我的 google 已经成功连接,但是小火箭仍然显示超时并且说配置无效
回复删除google 能用就说明翻成功了呀。翻墙客户端的测试结果只能信一半。
删除你好,两天过去了,仍然用不了这个节点,该怎么办呢
回复删除