ss+websocket不支持吗？ #173
Comments
|
因为ss那边分离出了插件层，所以协议结构和v2这边不太一样。 如果想用 v2做server， ss over v2做客户端的话需要在server
这里有个样例配置 |
我的这个，你有什么意见吗？ |
参考了你的配置文件，现在一个v2ray server就可以搞定ss+v2plugin和v2ray client共用了，ss-server+v2plugin可以丢掉了。谢谢！ |
可以看下你完整的json么？ |
配合caddy或者ngnix，共用443端口，本配置完全参考了@lcdtyph的样例文件。 {
"log": {
"access": "/var/log/v2ray/access.log",
"error": "/var/log/v2ray/error.log",
"loglevel": "warning"
},
"inbounds": [
{
"port": "10001", /* this is the server port for client */
"listen": "127.0.0.1",
"protocol": "dokodemo-door",
"tag": "wsdoko",
"settings": {
"address": "v1.mux.cool", /* don't change!!! */
"followRedirect": false,
"network": "tcp"
},
"streamSettings": {
"network": "ws", /* same as v2ray-plugin */
"wsSettings": {
"path": "/shadow"
}
}
},
{
"port": 9015, /* this port is not used, but you need to specific */
"protocol": "shadowsocks",
"settings": {
"method": "chacha20-ietf-poly1305",
"ota": false,
"password": "mypass",
"network": "tcp,udp"
},
"streamSettings": {
"network": "domainsocket"
}
},
{
"port": 10000,
"listen": "127.0.0.1",
"protocol": "vmess",
"tag": "proxy",
"settings": {
"clients": [{
"id": "your uuid",
"alterId": 64
}]
},
"streamSettings": {
"network": "ws",
"wsSettings": {
"path": "/ray"
}
}
}
],
"outbounds": [
{
"protocol": "freedom",
"settings": {},
"tag": "direct"
},
{
"protocol": "blackhole",
"settings": {},
"tag": "blocked"
},
{
"protocol": "freedom",
"tag": "ssmux",
"streamSettings": {
"network": "domainsocket"
}
}
],
"transport": {
"dsSettings": {
"path": "/var/run/ss-loop.sock" /* the directory must exist before v2ray starts */
}
},
"routing": {
"rules": [
{
"type": "field",
"inboundTag": [
"wsdoko"
],
"outboundTag": "ssmux"
},
{
"type": "field",
"ip": [
"geoip:private"
],
"outboundTag": "blocked"
}
]
}
} |
感谢 已经跑通了 |
你好，我服务端用的nginx+v2ray，按照你的配置，PC客户端用shadowsocks+v2ray-plugin连接没有问题 但是Android端从GooglePlay上安装的shadowsocks+v2ray-plugin连不通(安卓端设置是按照PC端对照着设置的，模式选的websocket+tls，path也跟pc端设置的一样的)。目前现象就是安卓端ss点击连接后，提示“已连接，点击测试连接”，点击一下，ss就开始测试，显示“测试中”，等一会就提示“无互联网连接”。 安卓端连接的话，是否还有什么需要注意的？感谢 |
|
印象中有个人也有这个问题，后来服务端证书改用fullchain解决了。自己测试一下。
MxdStudio <notifications@github.com> 于 2019年7月21日周日 02:29写道：
… 可以看下你完整的json么？
***@***.*** <https://github.com/lcdtyph>的样例文件。
{
"log": {
"access": "/var/log/v2ray/access.log",
"error": "/var/log/v2ray/error.log",
"loglevel": "warning"
},
"inbounds": [
{
"port": "10001", /* this is the server port for client */
"listen": "127.0.0.1",
"protocol": "dokodemo-door",
"tag": "wsdoko",
"settings": {
"address": "v1.mux.cool", /* don't change!!! */
"followRedirect": false,
"network": "tcp"
},
"streamSettings": {
"network": "ws", /* same as v2ray-plugin */
"wsSettings": {
"path": "/shadow"
}
}
},
{
"port": 9015, /* this port is not used, but you need to specific */
"protocol": "shadowsocks",
"settings": {
"method": "chacha20-ietf-poly1305",
"ota": false,
"password": "mypass",
"network": "tcp,udp"
},
"streamSettings": {
"network": "domainsocket"
}
},
{
"port": 10000,
"listen": "127.0.0.1",
"protocol": "vmess",
"tag": "proxy",
"settings": {
"clients": [{
"id": "your uuid",
"alterId": 64
}]
},
"streamSettings": {
"network": "ws",
"wsSettings": {
"path": "/ray"
}
}
}
],
"outbounds": [
{
"protocol": "freedom",
"settings": {},
"tag": "direct"
},
{
"protocol": "blackhole",
"settings": {},
"tag": "blocked"
},
{
"protocol": "freedom",
"tag": "ssmux",
"streamSettings": {
"network": "domainsocket"
}
}
],
"transport": {
"dsSettings": {
"path": "/var/run/ss-loop.sock" /* the directory must exist before v2ray starts */
}
},
"routing": {
"rules": [
{
"type": "field",
"inboundTag": [
"wsdoko"
],
"outboundTag": "ssmux"
},
{
"type": "field",
"ip": [
"geoip:private"
],
"outboundTag": "blocked"
}
]
}
}
你好，我服务端用的nginx+v2ray，按照你的配置，PC客户端用shadowsocks+v2ray-plugin连接没有问题
但是Android端从GooglePlay上安装的shadowsocks+v2ray-plugin连不通(安卓端设置是按照PC端对照着设置的，模式选的websocket+tls，path也跟pc端设置的一样的)。目前现象就是安卓端ss点击连接后，提示“已连接，点击测试连接”，点击一下，ss就开始测试，显示“测试中”，等一会就提示“无互联网连接”。
安卓端连接的话，是否还有什么需要注意的？感谢
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#173?email_source=notifications&email_token=AGNKUH5LZLCYN6XA7Q2PLF3QANKPFA5CNFSM4G3LBM32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2NTTHY#issuecomment-513489311>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGNKUH2X353JIGPL22VSIA3QANKPFANCNFSM4G3LBM3Q>
.
|
估计应该是这个问题。 其实昨天我也怀疑是这个问题。起因是我用手机上的浏览器访问了一下地址，想看看访问日志。安卓用chrome的时候正常，安卓用firefox访问的时候，提示“此连接不受信任”，搜了一下，很多讨论都说是因为没有包含中间证书，需要改用fullchain。 看了你的回复，我更肯定一些了，我估计大概率就是这个问题。等我回头试一下，把结果反馈上来。 再次感谢你回复，对确定问题很有用👍 |
经测试，就是因为缺少中间证书，导致证书不受信任。换成fullchain就OK了，android端可以连接了。 |
你好，我没有用反代，直接让v2ray服务端处理ws+tls数据，配置文件几乎和示例一样，只是在dokodemo-door的streamSettings里加上了tls相关的设置。但是运行起来之后没法连接，v2ray的日志里有大量的
如果不加tls，报错是这样的
不知道是不是我哪里设置的不对？客户端的v2ray-plugin参数应该怎么设置？ update： |
|
@Amaterasu33 |
{
"log":{
"access":"/var/log/v2ray/access.log",
"error":"/var/log/v2ray/error.log",
"loglevel":"warning"
},
"inbounds": [{
"port": 10000,
"listen":"127.0.0.1",
"protocol": "vmess",
"settings": {
"clients": [
{
"id": "xxx",
"level": 1,
"alterId": 64
}
]
},
"streamSettings":{
"network":"ws",
"wsSettings":{
"path":"xxx"
}
}
},
{
"port":10001,
"listen":"127.0.0.1",
"protocol":"dokodemo-door",
"tag":"wsdoko",
"settings":{
"address":"v1.mux.cool",
"follorRedirect":false,
"network":"tcp"
},
"steramSettings":{
"network":"ws",
"wsSettings":{
"path":"xxxx"
}
}
},
{
"port":10002,
"protocol":"shadowsocks",
"settings":{
"method":"aes-256-gcm",
"ota":false,
"password":"xxx",
"network":"tcp,udp"
},
"streamSettings":{
"network":"domainsocket"
}
}],
"outbounds": [{
"protocol": "freedom",
"settings": {}
},{
"protocol": "blackhole",
"settings": {},
"tag": "blocked"
},
{
"protocol":"freedom",
"tag":"ssmux",
"sreamSettings":{
"network":"domainsocket"
}
}],
"transport":{
"dsSettings":{
"path":"/var/run/v2ray/ss-loop.sock"
}
},
"routing": {
"rules": [
{
"type":"field",
"inboundTag":[
"wsdoko"
],
"outboundTag":"ssmux"
},
{
"type": "field",
"ip": ["geoip:private"],
"outboundTag": "blocked"
}
]
}
}第一个10000端口的用vmess+caddy反代没有问题，10001端口会出错 |
"steramSettings" -> "streamSettings"
"sreamSettings" -> "streamSettings" |
|
@lcdtyph 好尴尬啊，看了好几遍都没发现。谢谢啦！ |
|
v2ray-plugin插件更新1.2之后，在win客户端插件选项里加入mux=0之后可以正常访问v2ray作为服务端的ss+ws了。 |
你好，能看看v2ray服务端的json文件和客户端这边SS的配置截图吗？谢谢 |
why can't i find ss-loop.sock in /var/run |
|
@missmuxixi |
Thank you for help，i run it successfully，btw，Can this solution coexist with trojan on the same one server？sometimes，one of them is not works well enough，if we can choose anyone when the other one is weak，maybe feel better |
I believe the answer is yes. You can use trojan and v2ray and ss+v2ray-plugin in the same server with the same 443 port (with the help of nginx, for example). |
这条应该置顶，已经不再需要像之前那样写一堆了 |
可否分享一下你的服务端和客户端的配置文件或截图，参考一下吗？感谢 |
就是不需要服务端特殊写了，只要在客户端加 mux=0 就行。 |
|
楼上说的对，在客户端配置： |
SS最近出了新插件 shadowsocks/v2ray-plugin，然后在 https://toutyrater.github.io/basic/Shadowsocks.html
看到一句
所以就想试试在服务端部署v2ray的 ss + websocket, 自己电脑客户端用SS windows 客户端 + v2ray-plugin插件 来使用。
因为那个插件用的是4.16，我在服务端部署用的也是4.16,json文件如下
运行起来后，打开所用的域名网页，显示 Bad Request。信息提示
电脑SS客户端如下配置
用来翻墙打开谷歌也没打开， 是哪里没高对吗？
The text was updated successfully, but these errors were encountered: