自定义端口NaiveProxy与Caddy V2前置的VLESS/Vmess V2Ray共存 可开CDN

* 推荐使用Xshell的撰写窗格,这样多行命令可以写到撰写窗格里面执行。

Xshell 撰写窗格


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-https
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list
sudo apt update
sudo 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的配置部分

在Caddyfile的顶部添加下面这一段

{
  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
  }
}

也可以在撰写窗格里执行

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

测试一下你的VLESS/Vmess 和 NaiveProxy 应该都可以正常使用。


3. [可选项] 自定义NaiveProxy端口

编辑Caddfile, 把 “:443”改成你想要的端口号“:自定义端口”;并在域名后面加上“:自定义端口

像下面这样


重启NaiveProxy

service caddy restart

检查一下工作正常


 4. [可选项] NaiveProxy屏蔽墙内流量

NaiveProxy没有路由模块,需要用“外部”方案处理墙内流量问题

利用V2Ray的路由模块

DNS解析屏蔽墙内域名


========

正常操作日志

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
----------------------------------------------------------------
如果你的小鸡是双栈(同时有IPv4IPv6IP),请选择你把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==
以下两个二维码完全一样的内容
█████████████████████████████████████████████
█████████████████████████████████████████████
████ ▄▄▄▄▄ ▀▄█▀  ▀▀▄  ▀▄▀▀▀  ▀▀█ ▄▄▄▄▄ ████
████    █▄   ▀▀▄▄ ▀▀█ ▀▀▀ █▄█    ████
████ █▄▄▄█ ▀█▀█  █▄▄   ▀█▀▄▄ ▄█ █▄▄▄█ ████
████▄▄▄▄▄▄▄█ ▀▄█ █▄ █▄▀▄▀▄█ █▄▄▄▄▄▄▄████
████▄▄█▄▀▀▄ ▀▀ ▀██▀ ▀█▄▀▀▀▀▀▀ ▀▀ ▄▄ ▀████
████▄  ▄▄▄█▀▀███▀▀▄██ ▀▀▀█ ▀▀██▄ ▀▄▀ ████
████▄▄▀▄█ ▄▄  ▀▀ ██▀▄▄▀  ▀▀██▄ ▀█  ▀▄███ ████
████▄▀██▄█▄█ ▀▄█ ▀▀▄    ██ ▀▄▀ ▀▄████
█████▀▄█▄▄▄▄ ██▄█▄▄ ▀█▄▄ ▀█▀▄▀ ▀▄▄▄ ████
██████▀▄▀▄▄▄▄▀▄▀█ ▀▀ ▀▀ ▀██▄▄▀▀ ▀▀ ▄████
████ █▄█  ▄▄▄█▄  ▀▄▀ ███▄ ▀█ ▀▄▄ ▀▄█▄█ ████
█████▀▄█▄▀▄███▄   ▄▄▀▄▄▄   ▀██▀▄▄ █▄█▄▄████
████▄  ▀▄█▄██    ▀▀█▀   ▀▀▀▄▄▄▀▄▄ ████
████▄ ▀▀▄▄▄▀▄▀ █▄▄▀▀  ▀▀  ██▀▀ ▀█▄▀▄████
████▄▄████▄▄▀▀▀█  ▀▄▄▄ █▄▀▄  ▀█ ▄▄▄ ▀██▀████
████ ▄▄▄▄▄ █▄▀▀▄ ▀█▀▄█  ██ ▀█ █▄█ ▄████
████    ▀██▀██▀▄█▄█ ▀▀█▀ █▄ ▄▄  ▀▀▄▄████
████ █▄▄▄█ ████▀█ ▀▄▀▀ ▄█▀▀▄▄▄▄▄████
████▄▄▄▄▄▄▄█▄▄██▄████▄███▄▄▄▄▄█▄▄████▄▄▄▄████
█████████████████████████████████████████████
█████████████████████████████████████████████

---------- END -------------
以上节点信息保存在 ~/_naive_url_

----------------------------------------------------------------
END
root@391932510hax:~#

评论

  1. 你好,我用的是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
    4的80和443端口都不同,只有ipv6通了,我是先添加ipv6运行完后发现curl https://lokou.lokou.cf/没有回应,但后来添加了ipv4才有反应,但是我仍然无法使用这个节点,那需要能用这个节点再搭建naiveproxy还是直接用呢?不然的话该怎么解决呢?我的cdn没开的

    回复删除
    回复
    1. hax 上面还有 ipv4吗?
      搭naive和v2ray的域名要不一样。这样v2ray的那个可以开CDN,naive的这个不能开CDN. naive的这个也不能加websocket.

      删除
    2. 我只用了一个ipv4:94.23.116.85来映射ipv6的地址

      删除
    3. 你这个94.23.116.85 是哪里来的呢? 我在ping.pe上测试全世界都不通呀,这个IP开机了吗?

      删除
    4. 我的ipv4是在hax那个ipv4toipv6拿到的
      IPv4 IPv6
      1 94.23.116.185:1110 [2a01:4f8:151:24e7:face:0754:d8a3:0001]:22

      删除
    5. 端口映射开了,1110端口是好的。不过 国内访问不了。你自己看一下
      https://tcp.ping.pe/94.23.116.185:1110

      删除
    6. 但是也不可能ipv4的443和80都不通只有ipv6的通,而且伪装网站完全打不开,这应该也是不可能的,会不会是我的ipv6和ipv4都用了同一个域名lokou.lokou.cf所导致的?

      删除
  2. 忘记说了,由于hax在termius运行你的脚本command是are not find,所以我是用了warp ipv4到ipv6才运行的

    回复删除
    回复
    1. 你能把出错的日志原本发出来吗?不然,不知道发生了什么。

      删除
    2. 这是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"}

      删除
    3. 你这里面一切正常。没有看到 command are not find。

      删除
    4. 因为我是用了warp跑你的脚本的,不用的话是command are not found

      删除
  3. 所以接下来该怎么做呢?需要重新运行脚本吗

    回复删除
  4. 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

    回复删除
    回复
    1. 94.23.116.185 你这个IP是哪来的? IPv4 - IPv6 映射?那你认真看一下是把哪个端口映射到哪个端口。

      删除
  5. 回复
    1. 你现在是想单独安装naive 还是想共存?
      如果是想共存,你先把v2ray的部分搭成功,检验使用没问题再去搭naive.

      删除
  6. 我是按照你上面的步骤来先安装v2ray脚本,应该是共存的

    回复删除
  7. 但重点是我安装的v2ray的ipv4不通和ipv6是通的,会不会是我把它们都放在同一个域名lokou.lokou.cf所导致的,还是我生成不了伪装站所导致的?

    回复删除
    回复
    1. naive 和 v2ray 不要共用 域名,一个不能套CDN, 一个可以套CDN.
      aaa.mydomain.com 和 bbb.mydomain.com 是不同的域名。

      删除
  8. 如果是这样的话要删除那个呢?我都用了上面的v2ray脚本来解析ipv6了,而我是用的是termius,没有ipv4无法辨认机器的信息来源

    回复删除
    回复
    1. 如果你的 v2ray是搭好了的。那你就给naive重新设置一个域名,然后再执行naive的脚本安装就行了。

      删除
  9. 但我这个v2ray是上不了网的,那这样可以搭naive吗

    回复删除
  10. 如果可以,那我的ipv4开cdn呢还是ipv6套cdn呢?我是用了warp出站的

    回复删除
    回复
    1. 你如果是用的woiden,本身只有ipv6入站,你的域名应该解析到ipv6上面。

      删除
  11. 因为我把hax的ipv4映射地址和它的ipv6的地址都用在了cloudflare的同一个域名lokou.lokou.cf上,已经没有地址给naive了

    回复删除
    回复
    1. 你不应该这样设置域名解析。warp的ipv4只能用于出站,不能用于入站

      删除
    2. 你用不同的域名分别解析到 IPv4 和IPv6地址上

      删除
  12. 而且我用的termius是在电脑上用的,我的电脑是没有ipv6的,那我的域名解析和warp也是ipv6入站吗

    回复删除
    回复
    1. 电脑没有IPv6,想SSH登录看这篇 https://zelikk.blogspot.com/2022/08/ipv4ssh-hax-woiden.html

      删除
  13. 你好,我这个出了问题,该怎么办呢
    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.

    回复删除
    回复
    1. 你在手搓替换Caddy执行文件和Caddyfile之前,要先用Caddy官方的脚本安装一下。把相关的设置都弄好。这样我们才能只替换执行文件和配置文件。

      删除
  14. 我找不到caddfile在我的termius电脑

    回复删除
  15. 你好,我现在需要重装系统吗?究竟是哪里出错了呢

    回复删除
    回复
    1. 你需要先用Caddy官方的脚本安装一下。我更新了本教程,请再看一下。

      删除
  16. 请问一下,用你的一键脚本安装naiveproxy,安装后无法使用,tcping 域名的443端口,显示不通,而且网站也打不开,这是什么原因呢?

    回复删除
    回复
    1. 系统能装的话,最好装Debian11。有些Debian10 apt update 更新的时候会报错。
      当然如果你apt update的时候不报错,那下面这两行不需要执行。
      apt-get --allow-releaseinfo-change update
      apt-get dist-upgrade
      教程:https://zelikk.blogspot.com/2021/11/racknerd-vps-v2ray-1g-1t-12g-768mb-1088.html
      中间一段。

      删除
  17. 用一键脚本安装v2ray也是用不了,有点奇怪了。用的是全新的vultr vps,系统是Debian 10。

    回复删除
    回复
    1. vultr 默认开了防火墙. 要把80 443端口打开。
      ufw allow 80
      ufw allow 443
      教程
      https://zelikk.blogspot.com/2022/04/setup-v2ray-websocket-tls-troubleshoot.html

      删除
  18. 你好,为什么我安装caddy后还是找不到caddyfile,是不是需要自己新建caddyflie文件呢

    回复删除
    回复
    1. 你使用官方脚本安装完之后,是会自动生成Caddyfile的。
      https://caddyserver.com/docs/install#debian-ubuntu-raspbian

      删除
  19. 你好,我在使用上面那条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.

    回复删除
  20. 我在排错中还发现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

    回复删除
    回复
    1. 是啊, 80端口被apache2占用了,所以caddy没跑起来。所以443端口没人用。

      删除
  21. 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.

    回复删除
    回复
    1. Error: loading initial config: loading new config: http app module: start: listening on :80: listen tcp :80: bind: address already in use

      80端口被人占用了。你 lsof -i:80 看是谁在用。

      删除
    2. 这是我的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)

      删除
  22. 這是我的caddy
    root@1444685184woiden:~# cat /etc/caddy/Caddyfile
    lokou.lokou.cf
    {
    tls Y3JhenlwZWFjZQ@gmail.com
    encode gzip

    # 多用戶多path
    # 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:~#

    回复删除
  23. 我不清楚为什么用这条指令caddy运行不了

    回复删除
  24. 会不会是我用了warp input ipv4进行操作所导致的呢

    回复删除
  25. 你好,我在检查的时候发现ipv6的80和443是通的,但是我的ipv4的443和80是ping不通的,我现在仍然用不了上面那条v2ray:bash <(curl -L https://github.com/crazypeace/v2ray_wss/raw/main/install.sh)来上网

    回复删除
    回复
    1. 你的ipv4并不是独享的 你从申请 IPv4的地方就能看出来,也能从woiden VPS的名称上看出来 SharedIPv4+DedicatedIPv6
      所以你的ipv4上面的80和443你用不了。

      删除
  26. 这是我的ipv6
    2a01:4f8:202:1002:1111:1111:3152:0001

    回复删除
  27. 这是我的公共 IPv4 148.251.50.26

    回复删除
  28. 我是用我的公共 IPv4 148.251.50.26在我的没有ipv6的电脑来连接ssh termius来搭建naiveproxy的

    回复删除
    回复
    1. 是的。公共 IPv4上面有一个端口是让你用来SSH登录你的vps的,换句话,还有好多其它端口是让其它人去SSH登录他们的woiden VPS的。

      删除
  29. 你好,我的caddy说有损毁,打不开修改

    回复删除
    回复
    1. 也许你wget下载的时候出了问题所以压缩包有问题?
      你可以把之前下载的压缩包删除。再下载试试。

      删除
  30. 这是我的安装指令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

    回复删除
  31. 我是装了v2ray能用后再安装naive和caddy的

    回复删除
  32. 这是我的安装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

    回复删除
  33. 接下来是这个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.

    回复删除
  34. 然后是这个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/

    回复删除
  35. 还有这个root@1444685184woiden:~# cd /tmp
    root@1444685184woiden:/tmp# wget https://github.com/klzgrad/forwardproxy/releases/download/caddy2-naive-20221007/caddy-forwardproxy-naive.tar.xz

    回复删除
  36. 最後我用這個來找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#

    回复删除
  37. 我的Caddyfile仍然下载不了。不清楚这是怎么回事

    回复删除
    回复
    1. wget https://github.com/klzgrad/forwardproxy/releases/download/caddy2-naive-20221007/caddy-forwardproxy-naive.tar.xz
      这个是下载压缩包

      tar -xf caddy-forwardproxy-naive.tar.xz
      这个是解开压缩包

      删除
  38. 我在这个/tmp/caddy-forwardproxy-naive找的caddyfile正确吗

    回复删除
  39. 你好,我这个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.

    回复删除
  40. 但是我只有两个域名,一个是用了v2ray,另一个用来解析naive的域名,难道还需要制作第三个吗

    回复删除
  41. 我要删掉是吧后面的删掉吗
    # _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

    # 多用户 多path
    # 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}
    }
    }
    }

    回复删除
    回复
    1. 你把这两个之间的部分删掉
      # _naive_config_begin_
      # _naive_config_end_

      再后面是给v2ray用的。
      你自己阅读一下配置文件,看看里面写的什么域名。

      删除
  42. 你好,我的caddy似乎启动成功了,怎么用naiveproxy这个节点呢,我只有v2ray的脚本文本

    回复删除
    回复
    1. 你需要google "naiveproxy 节点如何使用"
      作者的repo的readme里面写了基本的用法
      https://github.com/klzgrad/naiveproxy#client-setup

      删除
  43. 下面描述了 forwardproxy 設置的原始分支。

    建造:

    go install github.com/caddyserver/xcaddy/cmd/xcaddy@latest
    ~/go/bin/xcaddy build --with github.com/caddyserver/forwardproxy@caddy2=github.com/klzgrad/forwardproxy@naive
    他这个需要设置吗在我运行完caddyfile之后

    回复删除
    回复
    1. 你说的那是搭服务端。
      你需要的是这部分
      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.

      删除
  44. 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.
    这个是服务端吗?写在哪个文件呢?

    回复删除
  45. 然后我发现启动caddy后在google输入我的naive域名是没有反应的,是caddy运行不成功吗

    回复删除
  46. 我用的的是macbook m系列的,只能用小火箭,v2rayu 没有naiveproxy协议

    回复删除
  47. 如果用的是小火箭,那这个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.
    放在哪里

    回复删除
    回复
    1. 你自己google一下 shadowrocket如何使用 naiveproxy

      删除
  48. 你好,我下载的客户端文件没法用在v2yaryu,每次都显示 vmess adress out,小火箭也显示超时,这个到底该怎么用呢

    回复删除
  49. 而且我运行的sudo setcap cap_net_bind_service=+ep ./caddy
    ./caddy start这条指令显示 error ./caddy,该怎么办呢

    回复删除
    回复
    1. 我的脚本里没有这一句吧。你在哪里看到的,要问那个作者啊。

      删除
  50. 不对啊我的vmess是可以正常用的,不太可能影响naiveproxy的config。json的吧?

    回复删除
  51. sudo setcap cap_net_bind_service=+ep ./caddy
    ./caddy start这条指令是上面发给我的那个github的指令,那个好像是服务端的指令
    https://github.com/klzgrad/naiveproxy#client-setup

    回复删除
  52. 不过我用的小火箭还需要用客户端那个config。json的文件吗?我是下载linux的还是macos的文件呢

    回复删除
  53. 我google的shadowrocket如何使用naiveproxy里面的博主都用他们的二维码来扫码,但是我用你的脚本好像是没有二维码的,那我该怎么搭建shadowrocket呢

    回复删除
    回复
    1. "小火箭是可以连接上naiveproxy服务器,type里选择h2或者https就可以" - 这是我搜索得到的答案 https://github.com/klzgrad/naiveproxy/issues/39
      你把shadowrocket打开, 点右上角+号,再点击 “类型” 你应该能看到 HTTPS, HTTP2 下面写了 naiveproxy的小字。然后你只需要填写 地址,端口,用户,密码 这四项就可以了。

      删除
  54. 而且我在上面测试“测试一下你的VLESS/Vmess 和 NaiveProxy”的时候发现naiveproxy的域名是没有任何伪装网站,只是google说我搜索的字体有错别字

    回复删除
    回复
    1. 配置文件里这一段是伪装站
      file_server {
      root /var/www/html
      }
      如果你没有在VPS的 /var/www/html 这个位置放一个index.html 那么访问 https://你的naive的域名:端口 就会什么都没有

      删除
  55. 我查过是有这个文件的,/var/www/html 这个位置放一个index.html,因为是按上面操作mkdir -p /var/www/html
    echo "hello world" > /var/www/html/index.html
    来进行的,但就是google域名报错

    回复删除
    回复
    1. 用你的浏览器访问 https://你的域名:端口
      就像我访问 https://npp.tzzhu.gq:14443 一样

      删除
  56. 而且我加载的naiveproxy在小火箭中测试超时,用不了,该怎么办呢

    回复删除
    回复
    1. 你先测试 https://你的域名:端口 能出来伪装网页再说。只有这样才说明你的服务器搭好了。
      同样的,你也可以通过 https://www.uptrends.com/tools/uptime 这个第三方来测试你的naive节点搭好了没有。排除掉你自己网络的原因。

      删除
  57. 你好,我通过 https://www.uptrends.com/tools/uptime 这个第三方来测试你的naive节点,全都是红色,写着DNS LOOKUP ERROR

    回复删除
    回复
    1. 你测试的 https://npp.tzzhu.gq:14443 这个吗?

      删除
    2. 我的意思是仅输入 https://npp.tzzhu.gq:14443 没有其它部分

      删除
  58. 不是,我是输入我的域名·和caddyfile的端口:443

    回复删除
  59. 回复
    1. 你提到的错误信息“DNS LOOKUP ERROR”说明域名解析有问题。建议你去查一下。你可以用ping.pe第三方检查你的域名解析的结果。

      删除
  60. 这是我查到的结果
    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 ...

    回复删除
    回复
    1. 你确认这个解析出来的IP地址是否正确。
      如果是正确的,那么你接下来可以使用 ping.pe 检测你的 域名:端口 tcp是不是通的。

      删除
  61. 似乎这个是有一半是运行的

    回复删除
  62. 域名好像可以,我也ping过了,有延迟

    回复删除
  63. 你好,我测过我的域名 naive.lokou.cf的443 和80都是通的

    回复删除
  64. 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

    回复删除
  65. 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.

    回复删除
    回复
    1. 你在你自己的VPS上访问你的 https://域名:端口
      curl -L htttps://域名:端口

      删除
  66. 好像我的域名端口都是通的

    回复删除
  67. 不行,这个有问题root@1444685184woiden:~# curl -L htttps://naive.lokou.cf
    curl: (1) Protocol "htttps" not supported or disabled in libcurl

    回复删除
  68. 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
    你好,他好像一直在运行,没有显示

    回复删除
  69. root@1444685184woiden:~# curl -L https://naive.lokou.cf
    curl: (6) Could not resolve host: naive.lokou.cf
    root@1444685184woiden:~#

    回复删除
    回复
    1. 这个错误是说域名不能解析。我不知道你把网络环境配置成什么样子了。
      我测试你的域名是可以出来hello world的结果的,说明搭好了呀。
      ~# curl -L https://naive.lokou.cf
      hello world

      删除
  70. 会不会是我的v2ray和naiveproxy并存,然后用了v2ray后不能用naiveproxy了?

    回复删除
  71. 又或者说naiveproxy只适合ipv6而不适合ipv4的?

    回复删除
    回复
    1. naive 不能过cdn, 你有ipv6环境吗?能tcp连通 woiden的ipv6地址吗?

      删除
  72. 还是说caddy需要另一条指令启动吗,因为我是用那个service caddy start

    回复删除
  73. 然后我配置的内容是根据etc/caddy/caddyfile这个内容去配置的

    回复删除
  74. 我只有v2ray的域名过cdn,naive的没开小云朵,只是dns解析

    回复删除
  75. 我这个woiden ipv6的443 和80是显示无效代码
    [ 2a01:4f8:202:1002:1111:1111:3152:0001 ]:443

    回复删除
  76. ! 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

    回复删除
  77. 或者你那边也测下,它的代码太多我发布了

    回复删除
  78. 我这里查的时候显示命令无效,查不到

    回复删除
  79. 不太懂哪个github呢?是自己的吗

    回复删除
    回复
    1. https://github.com/crazypeace/naive
      这里就是这个脚本的github项目
      里面有个issue你可以提问题,贴代码不会被夹。

      删除
  80. 要不我把caddfile的配置文件发给你,然后用小火箭看看那边能不能用?

    回复删除
    回复
    1. 你发给我也没用。我不能ipv6访问 woiden的ipv6地址。

      删除
  81. 因为我的v2ray是用warp出站的,不知道naive的并存是否也可以用warp出站

    回复删除
    回复
    1. 你把naive后面接上v2ray就肯定走v2ray的出站出去了。
      https://zelikk.blogspot.com/2022/11/naiveproxy-socks5-v2ray-cn-ip-domain-route.html

      删除
  82. 你好,尝试很多次,似乎都是连接失败

    回复删除
  83. 你好,我的google已经成功连接,但是小火箭仍然显示超时并且说配置无效

    回复删除
    回复
    1. google能用就说明翻成功了呀。翻墙客户端的测试结果只能信一半。

      删除
  84. 你好,两天过去了,仍然用不了这个节点,该怎么办呢

    回复删除

发表评论

The Hot3 in Last 30 Days

ClouDNS .asia免费域名 托管到CloudFlare开CDN白嫖Websocket WS通道翻墙 / desec.io

无服务器 自建短链服务 Url-Shorten-Worker 完整的部署教程