v2fly / v2ray-examples Goto Github PK
View Code? Open in Web Editor NEWv2ray-core 的模板们
v2ray-core 的模板们
”TCP + TLS 分流器“不香么?也可以用websocket+vless ,我也一直都是分流tcp+tls+vless和wss+tls+vless。
用的还不错。
VLESS over TCP with TLS + 回落 & 分流 to WebSocket 会更快??
大神分析一下,
可以做一个vless-ws-tls給cf(cdn)用吗.
试著用VLESS-TCP-TLS-WS改一个,回落到port 80有问题,而且速度比nginx-vless慢。
如果 nginx 采用正常配置(listen 443),在 Request Headers 可以获取到正常客户端 IP
但是如果用了回落(listen unix:/dev/shm/default.sock),则获取到的 IP 变成了 "unix"
请问有任何解决方法吗?
"inbounds": [
{
"port":65500,
"listen": "127.0.0.1",
"tag": "VLESS-in",
"protocol": "VLESS",
"settings": {
"clients": [
{
"id":"115bd9e3-7b7f-4628-b4f6-23004ce7ada9",
"alterId":0,
"level":0
}
],
"decryption": "none"
},
"streamSettings": {
"network": "ws",
"wsSettings": {
"path":"/cs"
}
}
},
{
"port":65501,
"listen": "127.0.0.1",
"tag": "VLESS-in",
"protocol": "VLESS",
"settings": {
"clients": [
{
"id":"d576b963-6a11-45f1-a89b-babe841f27f4",
"alterId":0,
"level":0
}
],
"decryption": "none"
},
"streamSettings": {
"network": "ws",
"wsSettings": {
"path":"/vless"
}
}
}
但是最后只有65501能搜到被开启了?请问何解谢谢。
2020/09/04 13:45:20 [Warning] [180504796] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vless/outbound: connection ends > v2ray.com/core/proxy/vless/outbound: failed to decode response header > v2ray.com/core/proxy/vless/encoding: failed to read response version > EOF
2020/09/04 13:45:53 [Warning] [491275247] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vless/outbound: connection ends > v2ray.com/core/proxy/vless/outbound: failed to decode response header > v2ray.com/core/proxy/vless/encoding: failed to read response version > EOF
2020/09/04 13:46:42 [Warning] [1208888797] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vless/outbound: connection ends > v2ray.com/core/proxy/vless/outbound: failed to decode response header > v2ray.com/core/proxy/vless/encoding: failed to read response version > EOF
2020/09/04 13:46:45 [Warning] [3620828823] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vless/outbound: connection ends > v2ray.com/core/proxy/vless/outbound: failed to decode response header > v2ray.com/core/proxy/vless/encoding: failed to read response version > websocket: close 1000 (normal)
2020/09/04 13:47:17 [Warning] [2925515764] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vless/outbound: connection ends > v2ray.com/core/proxy/vless/outbound: failed to decode response header > v2ray.com/core/proxy/vless/encoding: failed to read response version > EOF
{
"log": {
"access": "/var/log/v2ray/access.log",
"error": "/var/log/v2ray/error.log",
"loglevel": "warning"
},
"inbounds": [
{
"port": 443,
"protocol": "vless",
"settings": {
"clients": [
{
"id": "", // 填写你的 UUID
"level": 0
},
{
"id": "", // 填写你的 UUID
"level": 0
},
{
"id": "", // 填写你的 UUID
"level": 0
},
{
"id": "", // 填写你的 UUID
"level": 0
}
],
"decryption": "none",
"fallbacks": [
{
"dest": 80
},
{
"path": "/newjob", // 必须换成自定义的 PATH
"dest": 10000,
"xver": 1
}
]
},
"streamSettings": {
"network": "tcp",
"security": "tls",
"tlsSettings": {
"alpn": [
"http/1.1"
],
"certificates": [
{
"certificateFile": "", // 换成你的证书,绝对路径
"keyFile": "" // 换成你的私钥,绝对路径
}
]
}
}
},
{
"port": 10000,
"listen": "127.0.0.1",
"protocol": "vless",
"settings": {
"clients": [
{
"id": "", // 填写你的 UUID
"level": 0
},
{
"id": "", // 填写你的 UUID
"level": 0
},
{
"id": "", // 填写你的 UUID
"level": 0
},
{
"id": "", // 填写你的 UUID
"level": 0
}
],
"decryption": "none"
},
"streamSettings": {
"network": "ws",
"security": "none",
"wsSettings": {
"acceptProxyProtocol": true, // 提醒:若你用 Nginx/Caddy 等反代 WS,需要删掉这行
"path": "/newjob" // 必须换成自定义的 PATH,需要和上面的一致
}
}
}
],
"outbounds": [
{
"protocol": "freedom",
"settings": {}
},
{
"protocol": "freedom",
"settings": {
"domainStrategy": "UseIPv6"
},
"tag": "ipv6-out"
}
],
"routing": {
"domainStrategy": "AsIs",
"rules": [
{
"type": "field",
"outboundTag": "ipv6-out",
"domain": [
"geosite:google",
"geosite:netflix"
//"geosite:facebook"
]
}
]
}
}
{
"log": {
"loglevel": "warning"
},
"inbounds": [
{
"port": 1080,
"protocol": "socks",
"sniffing": {
"enabled": true,
"destOverride": ["http", "tls"]
},
"settings": {
"auth": "noauth",
"udp": false
}
},
{
"port": 1081,
"protocol": "http",
"sniffing": {
"enabled": true,
"destOverride": ["http", "tls"]
},
"settings": {
"auth": "noauth",
"udp": false
}
}
],
"outbounds": [
{
"protocol": "vless",
"settings": {
"vnext": [
{
"address": "domain",
"port": 443,
"users": [
{
"id": "6e01f4b4-22ba-cd12-6c16-3eb0b6cc3bee",
"level": 0,
"encryption": "none"
}
]
},
{
"address": "domain",
"port": 443,
"users": [
{
"id": "fd3afd2f-474b-81b4-4727-169c90073589",
"level": 0,
"encryption": "none"
}
]
},
{
"address": "domain",
"port": 443,
"users": [
{
"id": "5574f130-9446-4746-a426-d778369e9115",
"level": 0,
"encryption": "none"
}
]
}
]
},
"streamSettings": {
"network": "ws",
"security": "tls",
"wsSettings": {
"path": "/newjob"
}
},
"tag": "proxy-vless-out"
},
{
"protocol": "freedom",
"settings": {},
"tag": "direct"//直连
},
{
"protocol": "blackhole",
"settings": {},
"tag": "adblock"//广告过滤
}
],
"routing": {
"domainStrategy": "IPIfNonMatch",
"rules": [
{
"type": "field",
"outboundTag": "proxy-vless-out",
"domain": [
"geosite:google",
"domain:githubusercontent.com",
"domain:v2fly.org"
]
},
{
"type": "field",
"outboundTag": "direct",
"domain": [
"geosite:cn",// **大陆主流网站的域名
]
},
{
"type": "field",
"outboundTag": "adblock",
"domain": [
"geosite:category-ads-all"//包含了常见的广告域名,以及广告提供商的域名。
]
},
{
"type": "field",
"outboundTag": "direct",
"ip": [
"geoip:cn", // **大陆的 IP
"geoip:private" // 私有地址 IP,如路由器等
]
}
]
}
}
按模板配置后一直提示 配置文件照搬模板 只修改了path uuid 证书 域名 请问怎么解决
2020/09/01 12:06:40 [Warning] [2922928673] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vless/outbound: failed to find an available destination > v2ray.com/core/common/retry: [v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://n/62e9faad/): 520 Origin Error > websocket: bad handshake] > v2ray.com/core/common/retry: all retry attempts failed
这样写可以吗?
{
"listen": "127.0.0.1",
"port": 1053,
"protocol": "dokodemo-door",
"settings": {
"address": "127.0.0.1",
"port": 53,
"network": "tcp,udp",
"timeout": 0
}
}
如题vless是否支持多组id clients,测试的是开启多组id,就会无法连接,另,由vless直接回落到ws或者其他配置的时候,id是否需要保持为相同且唯一,望解答,谢谢
hi。
我看了这里https://github.com/v2fly/v2ray-examples/blob/master/VLESS-TCP-XTLS-WHATEVER/config_client/vless_tcp_xtls.json ,
vless_tcp_xtls.json文件有一点多余之处,那就是37-39行是多余的,完全可以删除。当然删除后,第36行末尾的逗号要去掉。
{
"log": {
"loglevel": "warning"
},
"inbounds": [
{
"port": 443,
"protocol": "vless",
"settings": {
"clients": [
{
"id": "d2fddbad-7962-4cab-bac4-8caeeb4a235c",
"level": 0,
"email": "[email protected]"
}
],
"decryption": "none",
"fallbacks": [
{
"dest": 80
},
{
"path": "/ccc",
"dest": 1234,
"xver": 1
}
]
},
"streamSettings": {
"network": "tcp",
"security": "tls",
"tlsSettings": {
"alpn": [
"http/1.1"
],
"certificates": [
{
"certificateFile": "/app/config/v2ray.crt",
"keyFile": "/app/config/v2ray.key"
}
]
}
}
},
{
"port": 1234,
"listen": "127.0.0.1",
"protocol": "vless",
"settings": {
"clients": [
{
"id": "d2fddbad-7962-4cab-bac4-8caeeb4a235c",
"level": 0,
"email": "[email protected]"
}
],
"decryption": "none"
},
"streamSettings": {
"network": "ws",
"security": "none",
"wsSettings": {
// "acceptProxyProtocol": true,
"path": "/ccc"
}
}
}
],
"outbounds": [
{
"protocol": "freedom"
}
]
}
nginx正常启动, 但v2ray启动提示443端口被占用
root@xxx-hk:~# /usr/local/bin/v2ray -config /usr/local/etc/v2ray/config.json
V2Ray 4.34.0 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.15.6 linux/amd64)
A unified platform for anti-censorship.
2021/03/03 00:22:17 [Info] v2ray.com/core/main/jsonem: Reading config: /usr/local/etc/v2ray/config.json
Failed to start v2ray.com/core/app/proxyman/inbound: failed to listen TCP on 443 > v2ray.com/core/transport/internet: failed to listen on address: 0.0.0.0:443 > v2ray.com/core/transport/internet/tcp: failed to listen TCP on 0.0.0.0:443 > listen tcp 0.0.0.0:443: bind: address already in use
端口占用情况
root@xxx-hk:~# lsof -i:443
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
google_gu 1610 root 6u IPv4 37193 0t0 TCP tranjonhk-ga-hk.asia-east2-a.c.copper-cider-305907.internal:45958->hkg07s28-in-f10.1e100.net:https (ESTABLISHED)
nginx 6792 root 8u IPv4 36957 0t0 TCP *:https (LISTEN)
nginx 6797 www-data 8u IPv4 36957 0t0 TCP *:https (LISTEN)
nginx 6798 www-data 8u IPv4 36957 0t0 TCP *:https (LISTEN)
以前是vless,现在v5的vless页面说vless弃用了推荐用Trojan代替。那么现在最推荐的方案难道是Trojan吗?能不能更新一下v5推荐方案的模板?
VMESS(VLESS)+WS+TLS+NGINX (麻烦把nginx的配置也写出来)
VMESS(VLESS)+WS+TLS (不含NGINX但加入path)
网络上关于mkcp+seed的模板很少
您好,搞了好久,不能自我解决,只好发问如下:
1)GOOGLE CLOULD上装了VLESS,用的是wulabing/V2Ray_ws-tls_bash_onekey的脚本。
2)今天按您的VLESS over TCP with XTLS + 回落 & 分流 to WHATEVER(终极配置)样本,修改V2RAY配置文件后出现:
root@ssrothk:~# sudo systemctl status v2ray
● v2ray.service - V2Ray Service
Loaded: loaded (/etc/systemd/system/v2ray.
Active: failed (Result: exit-code) since F
Process: 3043 ExecStart=/usr/local/bin/v2ra
Main PID: 3043 (code=exited, status=255/EXCE
Nov 20 14:04:53 ssrothk systemd[1]: v2ray.ser
Nov 20 14:04:53 ssrothk systemd[1]: v2ray.ser
lines 1-8...skipping...
● v2ray.service - V2Ray Service
Loaded: loaded (/etc/systemd/system/v2ray.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2020-11-20 14:04:53 UTC; 7s ago
Process: 3043 ExecStart=/usr/local/bin/v2ray -config /etc/v2ray/config.json (code=exited, status=255/EXCEPTION)
Main PID: 3043 (code=exited, status=255/EXCEPTION)
Nov 20 14:04:53 ssrothk systemd[1]: v2ray.service: Main process exited, code=exited, status=255/EXCEPTION
Nov 20 14:04:53 ssrothk systemd[1]: v2ray.service: Failed with result 'exit-code'.
Nov 20 14:04:53 ssrothk systemd[1]: v2ray.service: Service RestartSec=100ms expired, scheduling restart.
Nov 20 14:04:53 ssrothk systemd[1]: v2ray.service: Scheduled restart job, restart counter is at 5.
Nov 20 14:04:53 ssrothk systemd[1]: Stopped V2Ray Service.
Nov 20 14:04:53 ssrothk systemd[1]: v2ray.service: Start request repeated too quickly.
Nov 20 14:04:53 ssrothk systemd[1]: v2ray.service: Failed with result 'exit-code'.
Nov 20 14:04:53 ssrothk systemd[1]: Failed to start V2Ray Service.
3)我已将样本中所有注释删除。如下:
{
"log": {
"loglevel": "warning"
},
"inbounds": [
{
"port": 443,
"protocol": "vless",
"settings": {
"clients": [
{
"id": "5aad5140-dfc4-46be-9dc7-dbbf11dd5e11",
"flow": "xtls-rprx-direct",
"level": 0,
"email": "[email protected]"
}
],
"decryption": "none",
"fallbacks": [
{
"dest": 1310,
"xver": 1
},
{
"path": "/39b3b19b902aa/",
"dest": 1234,
"xver": 1
},
{
"path": "/39b3b19b902aa/",
"dest": 2345,
"xver": 1
},
{
"path": "/39b3b19b902aa/",
"dest": 3456,
"xver": 1
}
]
},
"streamSettings": {
"network": "tcp",
"security": "xtls",
"xtlsSettings": {
"alpn": [
"http/1.1"
],
"certificates": [
{
"certificateFile": "/root/.acme.sh/pearl.isaacserman.xyz_ecc/pearl.isaacserman.xyz.cer",
"keyFile": "/root/.acme.sh/pearl.isaacserman.xyz_ecc/pearl.isaacserman.xyz.key"
}
]
}
}
},
{
"port": 1310,
"listen": "127.0.0.1",
"protocol": "trojan",
"settings": {
"clients": [
{
"password": "",
"level": 0,
"email": "[email protected]"
}
],
"fallbacks": [
{
"dest": 80
}
]
},
"streamSettings": {
"network": "tcp",
"security": "none",
"tcpSettings": {
"acceptProxyProtocol": true
}
}
},
{
"port": 1234,
"listen": "127.0.0.1",
"protocol": "vless",
"settings": {
"clients": [
{
"id": "5aad5140-dfc4-46be-9dc7-dbbf11dd5e11",
"level": 0,
"email": "[email protected]"
}
],
"decryption": "none"
},
"streamSettings": {
"network": "ws",
"security": "none",
"wsSettings": {
"acceptProxyProtocol": true,
"path": "/39b3b19b902aa/"
}
}
},
{
"port": 2345,
"listen": "127.0.0.1",
"protocol": "vmess",
"settings": {
"clients": [
{
"id": "5aad5140-dfc4-46be-9dc7-dbbf11dd5e11",
"level": 0,
"email": "[email protected]"
}
]
},
"streamSettings": {
"network": "tcp",
"security": "none",
"tcpSettings": {
"acceptProxyProtocol": true,
"header": {
"type": "http",
"request": {
"path": [
"/39b3b19b902aa/"
]
}
}
}
}
},
{
"port": 3456,
"listen": "127.0.0.1",
"protocol": "vmess",
"settings": {
"clients": [
{
"id": "5aad5140-dfc4-46be-9dc7-dbbf11dd5e11",
"level": 0,
"email": "[email protected]"
}
]
},
"streamSettings": {
"network": "ws",
"security": "none",
"wsSettings": {
"acceptProxyProtocol": true,
"path": "/39b3b19b902aa/"
}
}
}
],
"outbounds": [
{
"protocol": "freedom"
}
]
}
还烦请赐教!
https://github.com/v2fly/v2ray-examples/blob/master/Shadowsocks-TCP/client.json
範例中,address 的IP 可以有 "", 但port裡面不能有""。
"protocol": "shadowsocks",
"settings": {
"servers": [
{
"address": "{{ host }}",
"port": "{{ port }}",
"method": "chacha20-ietf-poly1305",
"password": "{{ password}}"
}
]
https://github.com/XTLS/Xray-examples/blob/main/VLESS-TCP-XTLS-WHATEVER/config_server.json
按照上面这个教程 使用v2ray 核心
Vless tcp fallback to vmess tcp and vmess ws
vmess ws 是可以正常工作的, 但vmess 的 tcp 里面带path /vmesstcp 就无法连接
用脚本 bash <(curl -Lso- https://git.io/oneclick) 安装选13 就可以安装 vless fallback to vmess tcp 可以重现问题
印象中以前是可以的,不知道哪个版本后就不行了
Hi I have a website with the following server side configuration already working:
CDN -> Apache Web Server (reverse proxy) -> V2Ray Docker Container (port forwarding) -> V2ray with VMess protocol.
I want to try out VLESS. How should I modify my VMess conf file to make it work?
I've look through all the examples, they are not really helpful in my case. They all sort of exposing VLESS directly in the front, which is not my use case. I am particularly confused with the "fallback" setting in my situation.
{
"inbounds": [
{
"port": 1087,
"protocol": "vmess",
"settings": {
"clients": [
{
"id": "",
"alterId": 128
}
]
},
"streamSettings": {
"network": "ws",
"wsSettings": {
"path": "/my_masked_path"
}
}
}
],
"outbounds": [
{
"protocol": "freedom",
"settings": {}
}
]
}
请问这种方案如何配置多用户?我根据模板配置了一下没成功。
我创建了两个用户,"email“:a和"email“:b。
"email“:a id为 40d3d26c-bf99-40c8-938d-8189d6e0ad5d
"email“:b id为 40d3d26c-bf99-40c8-938d-8189d6e0ad5e
这是我尝试的第一种配置
{
"log": {
"loglevel": "warning"
},
"inbounds": [
{
"port": 443,
"protocol": "vless",
"settings": {
"clients": [
{
"id": "40d3d26c-bf99-40c8-938d-8189d6e0ad5d",
"level": 0,
"email": "a"
},
{
"email": "b",
"id": "40d3d26c-bf99-40c8-938d-8189d6e0ad5e",
"level": 0
}
],
"decryption": "none",
"fallbacks": [
{
"dest": 80
},
{
"path": "/z000",
"dest": 1234,
"xver": 1
},
{
"path": "/z001",
"dest": 1235,
"xver": 1
}
]
},
]
},
"streamSettings": {
"network": "tcp",
"security": "tls",
"tlsSettings": {
"alpn": [
"http/1.1"
],
"certificates": [
{
"certificateFile": "/home/cert.pem",
"keyFile": "/home/key.pem"
}
]
}
}
},
{
"port": 1234,
"listen": "127.0.0.1",
"protocol": "vless",
"settings": {
"clients": [
{
"id": "40d3d26c-bf99-40c8-938d-8189d6e0ad5d",
"level": 0,
"email": "a"
}
],
"decryption": "none"
},
"streamSettings": {
"network": "ws",
"security": "none",
"wsSettings": {
"acceptProxyProtocol": true,
"path": "/z000"
}
}
},
{
"port": 1235,
"listen": "127.0.0.1",
"protocol": "vless",
"settings": {
"clients": [
{
"id": "40d3d26c-bf99-40c8-938d-8189d6e0ad5e",
"level": 0,
"email": "b"
}
],
"decryption": "none"
},
"streamSettings": {
"network": "ws",
"security": "none",
"wsSettings": {
"acceptProxyProtocol": true,
"path": "/z001"
}
}
}
],
"outbounds": [
{
"protocol": "freedom"
}
]
}
这是我尝试的第二种配置
{
"log": {
"loglevel": "warning"
},
"inbounds": [
{
"port": 443,
"protocol": "vless",
"settings": {
"clients": [
{
"id": "40d3d26c-bf99-40c8-938d-8189d6e0ad5d",
"level": 0,
"email": "a"
},
{
"email": "b",
"id": "40d3d26c-bf99-40c8-938d-8189d6e0ad5e",
"level": 0
}
],
"decryption": "none",
"fallbacks": [
{
"dest": 80
},
{
"path": "/z000",
"dest": 1234,
"xver": 1
}
]
},
]
},
"streamSettings": {
"network": "tcp",
"security": "tls",
"tlsSettings": {
"alpn": [
"http/1.1"
],
"certificates": [
{
"certificateFile": "/home/cert.pem",
"keyFile": "/home/key.pem"
}
]
}
}
},
{
"port": 1234,
"listen": "127.0.0.1",
"protocol": "vless",
"settings": {
"clients": [
{
"id": "40d3d26c-bf99-40c8-938d-8189d6e0ad5d",
"level": 0,
"email": "a"
},
{
"email": "b",
"id": "40d3d26c-bf99-40c8-938d-8189d6e0ad5e",
"level": 0
}
],
"decryption": "none"
},
"streamSettings": {
"network": "ws",
"security": "none",
"wsSettings": {
"acceptProxyProtocol": true,
"path": "/z000"
}
}
}
],
"outbounds": [
{
"protocol": "freedom"
}
]
}
我是瞎搞的,不知道怎么弄才能成功,请大佬点拨,谢谢。
需要一个VMess-TCP-Fullcone的模板
对您的**VLESS-TCP-TLS-WS (recommended)**感兴趣,原来是ws + nginx and/or cdn; 是否可以顺便提供个简单的nginx参考呢?原来是在nginx进行tls验证转发到v2ray / 静态网页的;
Hello
Is is possible to provide the new gRPC examples?
Thanks
我客户端是ubuntu desktop
/etc/vray/config.json:
照抄了 https://github.com/v2fly/v2ray-examples/blob/master/VLESS-TCP-TLS%20(maximal%20by%20rprx)/config_client.json
{
"log": {
"loglevel": "warning"
},
"inbounds": [
{
"port": 10800,
"listen": "127.0.0.1",
"protocol": "socks",
"settings": {
"udp": true
}
}
],
"outbounds": [
{
"protocol": "vless",
"settings": {
"vnext": [
{
"address": "example.com", // 换成你的域名或服务器 IP(发起请求时无需解析域名了)
"port": 443,
"users": [
{
"id": "", // 填写你的 UUID
"encryption": "none",
"level": 0
}
]
}
]
},
"streamSettings": {
"network": "tcp",
"security": "tls",
"tlsSettings": {
"serverName": "example.com" // 换成你的域名
}
}
}
]
}
上面我改了我该填的东西 然后
sudo docker run -d --name v2ray -v /etc/v2ray:/etc/v2ray -p 10800:10800/tcp -p 10800:10800/udp v2fly/v2fly-core v2ray -config=/etc/v2ray/config.json
然后在chrome上 在 swithcomage上设置了 127.0.0.1 10800 ,但是还是不行
我是ubuntu,服务端没问题的,服务端 是 v2fly vless tcp tls,Windows上用 v2rayng一点问题也没有
{
"log": {
"access": "/var/log/v2ray/access.log",
"error": "/var/log/v2ray/error.log",
"loglevel": "info"
},
"inbounds": [
{
"port": 443,
"protocol": "vless",
"settings": {
"clients": [
{
"id": "uuid", // 填写你的 UUID
"level": 0,
"email": "email"
}
],
"decryption": "none",
"fallbacks": [
{
"dest": "/dev/shm/default.sock",
"xver": 1
},
{
"alpn": "h2",
"dest": "/dev/shm/h2c.sock",
"xver": 1
}
]
},
"streamSettings": {
"network": "tcp",
"security": "tls",
"tlsSettings": {
"alpn": [
"h2",
"http/1.1"
],
"certificates": [
{
"certificateFile": "/etc/ssl/v2ray/one.crt", // 换成你的证书,绝对路径
"keyFile": "/etc/ssl/v2ray/one.key" // 换成你的私钥,绝对路径
}
]
}
}
}
],
"outbounds": [
{
"protocol": "freedom"
}
]
}
server {
#listen 80 default_server;
#listen [::]:80 default_server;
listen [::]:80 ipv6only=off;
return 301 https://$http_host$request_uri;
}
server {
listen unix:/dev/shm/default.sock proxy_protocol;
listen unix:/dev/shm/h2c.sock http2 proxy_protocol;
set_real_ip_from 127.0.0.1;
server_name example.com;
root /var/www/html/wordpress;
index index.php index.html index.htm;
location = /favicon.ico {
log_not_found off;
access_log off;
}
location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}
location / {
# This is cool because no php is touched for static content
try_files $uri $uri/ /index.php?$args;
}
location ~ \.php$ {
include fastcgi_params;
fastcgi_intercept_errors on;
fastcgi_pass unix:/var/run/php/php7.4-fpm.sock;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
}
location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
expires max;
log_not_found off;
}
}
unix: - - [30/Oct/2020:01:50:46 -0400] "GET / HTTP/2.0" 301 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36" "-"myip:port
unix: - - [30/Oct/2020:01:50:46 -0400] "GET /wp-login.php HTTP/2.0" 302 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36" "-"myip:port
v2ray日志
2020/10/30 02:45:42 [Info] [2341473557] v2ray.com/core/proxy/vless/inbound: firstLen = 70
2020/10/30 02:45:42 [Info] [2341473557] v2ray.com/core/proxy/vless/inbound: fallback starts > v2ray.com/core/proxy/vless/encoding: invalid request version
2020/10/30 02:45:42 [Info] [2341473557] v2ray.com/core/proxy/vless/inbound: realAlpn = h2
v2ray-examples/VLESS-TCP-XTLS-WHATEVER/config_server.json
Lines 80 to 91 in cd71d22
v2ray-examples/VLESS-TCP-XTLS-WHATEVER/config_server.json
Lines 109 to 120 in cd71d22
因为VLESS协议不加密,如果采用VLESS over ws,with TLS + CDN方案,CDN厂商是否能够看到ws协议承载的原始未加密VLESS数据,从而轻而易举知道该上游服务器为V2RAY服务器?CDN厂商作为一个中间人,到底看到的是原始VLESS数据,还是TLS保护下的数据?小弟这点始终没想得很明白,望大佬帮忙解释下!
https://github.com/v2fly/v2ray-examples/blob/master/VLESS-TCP/config_client.json
in this config file line 30,it's shouldn't be "user": [ ,instead of it,it's "users": [
我用的是VLESS-TCP-TLS (minimal by rprx)这个模板
默认开启TLS1.0 TLS1.1导致
在Qualys SSL Labs's SSL Server Test测试的成绩是B
请问如何禁用TLS1.0 TLS1.1
vps: CentOS8
caddy version: v2.1.1 h1:X9k1+ehZPYYrSqBvf/ocUgdLSRIuiNiMo7CvyGUQKeA=
Caddyfile
my domain {
root * /usr/share/caddy
file_server
reverse_proxy /path 127.0.0.1:25668 {
transport http {
versions h2c
}
}
}
config.json
{
"log": {
"loglevel": "warning"
},
"inbounds": [
{
"port": 25668,
"listen": "127.0.0.1",
"protocol": "vless",
"settings": {
"clients": [
{
"id": "6a5d43bd-c74a-4f36-87f5-7c2c46338dc0",
"email": "[email protected]"
}
]
},
"streamSettings": {
"security": "none",
"network": "h2",
"httpSettings": {
"path": "/mysite",
"host": [
"my domain"
]
}
}
}
],
"outbounds": [
{
"tag": "direct",
"protocol": "freedom",
"settings": {}
},
{
"tag": "blocked",
"protocol": "blackhole",
"settings": {}
}
],
"routing": {
"domainStrategy": "AsIs",
"rules": [
{
"type": "field",
"ip": [
"geoip:private"
],
"outboundTag": "blocked"
}
]
}
}
伪装的网站可以正常访问, 但是v2ray报错
systemctl status v2ray
● v2ray.service - V2Ray Service
Loaded: loaded (/etc/systemd/system/v2ray.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2020-08-25 14:22:53 UTC; 969ms ago
Process: 116917 ExecStart=/usr/local/bin/v2ray -config /usr/local/etc/v2ray/config.json (code=exited, status=23)
Main PID: 116917 (code=exited, status=23)
Aug 25 14:22:53 sksmg systemd[1]: v2ray.service: Service RestartSec=100ms expired, scheduling restart.
Aug 25 14:22:53 sksmg systemd[1]: v2ray.service: Scheduled restart job, restart counter is at 5.
Aug 25 14:22:53 sksmg systemd[1]: Stopped V2Ray Service.
Aug 25 14:22:53 sksmg systemd[1]: v2ray.service: Start request repeated too quickly.
Aug 25 14:22:53 sksmg systemd[1]: v2ray.service: Failed with result 'exit-code'.
Aug 25 14:22:53 sksmg systemd[1]: Failed to start V2Ray Service.
status=23是指23行有错吗? 23行是path, 我检查了没有错. 想知道解决办法, 望大佬答复, 不胜感激!
使用了VLESS over TCP with TLS + 回落(建站配置)
这个模板,但是因为服务器上不止一个站点,所以在/etc/nginx/conf.d/
目录下配置了其他站点,但是会证书错误,发现用的还是v2ray
上配置的伪装域名证书。试过站点配置如下(非nginx
主配置文件)
server
{
listen 80;
listen [::]:80;
server_name XXX;
return 301 https://XXX$request_uri;
}
server
{
listen unix:/dev/shm/default.sock proxy_protocol;
listen unix:/dev/shm/h2c.sock http2 proxy_protocol;
server_name XXX;
root /usr/share/nginx/html;
set_real_ip_from 127.0.0.1;
# 异想天开加了一段SSL配置,结果没有用
ssl_certificate "XXX.cer";
ssl_certificate_key "XXX.key";
ssl_session_timeout 10m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:HIGH:!aNULL:!MD5:!RC4:!DHE;
ssl_prefer_server_ciphers on;
ssl_session_cache builtin:1000 shared:SSL:10m;
location / {
}
location ~ /\. {
deny all;
}
}
所以想请教一下这种情况应该如何配置呢?还是说只能把前端web
服务器换回nginx
呢?
我自己试了一下配置 outbound 但不成功,谁指点我一下
{
"protocol": "vless",
"settings": {
"vnext": [
{
"address": "example.com",
"port": 443,
"users": [
{
"encryption": "none",
"id": "uuid"
}
]
}
]
},
"streamSettings": {
"transport": "httpupgrade",
"transportSettings": {
"path": "/path",
"host": "example.com"
},
"security": "tls",
"tlsSettings": {
"serverName": "example.com"
}
},
"tag": "proxy"
}
os: debian10
nginx: 1.14.2
v2ray: 4.29.0
内部网络结构:
v2ray(443) -> nginx(http1.1) - (反代) - > web程序
\ /
nginx(http2)
v2ray 与 nginx 配置参考 VLESS over TCP with TLS + 回落(建站配置)
nginx: nginx.conf
user www-data;
worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;
events {
use epoll;
worker_connections 768;
multi_accept on;
}
http {
##
# Basic Settings
##
sendfile on;
tcp_nopush on;
tcp_nodelay on;
types_hash_max_size 2048;
server_tokens off;
##
# Timeout Settings
##
keepalive_timeout 10;
client_header_timeout 10;
client_body_timeout 10;
reset_timedout_connection on;
send_timeout 10;
# server_names_hash_bucket_size 64;
# server_name_in_redirect off;
include /etc/nginx/mime.types;
default_type application/octet-stream;
##
# Logging Settings
##
access_log off;
# access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log;
##
# SSL Settings
##
#ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
#ssl_prefer_server_ciphers on;
#ssl_session_cache shared:SSL:5m;
#ssl_session_timeout 20m;
#ssl_session_tickets on;
##
# Gzip Settings
##
gzip on;
gzip_disable "MSIE [1-6]";
gzip_vary on;
gzip_static on;
gzip_proxied any;
gzip_comp_level 2;
gzip_buffers 4 16k;
gzip_http_version 1.1;
gzip_types text/plain application/javascript application/x-javascript text/javascript text/xml text/css;
##
# Cache config
##
proxy_connect_timeout 5;
proxy_read_timeout 60;
proxy_send_timeout 5;
proxy_buffer_size 16k;
proxy_buffers 4 64k;
proxy_busy_buffers_size 128k;
proxy_temp_file_write_size 128k;
proxy_temp_path /home/temp_dir;
proxy_cache_path /home/cache levels=1:2 keys_zone=cache_one:200m inactive=1d max_size=30g;
proxy_headers_hash_max_size 51200;
proxy_headers_hash_bucket_size 6400;
##
# Virtual Host Configs
##
server {
listen 80 default;
server_name _;
return 403;
}
include vhost/*.conf;
}
nginx: vhost/example.com.conf
server {
listen 80;
server_name example.com another.example.com;
return 301 https://$http_host$request_uri;
}
server {
listen port1 proxy_protocol;
listen port2 http2 proxy_protocol;
server_name example.com another.example.com;
set_real_ip_from 127.0.0.1;
real_ip_header proxy_protocol;
location / {
proxy_set_header HOST $host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Real-IP $proxy_protocol_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-For $proxy_protocol_addr;
proxy_pass http://127.0.0.1:xxxx/;
}
}
v2ray: config.json
{
"inbounds": [{
"port": 443,
"protocol": "vless",
"settings": {
"clients": [{
"id": "uuid",
"flow": "xtls-rprx-origin"
}],
"decryption": "none",
"fallbacks": [{
"dest": port1,
"xver": 1
},
{
"alpn": "h2",
"dest": port2,
"xver": 1
}, {
"path": "/wspath",
"dest": port3
}
]
},
"streamSettings": {
"network": "tcp",
"security": "xtls",
"xtlsSettings": {
"alpn": [
"h2",
"http/1.1"
],
"certificates": [{
"certificateFile": "/xxx/fullchain.cer",
"keyFile": "/xxx/example.com.key"
}]
}
}
}, {
"port": 10000,
"listen": "127.0.0.1",
"protocol": "vmess",
"settings": {
"clients": [{
"id": "uuid"
}]
},
"streamSettings": {
"network": "ws",
"security": "none",
"wsSettings": {
"path": "/wspath"
}
}
}],
"outbounds": [{
"protocol": "freedom",
"settings": {}
},
{
"protocol": "blackhole",
"settings": {},
"tag": "block"
}
],
"routing": {
"domainStrategy": "AsIs",
"rules": [{
"type": "field",
"outboundTag": "block",
"domain": [
"geosite:cn",
"geosite:category-ads-all"
]
}, {
"type": "field",
"outboundTag": "block",
"protocol": [
"bittorrent"
]
}]
}
}
test.example.com
) 均可完成对网站的访问(即nginx的域名限制没有起到作用)开发者辛苦了,感谢回复!
nginx配置文件总是配不对,启动提示80、443端口被占用
最优质的稳定科学上网方法:科学上网方法推荐
【实战分享】ChatGPT注册登录经验:ChatGPT注册登录指南
感谢支持fallback功能。之前一直把trojan-gfw做外层,回落 v2ray使用达到共存。现在我想使用v2ray里的trojan协议达到类似效果:
尝试了一下外层是vless xtls,回落里面填写了 h2,ws,trojan. 最外层基本的vless xtls工作正常
如果把trojan的回落开启,path留空,用trojan尝试连接则服务端报错 not trojan request. //是不是trojan只能工作在最外层?
把trojan随便填个path禁用掉(trojan不支持path),则30086端口的vmess websocket可以正常工作;10086端口的h2还是不能工作,已经在alpn和xtls的alpn里都启用了h2。
我看到教程里写了 (非空则必须以 "/" 开头,不支持 h2c。) 也就是说回落是不支持h2的么?
如果要并存的话,是不是必须 trojan 外层,然后回落到 TLS的 vless和 vmess. 那么h2可以实现回落么?
"fallbacks": [
{
"alpn": "",
"path": "",
"dest": 80,
"xver": 0
},
{ "path": "/tro", // trojan 暂时禁用
"dest": 4433,
"xver":1
},
{
"path": "/dodo", // vmess ws 兼容
"dest": 30086,
"xver": 1
},
{ "alpn":"h2",
"path": "/fat",
"dest": 10086,
"xver": 1
}
]
I tried using Google Translate, but it says there is a syntax error:
%% Please use double quotation marks for large sections of text, otherwise characters such as Chinese punctuation cannot be used
%% text supports HTML syntax, such as line break, please use<br>
%% supports Font Awesome icon
%% For more syntax, please refer to [Mermaid Flowchart Grammar](https://mermaidjs.github.io/flowchart.html)
graph TB
tag (fa: fa-tag ver. 1.1)
style tag fill: #0000000a, stroke: #bfbfbf
start["How to choose V2Ray solution fa:fa-rocket"] -->
simple-way? (-"Mengxin? Too lazy to toss? Hurry to use?"-)
simple-way? -->
|No| speed? (-"Do you want speed? Or do you want stability?"-)
simple-way? -->
|Yes | buy["Buy, buy, buy! Please search for paid VPN SS V2Ray<br>Convenient, fast, time-saving and labor-saving!"]
speed? --> |Stable| worry-sniff?(-"Mind if it may be detected that you are using V2Ray?"-)
speed? --> |速度| kcp["fa:fa-star KCP"]
%% speed branch
kcp --> more-speed?(-"The speed of KCP alone is not ideal? Want to try a more complicated configuration?"-)
more-speed? -->
|Yes| kcp-udp2raw["fa:fa-star fa:fa-star fa:fa-star try KCP + udp2raw<br><i>*Note that udp2raw is difficult to use on the mobile client</i>"]
kcp-udp2raw --> more-more-speed? (-"Still not strong?"-)
more-more-speed? -->
|"Yes! I feel cheated!"| tcp-bbr["
fa:fa-star fa:fa-star fa:fa-star Adjust KCP parameters or try TCP + BBR<br>
<i>*Note that BBR requires specific system support, please refer to related tutorials. </i><br>
<i>Because it is a low-level unilateral algorithm, it can be combined with other options.</i>
"]
%% stable branch
worry-sniff? -->
|Don’t worry about anything else | tcp-vmess["fa:fa-star TCP + Vmess"]
worry-sniff? -->
|Work secretly| have-website?(-"How to build a website?<br>A website is already running on the server?"-)
have-website? -->
|"No, I don't understand and don't want to understand"| ws-or-obfu["fa:fa-star WebSocket, HTTP/2 or Vmess + disguise"]
have-website? -->
|"Yes! Coach! I want to learn this!"| https?(-"Want to hide V2Ray further?<br>Does the website support HTTPS?"-)
https? -->
|It’s always better to be safer| https-website["
fa:fa-star fa:fa-star Caddy + TLS + WebSocket、HTTP/2<br>
fa:fa-star fa:fa-star fa:fa-star Nginx/Apache/其它 + TLS + WebSocket、HTTP/2
"]
https? -->
|"Forget it, too much trouble"| website["fa:fa-star fa:fa-star Caddy/Nginx/Apache/Other + WebSocket"]
website --> cdn?
https-website --> cdn?
cdn?(-"Want to protect the host IP from being killed?<br>Even though the speed may be affected indefinitely?"-) -->
|"Yes, a bit more stable is a bit"| cdn["fa:fa-star fa:fa-star Cloudflare and other CDNs<br><i>*Note that this difficulty level belongs to CDN</i>"]
note("<i>
fa:fa-star represents the level of complexity, the more fa:fa-star, the more complicated, the more difficult it is
Some options in speed classification and stability classification can be used in combination<br>
To participate in the modification of this picture, please go to github.com/v2fly/vTemplate
</i>")
style note stroke-width:2px, stroke-dasharray: 5.5
我在 vultr 的服务器上把 /etc/v2ray/config.json 改成 VMess-TCP 的 config_server.json,然后 systemctl start v2ray,然后 systemctl status v2ray 显示正常运行;
在 v2rayNG (Google play 里下载的) 导入自定义配置 config_client.json,测试连接,有时候显示延时七八百毫秒,有时候显示 contet deadline exceeded,但是不管哪种情况浏览器都上不了网。
其他客户端没试过。
config_server.json 改了 id;config_client.json 改了 address 和 id;其他都没改。
在VPS上按VLESS-TCP-TLS模板配置了v2ray,用了没几天端口就被封了。psping <ip>:<port>
无法建立连接,需要换一个端口才能工作。请问有什么办法使"VLESS-TCP-TLS"的配置能保持长期稳定可用?
同样的服务器,当v2ray处理TLS时,就会变得极其不稳定,但是换用caddy处理TLS就稳定许多,包括trojan,只要v2ray 处理TLS就会慢和不稳定,感觉现在限制vless扩大使用的就是TLS处理性能了
VLESS 仍在不断变化,务必确保两边的 v2ray-core 均为最新版本(很多问题最后发现是没有升级版本)。
这里不是客服区,也没有客服。问题需要有建设性,或者你认为是 BUG 等,而不是不会配置/不会使用。
最终提出问题前,你应当先仔细地读完 VLESS 的文档:https://www.v2fly.org/config/protocols/vless.html
你应当先广泛地搜索类似的问题,提出问题时应当详细地描述场景,并一次性附上所有相关配置及日志。
目前的vless协议如何配置负载均衡?
// {
// "protocol": "vless",
// "settings": {
// "vnext": [
// {
// "address": "domain",
// "port": 443,
// "users": [
// {
// "id": "6e01f4b4-22ba-cd12-6c16-3eb0b6cc3bee",
// "level": 0,
// "encryption": "none"
// }
// ]
// },
// {
// "address": "domain",
// "port": 443,
// "users": [
// {
// "id": "fd3afd2f-474b-81b4-4727-169c90073589",
// "level": 0,
// "encryption": "none"
// }
// ]
// },
// {
// "address": "domain",
// "port": 443,
// "users": [
// {
// "id": "5574f130-9446-4746-a426-d778369e9115",
// "level": 0,
// "encryption": "none"
// }
// ]
// }
// ]
// },
// "streamSettings": {
// "network": "tcp",
// "security": "tls"
// },
// "tag": "proxy-vless-out"
// },
像这种好像是可以实现负载,但使用不了CDN。如果要使用CDN该如何配置才能实现负载均衡呢?
路由负载均衡的使用找不到具体的相关文档。搜索引擎里也找不到具体的应用方案。期待 examples 中给出一个具体的应用示例。谢谢!
config ===================
{
"log": {
"loglevel": "warning"
},
"routing": {
"domainStrategy": "AsIs",
"rules": [
{
"type": "field",
"ip": [
"geoip:private"
],
"tag": "direct"
}
]
},
"inbounds": [
{
"listen": "127.0.0.1",
"port": "1080",
"protocol": "socks",
"settings": {
"auth": "noauth",
"udp": true,
"ip": "127.0.0.1"
}
},
{
"listen": "127.0.0.1",
"port": "1081",
"protocol": "http"
}
],
"outbounds": [
{
"protocol": "vmess",
"settings": {
"vnext": [
{
"address": "15...01",
"port": 443,
"user": [
{
"id": "db280...ca363",
"alterId": 4,
"security": "no",
"testsEnabled": "VMessAEAD"
}
]
}
]
},
"streamSettings": {
"network": "tcp"
},
"tag": "proxy"
},
{
"protocol": "freedom",
"tag": "direct"
}
]
}
Nginx ===============================
server {
listen 443 ssl;
listen [::]:443 ssl;
ssl_certificate /etc/v2ray/v2ray.crt;
ssl_certificate_key /etc/v2ray/v2ray.key;
ssl_session_timeout 1d;
ssl_session_cache shared:MozSSL:10m;
ssl_session_tickets off;
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers ECDH...-SHA384;
ssl_prefer_server_ciphers off;
server_name $HOSTNAME;
root /var/www/$HOSTNAME/html;
# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;
location /ray {
proxy_redirect off;
proxy_pass http://127.0.0.1:10000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
# Show real IP in v2ray access.log
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
结果======================================
● v2ray.service - V2Ray Service
Loaded: loaded (/etc/systemd/system/v2ray.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/v2ray.service.d
└─10-donot_touch_single_conf.conf
Active: failed (Result: exit-code) since Sat 2020-09-26 04:42:45 UTC; 5s ago
Docs: https://www.v2fly.org/
Process: 4094 ExecStart=/usr/local/bin/v2ray -config /usr/local/etc/v2ray/config.json (code=exited, status=255/EXCEPTI>
Main PID: 4094 (code=exited, status=255/EXCEPTION)
Sep 26 04:42:45 seo....com systemd[1]: v2ray.service: Main process exited, code=exited, status=255/EXCEPTION
Sep 26 04:42:45 seo....com systemd[1]: v2ray.service: Failed with result 'exit-code'.
Sep 26 04:42:45 seo....com systemd[1]: v2ray.service: Scheduled restart job, restart counter is at 5.
Sep 26 04:42:45 seo....com systemd[1]: Stopped V2Ray Service.
Sep 26 04:42:45 seo....com systemd[1]: v2ray.service: Start request repeated too quickly.
Sep 26 04:42:45 seo....com systemd[1]: v2ray.service: Failed with result 'exit-code'.
Sep 26 04:42:45 seo....com systemd[1]: Failed to start V2Ray Service.
Sep 26 04:42:50 seo....com systemd[1]: v2ray.service: Start request repeated too quickly.
Sep 26 04:42:50 seo....com systemd[1]: v2ray.service: Failed with result 'exit-code'.
Sep 26 04:42:50 seo....com systemd[1]: Failed to start V2Ray Service.
lines 1-19/19 (END)
日志 ====================================
run journalctl -xe
Sep 26 04:05:03 seo....com systemd[885]: Reached target Main User Target.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 1.
Sep 26 04:05:03 seo....com systemd[885]: Startup finished in 96ms.
-- Subject: User manager start-up is now complete
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The user manager instance for user 1000 has been started. All services queued
-- for starting have been started. Note that other services might still be starting
-- up or be started at any later time.
--
-- Startup of the manager took 96882 microseconds.
Sep 26 04:05:19 seoul.sayhey.cyou sudo[991]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
Sep 26 04:05:26 seoul.sayhey.cyou sudo[991]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
升级了VLESS 1.5
nginx 配置为
user www-data;
worker_processes auto;
pid /run/nginx.pid;
events {
worker_connections 768;
}
http {
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for" '
'$proxy_protocol_addr:$proxy_protocol_port';
access_log /var/log/nginx/access.log main;
error_log /var/log/nginx/error.log;
sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
types_hash_max_size 2048;
include /etc/nginx/mime.types;
default_type application/octet-stream;
gzip on;
gzip_disable "msie6";
server {
listen [::]:80 default ipv6only=off;
return 301 https://$http_host$request_uri;
}
server {
listen unix:/dev/shm/default.sock proxy_protocol;
listen unix:/dev/shm/h2c.sock http2 proxy_protocol;
set_real_ip_from 127.0.0.1;
location / {
proxy_pass http://www.lovelive-anime.jp/;
}
error_page 404 /404.html;
location = /40x.html {
}
error_page 500 502 503 504 /50x.html;
location = /50x.html {
}
}
}
反代网站为http://www.lovelive-anime.jp/ 在VLESS1.3时,按当时 nginx配置我自己改好,访问我的域名,就能正常反代。今天升级后,访问域名就不行了。v2ray vless是正常工作的。
我阅读了v2fly.org,vless协议下关于fallback的解释,感觉还不是太明白,相信还有很多和我一样的人。希望在官网文档解释下fallback是什么,为什么设计fallback,以及怎么配置fallback。
例如:配置文件:https://github.com/v2fly/v2ray-examples/blob/master/VLESS-TCP-TLS-WS%20(recommended)/config_server.json 中
"fallbacks": [
{
"dest": 80
},
{
"path": "/websocket", // 必须换成自定义的 PATH
"dest": 1234,
"xver": 1
}
]
fallback数组中有两个对象,什么时候调用第一个,什么时候调用第二个,或者说第一个和第二个怎么联系的。
自己尝试着修改折腾了整整一整天都没成功。最接近成功的是已经pin通了但就是用不了。没辙了。
config.txt
用的是推荐配置
https://github.com/v2fly/v2ray-examples/blob/master/VLESS-TCP-TLS-WS%20(recommended)/config_server.json
配置好了以后tls正常,ws报错,下面是v2客户端的报错提示
2020/09/01 12:55:14 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vless/outbound: failed to find an available destination > v2ray.com/core/common/retry: [v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://域名/api): > unexpected EOF] > v2ray.com/core/common/retry: all retry attempts failed
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.