You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used the above configuration to prepare two bridges, but the first bridge can work normally, but the second bridge cannot communicate. Can anyone tell me why? Thank you so much.
The text was updated successfully, but these errors were encountered:
{
"reverse":{
"portals":[
{"tag":"portal1", "domain":"private1.cloud.com"},
{"tag":"portal2", "domain":"private2.cloud.com"}
]
},
"inbounds":[
{
"tag":"tunnel1",
"port":31957,
"listen": "0.0.0.0",
"protocol": "socks",
"settings": {
"auth": "password",
"accounts": [
{"user": "username", "pass": "username"}
],
"udp": true,
"ip": "0.0.0.0",
"userLevel": 0
}
},
{
"tag":"tunnel2",
"port":31958,
"listen": "0.0.0.0",
"protocol": "socks",
"settings": {
"auth": "password",
"accounts": [
{"user": "username", "pass": "password"}
],
"udp": true,
"ip": "0.0.0.0",
"userLevel": 0
}
},
{
"tag": "interconn",
"port":443,
"protocol":"vless",
"settings":{
"clients":[
{"id":"9E0AAF87-971B-475B-BFD3-83B075A25A42"}
],
"decryption": "none"
},
"streamSettings": {
"network": "ws",
"wsSettings": {
"path": "/colod"
},
"security": "tls",
"tlsSettings": {
"certificates": [
{ "certificateFile": "cloud.wpbom.com.crt", "keyFile": "cloud.wpbom.com.key"}
],
"allowInsecure": true,
"fingerprint": "random"
}
}
}
],
"routing": {
"rules": [
{"type":"field", "inboundTag":["tunnel1"], "outboundTag":"portal1"},
{"type":"field", "inboundTag":["tunnel2"], "outboundTag":"portal2"},
{"type":"field", "inboundTag":["interconn"], "outboundTag":"portal1", "domain":["full:private1.cloud.com"]},
{"type":"field", "inboundTag":["interconn"], "outboundTag":"portal2", "domain":["full:private2.cloud.com"]}
]
}
}
I used the above configuration to prepare two bridges, but the first bridge can work normally, but the second bridge cannot communicate. Can anyone tell me why? Thank you so much.
The text was updated successfully, but these errors were encountered: