Woiden IPv6 VPS 搭 V2ray 梯子 VLESS+Websocket+TLS 模式 免费 白嫖 全程手机操作

最近因为Woiden的网络环境有一些变化,请看这里的最新更新: 

<Woiden IPv6 VPS 搭 V2ray 梯子 2022-8-1>


HAX 的 IPv6 VPS 大火之后,现在库存已经被抢完了。目前手里有鸡的朋友,谨慎删鸡哦。

同样一套班子,又搭了一个Woiden.id出来,机器是基于OpenVZ虚拟的NAT VPS,有共享的IPv4,独立的IPv6。

整个搭建过程和HAX差不多。准备工作有一点点不一样。一开始要关闭自带的apache2服务,最后也不需要WARP获得IPv4'网口'


前提条件:

手机能上Telegram.

手机有个翻墙工具,比如 Shadowrocket,或者 V2rayNG.

手机走数据流量有IPv6。一般来说都有。用你的手机流量访问 http://test-ipv6.com/ 测试一下。

test-ipv6.com 测试你的IPv6网络环境


手机要有个SSH工具。

iOS可以用 Termius 图标是这个

Termius iOS 网络工具

安卓可以用 JuiceSSH (官方网站changelog)

JuiceSSH 安卓Android网络工具

搭建过程:

1. 创建 HAX VPS

1.1 注册Woiden账号

访问 https://woiden.id/ 点击左上角 "三" - Register

也可以直接访问 https://woiden.id/register

Woiden注册账户

点击机器人的名字,发送 /getid 给机器人,就会得到你的 Telegram ID,将其填到此页面内。点击"Submit"

Woiden注册账户输入Telegram ID
接收验证码,填写到页面中,输入你的Woiden账户密码。点击"Submit"
Woiden注册账户输入Telegram验证码和密码

登录Woiden账户,也可以直接访问 https://woiden.id/login
Woiden登录账户

输入用户名,密码,通过人机验证,点击"Submit"
Woiden登录账户 输入Telegram ID 密码


1.2 创建VPS
点击 "三" - "VPS" - "Create VPS",也可以直接访问 https://woiden.id/create-vps/
Woiden创建VPS
数据中心随便选,操作系统推荐 Debian 11,root密码自己定一个,推荐用 https://git.io/xkcdpw 生成,VPS目的随便选,勾上一堆"我同意",再通过一下人机验证。点击 "CREATE VPS"
Woiden创建VPS 选择地点 操作系统 root密码

过几分钟去看 VPS - VPS Info,也可以直接访问 https://woiden.id/vps-info/
Woiden查看VPS信息
把你的 VPS 的 IPv6 地址记下来
Woiden查看VPS IPv6地址

2. SSH 登录 VPS

打开 Termius,进入 Host
Termius Host 列表
右上角的 "+" 号,添加 Host
Termius 创建Host

Hostname 填 VPS 的 IPv6 地址
Username 填 root
Password 填 root 密码 (Create VPS那一步填的密码)
点击 "Save"
Termius 创建Host 输入IP地址 端口 root 密码
点击刚刚保存的 Host
Termius 连接 Host

第一次登录 要同意服务器的指纹。
Termius 连接 Host 同意服务器指纹

点击 连接好的 Host
Termius 连接 Host 后进入Host
就可以命令行操作 Woiden VPS 了。
Termius 连接 Host 命令行界面
推荐优化一下 Termius 的设置,以方便你自己使用:Termius 附加键盘设置
不作此设置也可以,不影响以下步骤,只是操作方便与否。

3. 申请Hax提供的免费域名

登录 Login (如果没有注册过, 那么请注册一个账户, 注册过程和Woiden一样的)
点击 DNS Pointing CF
也可以直接访问 https://hax.co.id/dns-pointing
Hax DNS Pointing CF 域名解析

CF Proxy - No
DNS Name - 数字字母组合随便弄一个
IPv6 Address - 你的VPS的IPv6地址
通过人机验证
点击 Create DNS

Hax DNS Pointing CF 域名解析参数设置 CF Proxy - NO
你申请出来的域名是这样的
Hax DNS Pointing CF 域名解析设置成功
如果不成功,可以把Domain Name那一栏换一下


4. 搭建 VLESS + WebSocket + TLS 模式的 V2Ray

用SSH工具登录VPS

4.1 关闭并删除 Apache2 服务

service apache2 stop
systemctl disable apache2
4.2 安装V2Ray
apt update
apt install -y curl
bash <(curl -L https://github.com/crazypeace/V2ray_VLESS_WebSocket_TLS_CaddyV2/raw/main/install.sh)
* 注意第3条命令很长,其实是一条命令。

一路上按提示输入。
域名填你刚刚申请的
问你IPv4还是IPv6输入6
其它的选项都可以回车默认
最终得到一个vless://链接。
脚本最后提示"用 WARP 创建 IPv4" 时按Ctrl+C取消

复制那个vless链接,添加到你手机的翻墙软件里面。访问google.com试试(手机使用纯数据流量, 不要开WiFi)。

---------------------
到目前为止,这个梯子只能接受IPv6访问。也就是说只有你的手机数据流量能用。如果你想给你的电脑使用,我们可以利用Cloudflare的CDN在中间作个转换。

5. 打开CDN

先删除CF Proxy为No的那条DNS
移除 Hax DNS Pointing CF 域名解析

再申请一个CF Proxy为Yes的DNS,注意只有CF Proxy为Yes,DNS name与之前的保持一致。
Hax DNS Pointing CF 域名解析参数设置 CF Proxy - YES

生效IPv4的访问需要多一点时间,你可以在你的IPv4环境上ping你的域名,有解析IP地址了就可以用这个梯子了。
梯子的配置参数没有变化,可以使用安装完成时显示的vless://链接。

---------------------


---------------------

后记

Hax域名的CF Proxy - Yes生效可能会很久。还可能生效了一小会又失效。(电脑家宽网络环境,一会儿能打开伪装站,一会儿打不开)

Woiden的网络出口波动很大。我昨天装好连接fast.com测速只有1Mbps左右,今天一会儿只能看720p油管,一会儿又可以刚刚勉强1080p油管(缓冲区数据只有10秒左右)

---------------------

如果你的域名解析很长时间都没有在你的IPv4环境(电脑)生效。
先检查一下Cloudflare服务器上的IPv4解析是否生效了。蓝色部分换成你的域名。
curl -sH 'accept: application/dns-json' "https://cloudflare-dns.com/dns-query?name=chacuoganzao.ipv6a.my.id&type=A" | jq -r '.Answer[0].data'
如果返回了一个IPv4地址。说明Cloudflare那边已经生效了。

如果这个IPv4你在自己的网络环境可以ping通,你可以自行修改你的IPv4环境(电脑)hosts文件,添加一行。蓝色部分换成你自己的IPv4和域名。
104.21.46.211 chacuoganzao.ipv6a.my.id
你也可以试试Cloudflare的IP优选找出你能用的Cloudflare的CDN的IPv4。https://github.com/XIU2/CloudflareSpeedTest

---------------------

有时候hax和woiden的网络环境影响脚本查询本机IP地址,你确认准备工作都是正确的,但是脚本就是提示"你的域名未解析到xxxxxx"。
此时你可以带域名参数跑脚本,这样可以跳过IP地址检查。
bash <(curl -L https://github.com/crazypeace/V2ray_VLESS_WebSocket_TLS_CaddyV2/raw/main/install.sh) 你的域名 6

 ---------------------

想在电脑上操作也不是不行。先要通过端口转发让电脑IPv4可以登录到HAX的IPv6的22端口上。目前Hax.co.id提供了端口转发,参考此文的第4步和第5步。不过有些转发机的IPv4已经被封了。目前还有可用的,不知道未来怎么样。
update: 
如果Hax是你的第一个VPS


如果你手里已经有其它VPS,还可以用这个方法
---------------------
没有IPv6的环境还有一个办法操作VPS,WebBase-SSH Client.

---------------------

附正常安装日志:

root@391032510woiden:~# service apache2 stop
root@391032510woiden:~# systemctl disable apache2
Synchronizing state of apache2.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable apache2
insserv: script bind9: service bind9 already provided!
insserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6).
insserv: script bind9: service bind9 already provided!
Removed /etc/systemd/system/multi-user.target.wants/apache2.service.
root@391032510woiden:~# 

 

root@391032510woiden:~# apt update
Get:1 http://security.debian.org/debian-security bullseye-security InRelease [44.1 kB]
Get:2 http://deb.debian.org/debian bullseye InRelease [116 kB]
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [39.4 kB]
Get:4 http://security.debian.org/debian-security bullseye-security/main amd64 Packages [124 kB]
Get:5 http://security.debian.org/debian-security bullseye-security/main Translation-en [79.1 kB]
Get:6 http://deb.debian.org/debian bullseye/main amd64 Packages [8182 kB]
Get:7 http://deb.debian.org/debian bullseye/main Translation-en [6241 kB]
Get:8 http://deb.debian.org/debian bullseye/contrib amd64 Packages [50.5 kB]
Get:9 http://deb.debian.org/debian bullseye/non-free amd64 Packages [93.8 kB]
Get:10 http://deb.debian.org/debian bullseye/non-free Translation-en [91.3 kB]
Get:11 http://deb.debian.org/debian bullseye-updates/main amd64 Packages.diff/Index [6117 B]
Get:12 http://deb.debian.org/debian bullseye-updates/main Translation-en.diff/Index [3873 B]
Get:13 http://deb.debian.org/debian bullseye-updates/main amd64 Packages T-2022-03-26-2012.00-F-2021-10-26-2004.40.pdiff [1641 B]
Get:13 http://deb.debian.org/debian bullseye-updates/main amd64 Packages T-2022-03-26-2012.00-F-2021-10-26-2004.40.pdiff [1641 B]
Get:14 http://deb.debian.org/debian bullseye-updates/main Translation-en T-2021-10-26-2004.40-F-2021-10-26-2004.40.pdiff [347 B]
Get:14 http://deb.debian.org/debian bullseye-updates/main Translation-en T-2021-10-26-2004.40-F-2021-10-26-2004.40.pdiff [347 B]
Fetched 15.1 MB in 16s (948 kB/s)                                                                                                                                                                               
Reading package lists... Done
Building dependency tree... Done
79 packages can be upgraded. Run 'apt list --upgradable' to see them.
N: Repository 'http://deb.debian.org/debian bullseye InRelease' changed its 'Version' value from '11.0' to '11.3'

 

root@391032510woiden:~# apt install -y curl
Reading package lists... Done
Building dependency tree... Done
The following additional packages will be installed:
  libcurl4
The following NEW packages will be installed:
  curl
The following packages will be upgraded:
  libcurl4
1 upgraded, 1 newly installed, 0 to remove and 78 not upgraded.
Need to get 608 kB of archives.
After this operation, 435 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 libcurl4 amd64 7.74.0-1.3+deb11u1 [341 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 curl amd64 7.74.0-1.3+deb11u1 [267 kB]
Fetched 608 kB in 0s (1663 kB/s)

(Reading database ... 28243 files and directories currently installed.)
Preparing to unpack .../libcurl4_7.74.0-1.3+deb11u1_amd64.deb ...
Unpacking libcurl4:amd64 (7.74.0-1.3+deb11u1) over (7.74.0-1.3+b1) ...
Selecting previously unselected package curl.
Preparing to unpack .../curl_7.74.0-1.3+deb11u1_amd64.deb ...
Unpacking curl (7.74.0-1.3+deb11u1) ...
Setting up libcurl4:amd64 (7.74.0-1.3+deb11u1) ...
Setting up curl (7.74.0-1.3+deb11u1) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13) ...

 

root@391032510woiden:~# bash <(curl -L https://github.com/crazypeace/V2ray_VLESS_WebSocket_TLS_CaddyV2/raw/main/install.sh)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   160  100   160    0     0    220      0 --:--:-- --:--:-- --:--:--   220
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
此脚本仅兼容于Debian 10+系统. 如果你的系统不符合,请Ctrl+C退出脚本
可以去 https://github.com/crazypeace/V2ray_VLESS_WebSocket_TLS_CaddyV2 查看脚本整体思路和关键命令, 以便针对你自己的系统做出调整.
有问题加群 https://t.me/+-wsJtBhlbQ8zMzRl
----------------------------------------------------------------
100 13455  100 13455    0     0  11599      0  0:00:01  0:00:01 --:--:-- 33721
按  Enter 回车键  继续....或按  Ctrl + C  取消.
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
78 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
bash is already the newest version (5.1-2+b3).
curl is already the newest version (7.74.0-1.3+deb11u1).
sudo is already the newest version (1.9.5p2-3).
The following additional packages will be installed:
  libjq1 libonig5
The following NEW packages will be installed:
  jq libjq1 libonig5
0 upgraded, 3 newly installed, 0 to remove and 78 not upgraded.
Need to get 384 kB of archives.
After this operation, 1148 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 libonig5 amd64 6.9.6-1.1 [185 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 libjq1 amd64 1.6-2.1 [135 kB]
Get:3 http://deb.debian.org/debian bullseye/main amd64 jq amd64 1.6-2.1 [64.9 kB]
Fetched 384 kB in 5s (71.7 kB/s)

Selecting previously unselected package libonig5:amd64.
(Reading database ... 28250 files and directories currently installed.)
Preparing to unpack .../libonig5_6.9.6-1.1_amd64.deb ...
Unpacking libonig5:amd64 (6.9.6-1.1) ...
Selecting previously unselected package libjq1:amd64.
Preparing to unpack .../libjq1_1.6-2.1_amd64.deb ...
Unpacking libjq1:amd64 (1.6-2.1) ...
Selecting previously unselected package jq.
Preparing to unpack .../archives/jq_1.6-2.1_amd64.deb ...
Unpacking jq (1.6-2.1) ...
Setting up libonig5:amd64 (6.9.6-1.1) ...
Setting up libjq1:amd64 (1.6-2.1) ...
Setting up jq (1.6-2.1) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13) ...


安装V2ray最新版本
----------------------------------------------------------------
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 21647  100 21647    0     0  46254      0 --:--:-- --:--:-- --:--:-- 46353
info: Installing V2Ray v4.44.0 for x86_64
Downloading V2Ray archive: https://github.com/v2fly/v2ray-core/releases/download/v4.44.0/v2ray-linux-64.zip
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   657  100   657    0     0    744      0 --:--:-- --:--:-- --:--:--   744
100 13.2M  100 13.2M    0     0  5712k      0  0:00:02  0:00:02 --:--:-- 10.6M
Downloading verification file for V2Ray archive: https://github.com/v2fly/v2ray-core/releases/download/v4.44.0/v2ray-linux-64.zip.dgst
info: Extract the V2Ray package to /tmp/tmp.cNMTF7JoWp and prepare it for installation.
info: Systemd service files have been installed successfully!
warning: The following are the actual parameters for the v2ray service startup.
warning: Please make sure the configuration file path is correctly set.
# /etc/systemd/system/v2ray.service
[Unit]
Description=V2Ray Service
Documentation=https://www.v2fly.org/
After=network.target nss-lookup.target

[Service]
User=nobody
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
AmbientCapabilities=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
NoNewPrivileges=true
ExecStart=/usr/local/bin/v2ray -config /usr/local/etc/v2ray/config.json
Restart=on-failure
RestartPreventExitStatus=23

[Install]
WantedBy=multi-user.target

# /etc/systemd/system/v2ray.service.d/10-donot_touch_single_conf.conf
# In case you have a good reason to do so, duplicate this file in the same directory and make your customizes there.
# Or all changes you made will be lost!  # Refer: https://www.freedesktop.org/software/systemd/man/systemd.unit.html
[Service]
ExecStart=
ExecStart=/usr/local/bin/v2ray -config /usr/local/etc/v2ray/config.json

installed: /usr/local/bin/v2ray
installed: /usr/local/bin/v2ctl
installed: /usr/local/share/v2ray/geoip.dat
installed: /usr/local/share/v2ray/geosite.dat
installed: /usr/local/etc/v2ray/config.json
installed: /var/log/v2ray/
installed: /var/log/v2ray/access.log
installed: /var/log/v2ray/error.log
installed: /etc/systemd/system/v2ray.service
installed: /etc/systemd/system/v2ray@.service
removed: /tmp/tmp.cNMTF7JoWp
info: V2Ray v4.44.0 is installed.
You may need to execute a command to remove dependent software: apt purge curl unzip
Please execute the command: systemctl enable v2ray; systemctl start v2ray

安装CaddyV2最新版本
----------------------------------------------------------------
sudo: unable to resolve host 391032510woiden.localdomain: Name or service not known
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
debian-archive-keyring is already the newest version (2021.1.1).
The following NEW packages will be installed:
  apt-transport-https debian-keyring
0 upgraded, 2 newly installed, 0 to remove and 78 not upgraded.
Need to get 31.3 MB of archives.
After this operation, 32.7 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 apt-transport-https all 2.2.4 [160 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 debian-keyring all 2021.07.26 [31.1 MB]
Fetched 31.3 MB in 2s (18.4 MB/s)         

Selecting previously unselected package apt-transport-https.
(Reading database ... 28270 files and directories currently installed.)
Preparing to unpack .../apt-transport-https_2.2.4_all.deb ...
Unpacking apt-transport-https (2.2.4) ...
Selecting previously unselected package debian-keyring.
Preparing to unpack .../debian-keyring_2021.07.26_all.deb ...
Unpacking debian-keyring (2021.07.26) ...
Setting up apt-transport-https (2.2.4) ...
Setting up debian-keyring (2021.07.26) ...

sudo: unable to resolve host 391032510woiden.localdomain: Name or service not known
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
OK
sudo: unable to resolve host 391032510woiden.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 https://dl.cloudsmith.io/public/caddy/stable/deb/debian any-version main

deb-src https://dl.cloudsmith.io/public/caddy/stable/deb/debian any-version main
sudo: unable to resolve host 391032510woiden.localdomain: Name or service not known
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye 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 [7491 B]   
Get:5 https://dl.cloudsmith.io/public/caddy/stable/deb/debian any-version/main amd64 Packages [1248 B]
Fetched 8739 B in 4s (2436 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
78 packages can be upgraded. Run 'apt list --upgradable' to see them.
sudo: unable to resolve host 391032510woiden.localdomain: Name or service not known
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  caddy
0 upgraded, 1 newly installed, 0 to remove and 78 not upgraded.
Need to get 11.7 MB of archives.
After this operation, 34.0 MB 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.4.6 [11.7 MB]
Fetched 11.7 MB in 3s (4572 kB/s)

Selecting previously unselected package caddy.
(Reading database ... 28284 files and directories currently installed.)
Preparing to unpack .../archives/caddy_2.4.6_amd64.deb ...
Unpacking caddy (2.4.6) ...
Setting up caddy (2.4.6) ...
Created symlink /etc/systemd/system/multi-user.target.wants/caddy.service → /lib/systemd/system/caddy.service.

 


打开BBR
----------------------------------------------------------------


配置 VLESS_WebSocket_TLS 模式
----------------------------------------------------------------
请输入 V2RayID 
(默认ID: 4520d087-c4df-4af9-b17d-204a5189dc85):


 V2RayID = 4520d087-c4df-4af9-b17d-204a5189dc85
----------------------------------------------------------------

请输入 V2Ray 端口 [1-65535], 不能选择 80 或 443 端口
(默认端口: 28441):


 V2Ray 端口 = 28441
----------------------------------------------------------------


请输入一个 正确的域名 Input your domain
(例如: mydomain.com): erzhanlarou.ipv6a.my.id


 你的域名 = erzhanlarou.ipv6a.my.id
----------------------------------------------------------------
如果你的小鸡是双栈(同时有IPv4和IPv6的IP),请选择你把v2ray搭在哪个'网口'上
如果你不懂这段话是什么意思, 请直接回车
Input 4 for IPv4, 6 for IPv6: 6


 请将 erzhanlarou.ipv6a.my.id  解析到: 2001:bc8:2146:300:1235:1235:1446:1

 Resolve erzhanlarou.ipv6a.my.id  to: 2001:bc8:2146:300:1235:1235:1446:1

 请将 erzhanlarou.ipv6a.my.id  解析到: 2001:bc8:2146:300:1235:1235:1446:1
----------------------------------------------------------------

(是否已经正确解析: [Y]): Is resolution correct?y


 域名解析 = 我确定已经有解析了
----------------------------------------------------------------

请输入想要  用来分流的路径  , 例如 /v2raypath , 那么只需要输入 v2raypath 即可
(默认: [204a5189dc85]):


 分流的路径 = /204a5189dc85
----------------------------------------------------------------

请输入 一个正确的  网址 用来作为 网站的伪装 , 例如 https://zelikk.blogspot.com
(默认: [https://zelikk.blogspot.com]):


 伪装的网址 = https://zelikk.blogspot.com
----------------------------------------------------------------


配置 /usr/local/etc/v2ray/config.json
----------------------------------------------------------------

配置 /etc/caddy/Caddyfile
----------------------------------------------------------------

重启 V2Ray
----------------------------------------------------------------

重启 CaddyV2
----------------------------------------------------------------


---------- V2Ray 配置信息 -------------

 ---提示..这是 VLESS 服务器配置--- 

 地址 (Address) = erzhanlarou.ipv6a.my.id

 端口 (Port) = 443

 用户ID (User ID / UUID) = 4520d087-c4df-4af9-b17d-204a5189dc85

 流控 (Flow) = 空

 加密 (Encryption) = none

 传输协议 (Network) = ws

 伪装类型 (header type) = none

 伪装域名 (host) = erzhanlarou.ipv6a.my.id

 路径 (path) = /204a5189dc85

 底层传输安全 (TLS) = tls

---------- V2Ray VLESS URL ----------
vless://4520d087-c4df-4af9-b17d-204a5189dc85@erzhanlarou.ipv6a.my.id:443?encryption=none&security=tls&type=ws&host=erzhanlarou.ipv6a.my.id&path=204a5189dc85#VLESS_WSS_erzhanlarou.ipv6a.my.id

---------- END -------------


这是一个 IPv6 小鸡,用 WARP 创建 IPv4
----------------------------------------------------------------
按  Enter 回车键  继续....或按  Ctrl + C  取消.

评论

  1. 点击刚刚保存的 Host时报错:👤 Starting a new connection to: "2a01:4f8:140:330e:face:08e3:507b:0001/112" port "22"
    ⚙️ Starting address resolution of "2a01:4f8:140:330e:face:08e3:507b:0001/112"
    😨 Address resolution finished with error: unknown node or service
    请问怎么解决??

    回复删除
    回复
    1. 你需要检查你的网络环境能否访问这个 IP 以及 22 端口。
      请参考 https://zelikk.blogspot.com/2022/03/inettools-ios-ipv6-ipv4-ping-port-free.html
      iOS可以用iNetTools, 安卓可以用IP Tools

      删除
    2. 你应该只填 2a01:4f8:140:330e:face:08e3:507b:0001,没有末尾的那个 /112

      删除
  2. 严格按此教程安装,发现有问题:IP、网址都能Ping通,但V2rayN客户端无法访问。
    反复试验排错,发现解决办法:最后一步WARP不应Ctrl + C 取消,继续回车安装就行了。

    回复删除
  3. 回复
    1. 不客气。很高兴能帮到你。
      免费的总是不长久。在免费的VPS上练手,长期来说,还是最好自己买一个VPS,稳定点。https://zelikk.blogspot.com/2021/11/racknerd-vps-v2ray-1g-1t-12g-768mb-1088.html

      删除
  4. 这个脚本执行搭建成功后,如果想要对某些参数进行微调应该如何操作?
    比如其它脚本再次执行install.sh能够显示菜单继续操作
    还是说需要安装xui面板进行操作?

    回复删除
    回复
    1. 你需要微调什么呢?
      要改节点参数直接改配置文件好了。
      https://zelikk.blogspot.com/2022/05/v2ray-websocket-tls-caddy-path-data-flow.html

      删除
  5. 你好,我用的是woiden,当我在验证域名时我已经把小云朵都关掉了,但都出现如果你的小鸡是双栈(同时有IPv4和IPv6的IP),请选择你把v2ray搭在哪个'网口'上
    如果你不懂这段话是什么意思, 请直接回车
    Input 4 for IPv4, 6 for IPv6: 6

    域名解析错误Domain resolution error....

    你的域名: hax.lokou.ml 未解析到:

    你的域名当前解析到: 2a01:4f8:151:24e7:face:754:d8a3:1

    备注...如果你的域名是使用 Cloudflare 解析的话... 在 DNS 设置页面, 请将代理状态设置为仅限DNS, 小云朵变灰.
    Notice...If you use Cloudflare to resolve your domain, on 'DNS' setting page, 'Proxy status' should be 'DNS only' but not 'Proxied'.
    我尝试强制安装生成vless链接跳过域名审查,但生成的节点没有反应,该怎么办呢

    回复删除
    回复
    1. 检测本机IP这个机制并不是一个特别准确的方法。在某些网络环境下是测不出来的。所以我提供了带参数执行脚本跳过IP检测的方法。
      安装完以后,排查问题看这个。https://zelikk.blogspot.com/2022/04/setup-v2ray-websocket-tls-troubleshoot.html

      删除
    2. 你能说一下你开在woiden的eu几吗?我去测试一下。

      删除
    3. 我刚刚开了一个woiden-eu-2的小鸡,测试可以完整安装完这个脚本。
      你再对照一下安装和排错的教程吧。

      删除
  6. 你好,我在检查时caddy显示
    caddy.service - Caddy
    Loaded: loaded (/lib/systemd/system/caddy.service; enabled; vendor preset: enabled)
    Active: failed (Result: exit-code) since Mon 2022-11-07 07:28:27 EST; 13h ago
    Docs: https://caddyserver.com/docs/
    Main PID: 35314 (code=exited, status=1/FAILURE)
    Status: "loading new config: http app module: start: listening on :443: listen tcp :443: bind: address already in use"
    CPU: 121ms
    该怎么办呢

    回复删除
    回复
    1. 你能主动检查出来caddy的报错信息很不错!你可以拿微信扫一扫翻译一下。意思是说443端口被占用了。你可以用 lsof -i:443 查一下是谁在监听这个端口

      删除
  7. 并且我在 '第三方' tcp ping檢查DNS是否正確时ssh没有反应及用瀏覽器訪問我的域名时没有伪装站

    回复删除
    回复
    1. 从脚本显示的内容来看,你的域名的DNS解析应该是设置的正确的。 ping.pe 检测你的IP地址解析应该与之一致。

      删除
  8. 你好,我输入指令后发现了这个:
    root@1444685184hax:~# lsof -i:443
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    xray 36402 root 3u IPv6 160742 0t0 TCP *:https (LISTEN)
    ,那怎么办呢

    回复删除
    回复
    1. 你应该又使用了别的一键脚本吧?你需要把别的脚本安装的内容清理掉。如果你弄不明白,你可以重新安装操作系统,把VPS清空。

      删除
  9. 你好,我重新安装并运行完后生成了链接,但是完全用不了,在手机也是,会不会是我人在国外,所以用不了这个链接呢?不然又是怎么回事呢?

    回复删除
    回复
    1. 你人在国内国外应该不是原因. 你使用的是国内的VPS吗? 如果你是用的 woiden, 那不是国内的资源. 安装完不能使用, 还是要排查一下原因. https://zelikk.blogspot.com/2022/04/setup-v2ray-websocket-tls-troubleshoot.html

      删除
    2. 我的这个脚本写得很简单, 只是帮你输入一下命令而已, 能生成链接并不能说明没有问题.

      删除
  10. 你好,我在检查caddy还是失败
    caddy.service - Caddy
    Loaded: loaded (/lib/systemd/system/caddy.service; enabled; vendor preset: enabled)
    Active: failed (Result: exit-code) since Wed 2022-11-09 07:29:03 EST; 12h ago
    Docs: https://caddyserver.com/docs/
    Process: 44624 ExecStart=/usr/bin/caddy run --environ --config /etc/caddy/Caddyfile (code=exited, status=1/FAILURE)
    Main PID: 44624 (code=exited, status=1/FAILURE)
    Status: "loading new config: http app module: start: listening on :443: listen tcp :443: bind: address already in use"
    CPU: 208ms

    Nov 09 07:29:03 1444685184hax.localdomain caddy[44624]: {"level":"info","ts":1667996943.3345504,"logger":"http","msg":"server is listening >
    Nov 09 07:29:03 1444685184hax.localdomain caddy[44624]: {"level":"info","ts":1667996943.3345695,"logger":"http","msg":"enabling automatic H>
    Nov 09 07:29:03 1444685184hax.localdomain caddy[44624]: {"level":"info","ts":1667996943.3361952,"logger":"tls","msg":"cleaning storage unit>
    Nov 09 07:29:03 1444685184hax.localdomain caddy[44624]: {"level":"info","ts":1667996943.3362179,"logger":"tls","msg":"finished cleaning sto>
    Nov 09 07:29:03 1444685184hax.localdomain caddy[44624]: {"level":"info","ts":1667996943.3363042,"logger":"tls.cache.maintenance","msg":"sta>
    Nov 09 07:29:03 1444685184hax.localdomain caddy[44624]: {"level":"info","ts":1667996943.3363342,"logger":"tls.cache.maintenance","msg":"sto>
    Nov 09 07:29:03 1444685184hax.localdomain caddy[44624]: Error: loading initial config: loading new config: http app module: start: listenin>
    Nov 09 07:29:03 1444685184hax.localdomain systemd[1]: caddy.service: Main process exited, code=exited, status=1/FAILURE
    Nov 09 07:29:03 1444685184hax.localdomain systemd[1]: caddy.service: Failed with result 'exit-code'.
    Nov 09 07:29:03 1444685184hax.localdomain systemd[1]: Failed to start Caddy.
    lines 1-19/19 (END)

    回复删除
  11. 这个是我检查80端口的内容
    root@1444685184hax:~# lsof -i:80
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    nginx 36414 root 6u IPv4 160795 0t0 TCP *:http (LISTEN)
    nginx 36414 root 7u IPv6 160796 0t0 TCP *:http (LISTEN)
    nginx 36415 nginx 6u IPv4 160795 0t0 TCP *:http (LISTEN)
    nginx 36415 nginx 7u IPv6 160796 0t0 TCP *:http (LISTEN

    回复删除
    回复
    1. 这个结果说明是nginx占用了80端口。我的这个脚本是不安装nginx的。
      请问你是重装的系统,直接开始使用我的脚本吗?你安装了其它脚本吗?
      如果你是使用的woiden的Debian11操作系统,不应该出现这样的情况。
      你可以google搜索如何关闭nginx 然后尝试重新启动Caddy
      service caddy start

      删除
    2. 对啊,我重装后直接使用你的脚本的

      删除
  12. 443端口检查的是这个
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    xray 36402 root 3u IPv6 160742 0t0 TCP *:https (LISTEN)
    我都重新安装了debian系统了,这些问题似乎还在,该怎么办呢?

    回复删除
    回复
    1. 我的脚本不是安装的xray。你应该是使用了其它脚本安装什么功能。
      我的脚本是安装的v2ray.

      删除
    2. 那这个怎么办呢?我都反复重装了,好像它还有残余的脚本

      删除
    3. 你确定用的是重装操作系统的功能?https://woiden.id/vps-reinstall
      重装操作系统后的VPS应该没有xray,也没有nginx.

      删除
    4. 主要是我重新安装debian11是有xray,但是我选择其他系统则全部清空例如debian10,那我还能用debian11搭建吗

      删除
    5. 重新安装操作系统不可能自带xray
      你去 woiden的群里问问怎么操作吧。https://t.me/ipv6china

      删除
  13. 你好,我重新安装了之后caddy能运行,但还是用不了,于是我在排查中发现这个,它好像有问题
    root@1444685184hax:~# /usr/local/bin/v2ray -config /usr/local/etc/v2ray/config.json
    V2Ray 4.45.2 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.18.3 linux/amd64)
    A unified platform for anti-censorship.
    Failed to start app/proxyman/inbound: failed to listen TCP on 33565 > transport/internet: failed to listen on address: 127.0.0.1:33565 > transport/internet/websocket: failed to listen TCP(for WS) on 127.0.0.1:33565 > listen tcp 127.0.0.1:33565: bind: address already in use

    回复删除
    回复
    1. 你在命令行执行这一条之前, 你确认了 service caddy status是已经在运行的吗?
      别在sevice里已经跑了一个caddy占了端口,你又在命令行跑一个然后报错说端口被占用。
      如果你的caddy已经在service里运行了。你去查有没有得到证书
      “4.1 检查是否成功得到域名的证书. 有没有.crt .key 文件?”

      删除
  14. 80和443好像多了几条caddy
    root@1444685184hax:~# lsof -i:80
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    caddy 2036 caddy 9u IPv6 17454 0t0 TCP *:http (LISTEN)
    root@1444685184hax:~# lsof -i:443
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    caddy 2036 caddy 7u IPv6 17452 0t0 TCP *:https (LISTEN)
    caddy 2036 caddy 8u IPv6 17453 0t0 UDP *:https
    caddy 2036 caddy 10u IPv6 17464 0t0 TCP [2a01:4f8:151:24e7:face:754:d8a3:1]:60908->[2606:4700:60:0:f53d:5624:85c7:3a2c]:https (ESTABLISHED)

    回复删除
  15. 然后我的伪装域名并没有开,只显示无法连接这个网站,该怎么解决呢

    回复删除
  16. ipv6那个群没人理会,还想请你帮下我,谢谢:我已经重装完毕并且开启了caddy,为什么又有新的问题呢?

    回复删除
  17. 你好,这个我是有运行的
    caddy.service - Caddy
    Loaded: loaded (/lib/systemd/system/caddy.service; enabled; vendor preset: enabled)
    Active: active (running) since Thu 2022-11-10 02:14:39 EST; 1 day 2h ago
    Docs: https://caddyserver.com/docs/
    Main PID: 2036 (caddy)
    Tasks: 7 (limit: 455)
    Memory: 15.1M
    CPU: 4.106s
    CGroup: /system.slice/caddy.service
    └─2036 /usr/bin/caddy run --environ --config /etc/caddy/Caddyfile

    Nov 10 02:14:41 1444685184hax.localdomain caddy[2036]: {"level":"info","ts":1668064481.515747,"logger":"tls","msg":"served key authenticati>
    Nov 10 02:14:41 1444685184hax.localdomain caddy[2036]: {"level":"info","ts":1668064481.6047235,"logger":"tls","msg":"served key authenticat>
    Nov 10 02:14:41 1444685184hax.localdomain caddy[2036]: {"level":"info","ts":1668064481.7100153,"logger":"tls","msg":"served key authenticat>
    Nov 10 02:14:42 1444685184hax.localdomain caddy[2036]: {"level":"info","ts":1668064482.1563466,"logger":"http.acme_client","msg":"authoriza>
    Nov 10 02:14:42 1444685184hax.localdomain caddy[2036]: {"level":"info","ts":1668064482.1569085,"logger":"http.acme_client","msg":"validatio>
    Nov 10 02:14:43 1444685184hax.localdomain caddy[2036]: {"level":"info","ts":1668064483.5899806,"logger":"http.acme_client","msg":"successfu>
    Nov 10 02:14:43 1444685184hax.localdomain caddy[2036]: {"level":"info","ts":1668064483.5906963,"logger":"tls.obtain","msg":"certificate obt>
    Nov 10 02:14:43 1444685184hax.localdomain caddy[2036]: {"level":"info","ts":1668064483.5908277,"logger":"tls.obtain","msg":"releasing lock">
    Nov 11 02:14:39 1444685184hax.localdomain caddy[2036]: {"level":"info","ts":1668150879.1461155,"logger":"tls","msg":"cleaning storage unit">
    Nov 11 02:14:39 1444685184hax.localdomain caddy[2036]: {"level":"info","ts":1668150879.1587124,"logger":"tls","msg":"finished cleaning stor>
    lines 1-21/21 (END)

    回复删除
  18. 我是有证件的,但不知道有没有重复
    root@1444685184hax:~# find / -name "*lokou.lokou.ml*"
    /var/lib/caddy/.local/share/caddy/certificates/acme-v02.api.letsencrypt.org-directory/lokou.lokou.ml
    /var/lib/caddy/.local/share/caddy/certificates/acme-v02.api.letsencrypt.org-directory/lokou.lokou.ml/lokou.lokou.ml.key
    /var/lib/caddy/.local/share/caddy/certificates/acme-v02.api.letsencrypt.org-directory/lokou.lokou.ml/lokou.lokou.ml.json
    /var/lib/caddy/.local/share/caddy/certificates/acme-v02.api.letsencrypt.org-directory/lokou.lokou.ml/lokou.lokou.ml.crt
    /var/lib/caddy/.local/share/caddy/ocsp/lokou.lokou.ml-465550c
    那我接下来该怎么做呢

    回复删除
    回复
    1. 5. 用浏览器访问你的域名, 是否显示伪装站? 如果不是, 显示什么?
      5.1 检查是否DNS问题. 在VPS里访问域名, 是否得到 html.../html 的结果?

      删除
    2. 域名显示:无法连接这个网站检查 lokou.lokou.ml 中是否有錯字。
      DNS_PROBE_FINISHED_NXDOMAIN

      删除
  19. dns好像也没有问题,有html

    root@1444685184hax:~#

    回复删除
    回复
    1. 在你的VPS上访问你的域名,有HTML. 再加上ping.pe检测你的DNS设置正确,说明你的VPS上面梯子已经搭好了,不用改动了。
      接下来是要解决从你自己的 电脑/手机 连到VPS上面的这一段。

      删除
  20. ping.pe也没有问题,只是有些地址呈红色
    Probing 2a01:4f8:151:24e7:face:754:d8a3:1 – RIPENCC /32 AS24940 HETZNER – Germany [hosting] MAP

    回复删除
    回复
    1. 现在看起来,你需要把cloudflare的CDN打开。

      删除
  21. 我打开了,但是电脑完全无效,手机v2rayng有速度,但是真延迟是-1,也连接不了

    回复删除
  22. 这个我在检查是否用户权限问题, 在当前用户下运行v2ray是否功能正常
    检查的问题

    root@1444685184hax:~# /usr/local/bin/v2ray -config /usr/local/etc/v2ray/config.json
    V2Ray 4.45.2 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.18.3 linux/amd64)
    A unified platform for anti-censorship.
    Failed to start app/proxyman/inbound: failed to listen TCP on 54152 > transport/internet: failed to listen on address: 127.0.0.1:54152 > transport/internet/websocket: failed to listen TCP(for WS) on 127.0.0.1:54152 > listen tcp 127.0.0.1:54152: bind: address already in use

    回复删除
  23. 这是我的80和443
    root@1444685184hax:~# lsof -i:80
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    caddy 5253 caddy 9u IPv6 50460 0t0 TCP *:http (LISTEN)
    root@1444685184hax:~# lsof -i:443
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    caddy 5253 caddy 7u IPv6 50458 0t0 TCP *:https (LISTEN)
    caddy 5253 caddy 8u IPv6 50459 0t0 UDP *:https

    回复删除
  24. ping.pe 的ipv680端口是连接成功的,但443端口是连接失败的
    Query: tcp6 [2a01:4f8:202:1002:1111:1111:3152:0001]:80

    Location ISP TCP port check result
    USA, CA, Fremont Linode Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    USA, CA, San Francisco Digital Ocean Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    USA, CA, Los Angeles Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    USA, CO, Denver Cogent Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 failed
    USA, IL, Chicago Cogent Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    USA, NY, New York Telehouse/RamNode Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    Canada, QC, Montreal OVH Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    UK, London Cogent Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    Netherlands, Amsterdam Online.net Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    Netherlands, Nuland WeservIT/RamNode Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    Nigeria, Lagos Terrahost Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    Norway, Sandefjord Terrahost Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    Germany, Nuremberg Hetzner Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    Italy, Milan Prometeus Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    India, Mumbai Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    India, Bengaluru Digital Ocean Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    Singapore Digital Ocean Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    Japan, Tokyo Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful
    Australia, Sydney Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:80 successful

    443 port:
    Query: tcp6 [2a01:4f8:202:1002:1111:1111:3152:0001]:443

    Location ISP TCP port check result
    USA, CA, Fremont Linode Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    USA, CA, San Francisco Digital Ocean Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    USA, CA, Los Angeles Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    USA, CO, Denver Cogent Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    USA, IL, Chicago Cogent Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    USA, NY, New York Telehouse/RamNode Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    Canada, QC, Montreal OVH Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    UK, London Cogent Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    Netherlands, Amsterdam Online.net Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    Netherlands, Nuland WeservIT/RamNode Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    Nigeria, Lagos Terrahost Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    Norway, Sandefjord Terrahost Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    Germany, Nuremberg Hetzner Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    Italy, Milan Prometeus Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    India, Mumbai Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    India, Bengaluru Digital Ocean Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    Singapore Digital Ocean Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    Japan, Tokyo Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed
    Australia, Sydney Vultr Connection to [2a01:4f8:202:1002:1111:1111:3152:0001]:443 failed

    回复删除
  25. 我的debian11防火墙是没有的,那是不是443又被占用呢?

    回复删除
    回复
    1. 你现在的问题就是你自己使用的网络环境访问不到 lokou.lokou.ml
      我现在,在我的VPS上,用curl去访问这个域名,可以得到 html 所以说你现在梯子已经不用动了。就解决你自己的网络环境的问题.
      1. 打开CDN。
      2. 你可以修改你自己的hosts,改为CF的CDN服务器的地址,你可以用“优选CF”的方案,不要用104开头的。https://github.com/XIU2/CloudflareSpeedTest/issues/42

      删除
    2. 我的是MacBook m1,怎么下载这个呢

      删除
    3. mac 应该用 linux脚本吧? 我猜。我自己没有mac

      删除
  26. 而且我就是打开cdn也上不了网

    回复删除
    回复
    1. 我在我的环境下测试 Cloudflare的CDN服务器IP地址为172.67.202.14
      所以你把你自己的hosts添加一条,把你的域名 lokou.lokou.ml 解析为 172.67.202.14
      你先测试一下这样通不通,先不管速度。如果这样是通的,那么你只剩下如何弄到在你自己的环境下,好用的Cloudflare的CDN服务器IP地址

      删除
  27. 我这台用的是v2rayu,我是在地址填这个ip,还是host填这个IP?我的host现在写的是lokou.lokou.ml

    回复删除
    回复
    1. 你先测试一下你能不能ping通这个IP?如果可以,那么地址填这个IP;你也可以直接修改你自己的 hosts

      删除
  28. 我试过了,完全连不通,会不会是其他问题?

    回复删除
  29. 终端机是ping通了,但是用不了

    回复删除
  30. 要不我把我这条节点转发给你,你看下能不能通?

    回复删除
    回复
    1. 可以啊。反正你重新搭建的话,节点信息就变了。不担心泄漏的问题。

      删除
  31. vless://ac08b4b0-8712-4f21-a7d9-0d6246da617f@lokou.lokou.ml:443?flow=&security=tls&encryption=none&type=ws&host=lokou.lokou.ml&path=0d6246da617f&sni=#VLESS_WSS_lokou.lokou.ml

    回复删除
  32. 回复
    1. 我测试了一下,我也无法使用这个节点。
      我本地ping测试了,也通过ping.pe测试了,能看到你是给域名开了CDN。
      我测试了 访问域名 正常显示伪装站, 访问 域名/节点path 能得到400 bad request.
      说不清楚到底什么问题。
      1. 你把你的VPS重启一下试试。
      2. 你检查一下你的v2ray的config.json里面的UUID是否与节点信息一致

      删除
  33. 我用的是woiden ssh的终端机,如何检查我的v2ray的config.json里面的UUID?

    回复删除
    回复
    1. 请看这篇。
      https://zelikk.blogspot.com/2022/05/v2ray-websocket-tls-caddy-path-data-flow.html
      解释了VPS上的配置文件参数对应节点配置参数。

      删除
  34. 我运行了这个之后只回应了个重复的给我Last login: Sun Nov 13 07:03:57 2022 from 2400:8901::f03c:92ff:fec2:7bd3
    root@1444685184hax:~# find / -name "config.json"

    /usr/local/etc/v2ray/config.json

    回复删除
    回复
    1. 可以用cat输出文件内容,也可以用文本编辑器打开比如nano或者vi

      删除
  35. root@1444685184woiden:~# cat /usr/local/etc/v2ray/config.json
    { // VLESS + WebSocket + TLS
    "log": {
    "access": "/var/log/v2ray/access.log",
    "error": "/var/log/v2ray/error.log",
    "loglevel": "warning"
    },
    "inbounds": [
    {
    "listen": "127.0.0.1",
    "port": 54703, // ***
    "protocol": "vless",
    "settings": {
    "clients": [
    {
    "id": "f1d3834f-b319-4326-a672-9eaf4a169dac", // ***
    "level": 1,
    "alterId": 0
    }
    ],
    "decryption": "none"
    },
    "streamSettings": {
    "network": "ws"
    },
    "sniffing": {
    "enabled": true,
    "destOverride": [
    "http",
    "tls"
    ]
    }
    }
    ],
    "outbounds": [
    {
    "protocol": "freedom",
    "settings": {
    "domainStrategy": "UseIP"
    },
    "tag": "direct"
    },
    // [outbound]
    {
    "protocol": "freedom",
    "settings": {
    "domainStrategy": "UseIPv4"
    },
    "tag": "force-ipv4"
    },
    {
    "protocol": "freedom",
    "settings": {
    "domainStrategy": "UseIPv6"
    },
    "tag": "force-ipv6"
    },
    // {
    // "protocol": "socks",
    // "settings": {
    // "servers": [{
    // "address": "127.0.0.1",
    // "port": 40000 //warp socks5 port
    // }]
    // },
    // "tag": "socks5-warp"
    // },
    {
    "protocol": "blackhole",
    "settings": {},
    "tag": "blocked"
    }
    ],
    "dns": {
    "servers": [
    "https+local://8.8.8.8/dns-query",
    "8.8.8.8",
    "1.1.1.1",
    "localhost"
    ]
    },
    "routing": {
    "domainStrategy": "IPOnDemand",
    "rules": [
    {
    "type": "field",
    "ip": [
    "0.0.0.0/8",
    "10.0.0.0/8",
    "100.64.0.0/10",
    "127.0.0.0/8",
    "169.254.0.0/16",
    "172.16.0.0/12",
    "192.0.0.0/24",
    "192.0.2.0/24",
    "192.168.0.0/16",
    "198.18.0.0/15",
    "198.51.100.0/24",
    "203.0.113.0/24",
    "::1/128",
    "fc00::/7",
    "fe80::/10"
    ],
    "outboundTag": "blocked"
    },
    // [routing-rule]
    // {
    // "type": "field",
    // "outboundTag": "force-ipv6", // force-ipv6 // force-ipv4 // socks5-warp
    // "domain": ["geosite:google"] // ***
    // },
    {
    "type": "field",
    "protocol": [
    "bittorrent"
    ],
    "outboundTag": "blocked"
    }
    ]
    }
    }

    回复删除
  36. root@1444685184woiden:~# cat /usr/local/etc/v2ray/config.json
    { // VLESS + WebSocket + TLS
    "log": {
    "access": "/var/log/v2ray/access.log",
    "error": "/var/log/v2ray/error.log",
    "loglevel": "warning"
    },
    "inbounds": [
    {
    "listen": "127.0.0.1",
    "port": 54703, // ***
    "protocol": "vless",
    "settings": {
    "clients": [
    {
    "id": "f1d3834f-b319-4326-a672-9eaf4a169dac", // ***
    "level": 1,
    "alterId": 0
    }
    ],
    "decryption": "none"
    },
    "streamSettings": {
    "network": "ws"
    },
    "sniffing": {
    "enabled": true,
    "destOverride": [
    "http",
    "tls"
    ]
    }
    }
    ],
    "outbounds": [
    {
    "protocol": "freedom",
    "settings": {
    "domainStrategy": "UseIP"
    },
    "tag": "direct"
    },
    // [outbound]
    {
    "protocol": "freedom",
    "settings": {
    "domainStrategy": "UseIPv4"
    },
    "tag": "force-ipv4"
    },
    {
    "protocol": "freedom",
    "settings": {
    "domainStrategy": "UseIPv6"
    },
    "tag": "force-ipv6"
    },
    // {
    // "protocol": "socks",
    // "settings": {
    // "servers": [{
    // "address": "127.0.0.1",
    // "port": 40000 //warp socks5 port
    // }]
    // },
    // "tag": "socks5-warp"
    // },
    {
    "protocol": "blackhole",
    "settings": {},
    "tag": "blocked"
    }
    ],
    "dns": {
    "servers": [
    "https+local://8.8.8.8/dns-query",
    "8.8.8.8",
    "1.1.1.1",
    "localhost"
    ]
    },
    "routing": {
    "domainStrategy": "IPOnDemand",
    "rules": [
    {
    "type": "field",
    "ip": [
    "0.0.0.0/8",
    "10.0.0.0/8",
    "100.64.0.0/10",
    "127.0.0.0/8",
    "169.254.0.0/16",
    "172.16.0.0/12",
    "192.0.0.0/24",
    "192.0.2.0/24",
    "192.168.0.0/16",
    "198.18.0.0/15",
    "198.51.100.0/24",
    "203.0.113.0/24",
    "::1/128",
    "fc00::/7",
    "fe80::/10"
    ],
    "outboundTag": "blocked"
    },
    // [routing-rule]
    // {
    // "type": "field",
    // "outboundTag": "force-ipv6", // force-ipv6 // force-ipv4 // socks5-warp
    // "domain": ["geosite:google"] // ***
    // },
    {
    "type": "field",
    "protocol": [
    "bittorrent"
    ],
    "outboundTag": "blocked"
    }
    ]
    }
    }
    root@1444685184woiden:~#

    回复删除
  37. 这个是我的caddy


    root@1444685184woiden:~# cat /etc/caddy/Caddyfile
    lokou.lokou.ml
    {
    tls Y3JhenlwZWFjZQ@gmail.com
    encode gzip

    # 多用户 多path
    # import Caddyfile.multiuser

    handle_path /9eaf4a169dac {
    reverse_proxy localhost:54703
    }
    handle {
    reverse_proxy https://zelikk.blogspot.com {
    trusted_proxies 0.0.0.0/0
    header_up Host {upstream_hostport}
    }
    }
    }

    回复删除
  38. 我在查看我的v2rayu配置时发现level不一样,我导入的时候它由1变成0,然后我的alerted是查不到的

    回复删除
  39. 回复
    1. 说实话,你的情况我也觉得很奇怪。你能把root密码给我吗?我上去看一下。

      删除
  40. 回复
    1. 你好,现在应该正常了。我也没干啥,装了一步warp,设置了一下IPv6优先,重启了一下系统。把access.log和error.log清空了一下。
      我后悔没把access.log和error.log备份下来。现在只能猜测原因了。
      1. 是不是你为了跑github脚本,设置了DNS64?这样把系统的DNS设置搞坏了。所以数据到了v2ray再往外走的时候,走不动。

      删除
  41. 不过我还是想问下dns64是什么,什么情况下会出现这种情况

    回复删除
    回复
    1. 如果你对此没有印象,说明你应该没有弄过。看了一下前面的一个评论,也是装了warp就正常了。
      你就在脚本安装的最后一步把warp装了。这样会有一个ipv4出站的能力。
      我现在只能猜测是woiden-eu-2 的ipv6出口非常不好,只能靠warp的ipv4来做出口。

      删除
  42. 如果再碰到,该怎么办呢

    回复删除
  43. 可是我的cloudflare 的dns是用ipv6的,ipv4我是没有装过的,那装了ipv
    4也是能出站的吗

    回复删除

发表评论

The Hot3 in Last 30 Days