mellow-io/mellow

Mellow is a rule-based global transparent proxy client for Windows, macOS and Linux. Also a Proxifier alternative.

mellow's Issues

macOS不稳定的issue

MacBook Pro (Retina, 15-inch, Mid 2015)
macOS Catalina Version 10.15

1. connect 点击后，不一定有效，反复disconnect和connect后，偶尔可以正常工作
2. 偶现和微信mac版不能共同工作的问题，一打开微信，Mellow就报错。

Questions about Mellow and go-tun2socks

Hi, mellow maintainers. I just found this awesome project several hours ago, and it totally surprised me by that your idea is exactly what I'm thinking. However, there are also some questions while I was exploring it:

1. Is there any connection (e.g., depends on) between Mellow and go-tun2socks?
2. If yes, I see that the core file might be a customized build of go-tun2socks, and ./core -version indicates that the tag and commit hash are v1.16.2 and e3b3599. I can't find this commit in go-tun2socks repo. Is the core file open sourced?
3. The latest release of go-tun2socks seems removed the "native" support of V2Ray (Vmess) proxy. If there's no planning for making core file open-source, can I replace the core file with my build of the open-source go-tun2socks project?

Thank you!

A JavaScript error occurred in the main process

macOS 10.14.5 (18F132)

错误信息
Uncaught Exception:
ReferenceError: mainWindow is not defined
at App. (/Applications/Mellow.app/Contents/Resources/app.asar/main.js:247:3)
at App.emit (events.js:194:13)

什么时候出一版Linux的呢？

udp流量转发貌似有问题，微信视频时cpu300%占用

在没有微信视频时(也就是不存在大量udp流量的情况下)，一切工作正常，一旦视频，cpu占用爆炸，直接没网。

版本信息

• macOS 10.14.6
• Mellow 0.0.6

配置文件

{
  "outbounds": [
    {
      "protocol": "socks",
      "settings": {
        "servers": [
          {
            "address": "127.0.0.1",
            "port": 1080
          }
        ]
      }
    },
    {
      "protocol": "freedom",
      "settings": {
        "domainStrategy": "UseIP"
      },
      "tag": "direct"
    }
  ],
  "routing": {
    "domainStrategy": "IPIfNonMatch",
    "rules": [
      {
        "app": [
          "*shadowsocks*",
          "ShadowsocksX-NG",
          "ClashX",
          "clash"
        ],
        "type": "field",
        "outboundTag": "direct"
      }
    ]
  }
}

日志

log.log

能支持中文吗？安装了一下，一脸懵逼

能支持中文吗？安装了一下，一脸懵逼

作者可以告知mellow使用什么语言开发的吗，想学习一门语言，谢谢

0.0.13 Windows 10启动失败

0.0.13安装后无法启动，出现以下错误信息

当有多个active的interface时，send through的选择问题

我的电脑上配置有两个active的interface: en0 和 en8

mellow disconnect时，默认路由：

Destination        Gateway            Flags        Refs      Use   Netif Expire
default            192.168.1.1        UGSc           76        0     en8

mellow connect时，默认路由：

Destination        Gateway            Flags        Refs      Use   Netif Expire
default            10.255.0.1         UGSc           78        0 utun233
default            192.168.1.1        UGScI          13        0     en0

平时主要使用en8，但现在被更换为了en0.

看了下目前findOriginalSendThrough的逻辑是：找到一个interface就返回。感觉这样不太合理。

把findOriginalSendThrough的逻辑换为 “disconnect时的interface” 是否更为合理？

IPv6支持

目前版本似乎并不支持IPv6，以后是否有计划支持？
（辣鸡教育网一到晚高峰IPv4丢包到怀疑人生。。。

win10移动热点开启，本机代理失效，连接热点的机器时也不能通过mellow实现透明代理

mellow的linux客户端分流错误

最新版0.1.2 linux客户端，使用kitsunebi的绕过局域网和大陆的配置用在mellow上，国外网站都能访问，国内网站都打不开 。

0.1.2升级到0.1.4后无法连接 [macOS]

日志：

[2019-10-12 16:52:13.760] [info] Mellow (0.1.4) started.
[2019-10-12 16:52:17.561] [info] Checking helper files.
[2019-10-12 16:52:17.835] [info] Original gateway is 192.168.31.1
[2019-10-12 16:52:17.836] [info] Original send through 192.168.31.127 en0
[2019-10-12 16:53:10.015] [info] Original gateway is 192.168.31.1
[2019-10-12 16:53:10.016] [info] Original send through 192.168.31.127 en0
[2019-10-12 16:53:13.771] [info] Original gateway is 192.168.31.1
[2019-10-12 16:53:13.772] [info] Original send through 192.168.31.127 en0
[2019-10-12 16:53:31.831] [info] Original gateway is 192.168.31.1
[2019-10-12 16:53:31.832] [info] Original send through 192.168.31.127 en0
[2019-10-12 16:53:33.014] [info] Original gateway is 192.168.31.1
[2019-10-12 16:53:33.015] [info] Original send through 192.168.31.127 en0

使用旧版的json配置文件

请教一下关于DNS的问题

现在的问题应该是无法使用配置文件中的DNS进行域名解析
系统macOS 10.14.6
尝试过的一些操作

1. 将WiFi接口的DNS设为8.8.8.8是能正常工作的，在此之前是路由器IP，路由器的DNS大概是联通的
2. 将路由规则改成 "rules": [
   {
   "ip": [
   "0.0.0.0/0",
   "::/0"
   ],
   "type": "field",
   "outboundTag": "proxy"
   }
   ]
   也就是所有流量都走代理，国内网站是能正常解析的，百度显示的IP也是代理的IP，但是国外网站（google...）解析不出来
   所以猜测是DNS的问题，不知道是不是配置的不对
   配置文件：
   {
   "log": {
   "loglevel": "warning"
   },"dns": {
   "hosts": {
   "localhost": "127.0.0.1"
   },
   "servers": [
   {
   "address": "8.8.8.8",
   "port": 53
   },
   {
   "address": "223.5.5.5",
   "port": 53,
   "domains": [
   "geosite:cn"
   ]
   }
   ]
   },
   "outbounds": [
   {
   "protocol": "vmess",
   "settings": {
   "vnext": [
   {
   "users": [
   {
   "id": "*****************",
   "alterId": 2,
   "security": "auto"
   }
   ],
   "address": "**********",
   "port": 443
   }
   ]
   },
   "streamSettings": {
   "network": "tcp",
   "security": "tls",
   "tlsSettings": null,
   "tcpSettings": null,
   "kcpSettings": null,
   "wsSettings": null,
   "httpSettings": null
   },
   "tag": "proxy"
   },
   {
   "protocol": "freedom",
   "settings": {},
   "tag": "direct"
   }
   ],
   "routing": {
   "domainStrategy": "IPIfNonMatch",
   "rules": [
   {
   "type": "field",
   "domain": [
   "geosite:cn"
   ],
   "outboundTag": "direct"
   },
   {
   "type": "field",
   "ip": [
   "geoip:cn",
   "geoip:private"
   ],
   "outboundTag": "direct"
   },
   {
   "ip": [
   "0.0.0.0/0",
   "::/0"
   ],
   "type": "field",
   "outboundTag": "proxy"
   }
   ]
   }
   }

如何实现lan共享？

如题，能否实现局域网内共享代理？在配置文件写了inbound配置监听0.0.0.0:10808报错无法connect。

outbound support http

like this pr

能不能设置打开软件时自动开启代理，每次点start很麻烦

能不能设置打开软件时自动开启代理，每次点start很麻烦

Linux 版本能否编译一个 ARM 架构的

类树莓派的 SBC 都是 ARM 架构的，要是能有一个 ARM 架构版本的就更好了，那样可以直接运行在 SBC 上充当翻墙网关

dokodemo-door入站协议异常

1. 现象
   设置dokodemo-door协议后只能收到tcp请求，无法收到udp请求。
2. 版本
   Mellow (v0.0.18) 在Macbook运行
3. 配置文件

{
    "log": {
            "loglevel": "debug"
    },
    "inbounds": [
        {
            "protocol": "dokodemo-door",
            "port": 53,
            "tag": "dns-in",
            "settings": {
                "address": "223.5.5.5",
                "port": 53,
                "network": "tcp,udp"
            }
        }
    ],
    "outbounds": [
        {
            "protocol": "dns",
            "tag": "dns-out"
        },
        {
            "protocol": "freedom",
            "settings": {
                "domainStrategy": "UseIP"
            },
            "tag": "direct"
        }
    ],
    "routing": {
        "domainStrategy": "IPIfNonMatch",
        "rules": [
            {
                "type": "field",
                "inboundTag": [
                    "dns-in"
                ],
                "outboundTag": "dns-out"
            },
            {
                "ip": [
                    "0.0.0.0/0",
                    "::/0"
                ],
                "type": "field",
                "outboundTag": "direct"
            }
        ]
    }
}

4. 具体说明

（1）使用上述配置文件后，在本机运行如下命令（192.168.50.240为本机IP）：

dig www.baidu.com @192.168.50.240
telnet 192.168.50.240 53

只能在日志中找到tcp相关信息：

2019/09/09 13:03:50 [Debug] [3010167163] v2ray.com/core/proxy/dokodemo: processing connection from: 192.168.50.240:51704
2019/09/09 13:03:50 [Info] [3010167163] v2ray.com/core/app/dispatcher: taking detour [dns-out] for [tcp:223.5.5.5:53]
2019/09/09 13:03:50 [Info] [3010167163] v2ray.com/core/proxy/dns: handling DNS traffic to tcp:223.5.5.5:53

（2）使用V2Ray 4.19.1运行相同配置，执行相同命令时，在日志中能找到udp和tcp相关信息：

2019/09/09 12:59:57 [Debug] [2867811318] v2ray.com/core/proxy/dokodemo: processing connection from: 192.168.50.240:65005
2019/09/09 12:59:57 [Info] [2867811318] v2ray.com/core/app/dispatcher: taking detour [dns-out] for [udp:223.5.5.5:53]
2019/09/09 12:59:57 [Info] [2867811318] v2ray.com/core/proxy/dns: handling DNS traffic to udp:223.5.5.5:53
2019/09/09 13:00:10 [Debug] [1534539022] v2ray.com/core/proxy/dokodemo: processing connection from: 192.168.50.240:51307
2019/09/09 13:00:10 [Info] [1534539022] v2ray.com/core/app/dispatcher: taking detour [dns-out] for [tcp:223.5.5.5:53]
2019/09/09 13:00:10 [Info] [1534539022] v2ray.com/core/proxy/dns: handling DNS traffic to tcp:223.5.5.5:53

如何指定某几个进程走代理, 而其他进程不走代理

我的目的是让cmd.exe以及chrome.exe同时走代理, 同时其它的进程不走代理, 但是并不成功.
然后我尝试了下面这种方式设置路由后发现chrome还是走了代理.

    "routing": {
      "rules": [
          {
              "app": [
                  "git*",
                  
                  "cmd.exe"
              ],
              "type": "field",
              "outboundTag": "proxy"
          }
      ]
  }

WiFi切换另一个网络后，mellow需要reconnect

如题，正常使用状态下，切换另一个网络连接，mellow不能随之切换，需要手动reconnect后才能使用。请问作者大大是不是现在的版本是不是还未实现切换？谢谢作者大大。

提示"tap device not ready, user does not grant permission"

我理解的不是安装（已经用administrator权限运行安装了）时默认会配置好tap？还是tun？
看到说明里也没有说需要额外配置tap or tun，所以就没有进行有关配置。

然后就用readme里最简单的outbounds设置，也是如此提示。

日志如下：
2019-09-26 15:37:56.097] [info] Mellow (0.1.0) started.
[2019-09-26 15:39:36.525] [info] Original gateway is 10.0.0.1
[2019-09-26 15:39:36.532] [info] Original send through 10.0.0.151 Ethernet 3
[2019-09-26 15:39:36.537] [info] Ensuring tap device sets up correctly.
[2019-09-26 15:39:37.129] [info] undefined
[2019-09-26 15:39:37.135] [info] undefined
[2019-09-26 15:39:55.646] [info] Shutting down the core.
[2019-09-26 15:39:56.275] [info] Core downed.

请问tap 和 tun还需要配置吗？该如何配置？
如果需要，能否在readme部分做一个简单介绍，有个线索即可，本人就可以自行去google学习和了解。谢谢了。

macOS DNS流量异常

网页显示找不到ip
statistics里面没找到相关的DNS解析udp包，同样的配置文件windows下正常

Problem using V2ray client as outbound

I just moved from Proxifier to Mellow. When using Mellow with V2rayN client on Windows, the V2ray client log is flushed with errors. Some app failed to connect to the Internet, while some connections are abnormally slow.

V2RayN listens on socks5://localhost:1080

Mellow cfg.json as follow:

{
	"log": {
		"loglevel": "warning"
	},
	"outbounds": [
		{
			"protocol": "socks",
			"settings": {
				"servers": [
					{
						"address": "127.0.0.1",
						"port": 1080
					}
				]
			},
			"tag": "v2ray"
		},
		{
			"protocol": "freedom",
			"tag": "direct"
		},
		{
			"protocol": "blackhole",
			"tag": "block"
		}
	],
	"routing": {
		"domainStrategy": "AsIs",
		"rules": [
			{
				"type": "field",
				"ip": [
					"geoip:private"
				],
				"outboundTag": "direct"
			},
			{
				"type": "field",
				"port": "53",
				"outboundTag": "direct"
			},
			{
				"type": "field",
				"domain": [
					"example.com"
				],
				"outboundTag": "direct"
			},
			{
				"app": [
					"v2ray*.exe",
					"wv2ray.exe",
					"chrome.exe",
					"firefox.exe",
					"qbittorrent.exe",
					"qemu*.exe",
					"filezilla.exe"
				],
				"type": "field",
				"outboundTag": "direct"
			},
			{
				"type": "field",
				"network": "udp",
				"outboundTag": "direct"
			}
		]
	}
}

The log of the V2ray client:

2019/09/07 23:32:33 [Info] [2747579422] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2019/09/07 23:32:33 [Info] [3950373290] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2019/09/07 23:32:33 [Info] [1014540110] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2019/09/07 23:32:33 [Info] [1799767726] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2019/09/07 23:32:33 [Info] [222186543] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2019/09/07 23:32:33 [Info] [1911553490] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2019/09/07 23:32:33 [Info] [3640751713] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2019/09/07 23:32:33 [Info] [3105356902] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2019/09/07 23:32:33 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:34 [Info] [2799824874] v2ray.com/core/proxy/socks: TCP Connect request to tcp:www.youtube.com:443
2019/09/07 23:32:34 tcp:[::1]:11148 accepted tcp:www.youtube.com:443 
2019/09/07 23:32:34 [Info] [2799824874] v2ray.com/core/app/dispatcher: taking detour [proxy] for [tcp:www.youtube.com:443]
2019/09/07 23:32:34 [Info] [2799824874] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:34 [Info] [538549186] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:34 [Warning] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11040->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:34 [Info] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2019/09/07 23:32:34 [Info] [1390016570] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:35 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:35 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain session.raidrive.com at server udp:8.8.8.8:53 > context deadline exceeded
2019/09/07 23:32:35 [Info] v2ray.com/core/app/router: resolve ip for session.raidrive.com > v2ray.com/core/app/dns: returning nil for domain session.raidrive.com > context deadline exceeded
2019/09/07 23:32:35 [Debug] v2ray.com/core/app/dns: querying DNS for: session.raidrive.com.
2019/09/07 23:32:35 [Debug] v2ray.com/core/transport/internet/udp: dispatch request to: udp:8.8.8.8:53
2019/09/07 23:32:35 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:8.8.8.8:53
2019/09/07 23:32:35 [Debug] v2ray.com/core/transport/internet/udp: dispatch request to: udp:8.8.8.8:53
2019/09/07 23:32:35 [Info] v2ray.com/core/app/dispatcher: default route for udp:8.8.8.8:53
2019/09/07 23:32:35 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:35 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:35 [Warning] [1390016570] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10849->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10916->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10982->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11053->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:35 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:35 [Info] [2747579422] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:35 [Info] [3950373290] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:35 [Info] [1799767726] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:35 [Info] [222186543] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:35 [Info] [722088281] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:35 [Info] [3105356902] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:35 [Info] [3640751713] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:35 [Info] [1014540110] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:35 [Info] [1911553490] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:36 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:36 [Warning] [2747579422] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10858->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10929->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11002->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11071->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:36 [Warning] [3950373290] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10859->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10930->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11003->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11072->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:36 [Warning] [722088281] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10860->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10931->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11004->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11073->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:36 [Warning] [222186543] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10868->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10935->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11007->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11074->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:36 [Warning] [3105356902] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10872->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10936->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11010->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11076->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:36 [Warning] [3640751713] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10871->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10937->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11009->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11079->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:36 [Warning] [1014540110] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10863->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10932->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11008->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11078->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:36 [Warning] [1799767726] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10864->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10933->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11005->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11075->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:36 [Warning] [1911553490] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10867->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10934->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11006->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11077->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:36 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain userstylesapi.com at server udp:8.8.8.8:53 > context deadline exceeded
2019/09/07 23:32:36 [Info] v2ray.com/core/app/router: resolve ip for userstylesapi.com > v2ray.com/core/app/dns: returning nil for domain userstylesapi.com > context deadline exceeded
2019/09/07 23:32:36 [Debug] v2ray.com/core/app/dns: querying DNS for: userstylesapi.com.
2019/09/07 23:32:36 [Debug] v2ray.com/core/transport/internet/udp: dispatch request to: udp:8.8.8.8:53
2019/09/07 23:32:36 [Debug] v2ray.com/core/transport/internet/udp: dispatch request to: udp:8.8.8.8:53
2019/09/07 23:32:37 [Warning] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11070->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:37 [Info] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2019/09/07 23:32:37 [Info] [3352928952] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2019/09/07 23:32:38 tcp:[::1]:11182 accepted tcp:clients4.google.com:443 
2019/09/07 23:32:38 [Info] [1159051673] v2ray.com/core/proxy/socks: TCP Connect request to tcp:clients4.google.com:443
2019/09/07 23:32:38 [Info] [1159051673] v2ray.com/core/app/dispatcher: taking detour [proxy] for [tcp:clients4.google.com:443]
2019/09/07 23:32:38 [Info] [1159051673] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:39 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:39 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain session.raidrive.com at server udp:8.8.8.8:53 > context deadline exceeded
2019/09/07 23:32:39 [Info] v2ray.com/core/app/router: resolve ip for session.raidrive.com > v2ray.com/core/app/dns: returning nil for domain session.raidrive.com > context deadline exceeded
2019/09/07 23:32:39 [Info] [235575070] v2ray.com/core/app/dispatcher: default route for tcp:session.raidrive.com:443
2019/09/07 23:32:39 [Info] [235575070] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:39 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:39 [Info] [1159051673] v2ray.com/core/proxy/vmess/outbound: tunneling request to tcp:clients4.google.com:443 via tcp:example.com:9819
2019/09/07 23:32:39 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:39 [Info] [3352928952] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:40 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:40 [Warning] [3352928952] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10899->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10963->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11035->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11103->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:40 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain userstylesapi.com at server udp:8.8.8.8:53 > context deadline exceeded
2019/09/07 23:32:40 [Info] v2ray.com/core/app/router: resolve ip for userstylesapi.com > v2ray.com/core/app/dns: returning nil for domain userstylesapi.com > context deadline exceeded
2019/09/07 23:32:40 [Debug] v2ray.com/core/app/dns: querying DNS for: userstylesapi.com.
2019/09/07 23:32:40 [Debug] v2ray.com/core/transport/internet/udp: dispatch request to: udp:8.8.8.8:53
2019/09/07 23:32:40 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:8.8.8.8:53
2019/09/07 23:32:40 [Debug] v2ray.com/core/transport/internet/udp: dispatch request to: udp:8.8.8.8:53
2019/09/07 23:32:40 [Info] v2ray.com/core/app/dispatcher: default route for udp:8.8.8.8:53
2019/09/07 23:32:40 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:40 [Info] [1653032650] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:40 [Info] [3435734673] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:40 [Info] [2229535272] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:40 [Info] [3967053876] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:40 [Info] [3908115426] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:40 [Info] [2765807898] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:40 [Info] [625425166] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:40 [Info] [2074659080] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:40 [Info] [3870417887] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:40 [Info] [3940928244] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:40 [Info] [538549186] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2019/09/07 23:32:41 [Warning] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11102->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:41 [Info] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2019/09/07 23:32:41 [Info] [529911429] v2ray.com/core/proxy/socks: TCP Connect request to tcp:www.youtube.com:443
2019/09/07 23:32:41 tcp:[::1]:11220 accepted tcp:www.youtube.com:443 
2019/09/07 23:32:41 [Info] [529911429] v2ray.com/core/app/dispatcher: taking detour [proxy] for [tcp:www.youtube.com:443]
2019/09/07 23:32:41 [Info] [529911429] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:42 [Info] [2799824874] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:43 [Info] [538549186] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:43 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:43 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:43 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:43 [Warning] [538549186] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10924->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:10986->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11050->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11152->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:44 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:44 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain userstylesapi.com at server udp:8.8.8.8:53 > context deadline exceeded
2019/09/07 23:32:44 [Info] v2ray.com/core/app/router: resolve ip for userstylesapi.com > v2ray.com/core/app/dns: returning nil for domain userstylesapi.com > context deadline exceeded
2019/09/07 23:32:44 [Info] [1997758930] v2ray.com/core/app/dispatcher: default route for tcp:userstylesapi.com:443
2019/09/07 23:32:44 [Info] [1997758930] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:45 [Warning] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11174->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:45 [Info] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2019/09/07 23:32:47 [Info] [235575070] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:48 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:48 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:48 [Info] [3435734673] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:48 [Info] [1653032650] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:48 [Info] [2229535272] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:48 [Info] [3967053876] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:48 [Info] [3908115426] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:48 [Info] [2765807898] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:48 [Info] [625425166] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:48 [Info] [3870417887] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:48 [Info] [2074659080] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:48 [Info] [3940928244] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:49 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:49 [Info] [529911429] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:49 [Info] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:50 [Info] [2799824874] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819
2019/09/07 23:32:50 [Warning] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/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://example.com:9819/path/to/ws/):  > read tcp 10.255.0.2:11193->114.51.41.91:9819: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://example.com:9819/path/to/ws/):  > dial tcp: operation was canceled] > v2ray.com/core/common/retry: all retry attempts failed
2019/09/07 23:32:50 [Info] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2019/09/07 23:32:52 [Info] [1997758930] v2ray.com/core/transport/internet/websocket: creating connection to tcp:example.com:9819

Please help. Thank you.

指定进程的时候是否可以指定父进程

指定进程的时候是否可以指定父进程，然后下面所有的子进程都按父进程的配置来

mellow配合clash时，clash链接远端代理的ip请求被dispatcher解析为 混淆后的域名请求

clash里链接用的节点

@eycorsican

我用了和 @0njzy0 一样的配置，但发现clash链接远端的请求被dispatcher解析为混淆的域名。导致连接失败。

clash直连的没问题

Originally posted by @Masstone in #3 (comment)

Mellow重载配置后在macOS菜单栏产生多余空白

环境

• macOS 10.13.6
• Mellow v1.0.6

每次重载当前配置后，顶部菜单栏Mellow图标右侧产生多余空格。

mac上和windows上安装后均报错

mac上和windows上安装后均报错找不到config文件，不能运行

IPV4环境下，能否去除dns_out请求AAAA的操作？

主要是请求AAAA浪费时间和资源，有的域名没有返回AAAA的话，还要等超时。能否做个开关选项？

请教一下如何配合其他代理软件一起使用

我想将mellow配合clashx一起使用。clashx本地socks端口为1088。由于clashx目前没有tun，所以我想配合mellow一起使用，从而实现透明代理。请教一下配置文件如何配置。

这是我目前的配置文件：

{
  "log": {
    "loglevel": "info"
  },
  "inbounds": [
    {
      "port": 1080,
      "protocol": "socks",
      "sniffing": {
        "enabled": true,
        "destOverride": [
          "http",
          "tls"
        ]
      },
      "settings": {
        "auth": "noauth"
      }
    }
  ],
  "outbounds": [
    {
      "protocol": "socks",
      "settings": {
        "servers": [
          {
            "address": "127.0.0.1",
            "port": 1088
          }
        ]
      },
      "tag": "clashx"
    },
    {
      "protocol": "freedom",
      "settings": {
        "domainStrategy": "UseIP"
      },
      "tag": "direct"
    }
  ],
  "routing": {
    "domainStrategy": "IPIfNonMatch",
    "rules": [
      {
        "app": [
          "ClashX"
        ],
        "type": "field",
        "outboundTag": "direct"
      }
    ]
  }
}

Windows下考虑使用Wireguard的WinTun？

https://www.wintun.net/
可能会比Tap Windows稳定一些？

能考虑支持下可怜的32位系统吗? please

关于开源

对于 core 和 route 是否开源?

HTTP/2传输方式conf转换不正确

使用HTTP/2作为传输方式的配置，如果使用conf格式配置无法连接，通过查看json配置，发现缺失了httpSettings和tlsSettings数据

conf配置内容
参考ws的方法：
Proxy-H2, vmess1, vmess1://[email protected]:443/h2?network=http&tls=true
或是从kitsunebi复制的配置URL：
Proxy-H2, vmess1, vmess1://[email protected]:443/h2?network=http&http.host=&tls=true&tls.allowinsecure=true

转换后的json均为以下内容

{
  "protocol": "vmess",
  "tag": "Proxy-H2",
  "settings": {
    "vnext": [
      {
        "users": [
          {
            "id": "12345678-90ab-cdef-1234-567890abcdef"
          }
        ],
        "address": "xxx.xxx.xxx",
        "port": 443
      }
    ]
  },
  "streamSettings": {
    "network": "http",
    "security": "tls"
  }
}

geosite.dat不支持v2ray中的一些规则

helper目录下的geosite.dat和v2ray/domain-list-community仓库中提供的（v2ray自带）不一致，缺少了一些规则（如geolocation-!cn）
现在用的解决方法是安装或更新后手动替换在源码中替换后自行编译
可否将geosite.dat更换为和v2ray/domain-list-community一致的版本？

Windows 要求已数字签名的驱动程序

WINDOWS7 64位安装时报错

真der!好用我滴天！

用过v2rayU和v2rayX,但都不太好用，pac并不适合我，全局更加不方便。邮箱不能设置代理，所以我尝试下载了代理app的Proxifier，它是收费的，我下的破解版，但似乎和v2rayU发生了一些冲突，也有可能是我设置不当，反正很快就卸载了。我在手机上用的就是作者的Kitsunebi，在作者推特上看到了这个项目，出于Kitsunebi的良好使用体验，我尝试了mellow，尽管它并没有gui。
果然它就是我需要的，简单上手，谢谢作者的努力，它是我目前找到的最优秀的v2ray mac端的代理App，分流很好，邮箱也工作了。加油！看好Mellow！

Failed to start the core

log.txt

这个vmess配置怎么填呢

websocket + tls 类型的

dns设置无效

在cfg.json中配置dns地址后

 "dns": {
  "servers": [
        {
            "address": "8.8.8.8",
           "port": 53
      },
        {
            "address": "127.0.0.1",
            "port": 53,
            "domains": [
                "geosite:cn"
            ]
        }
    ]
},

dns依旧是设置成了223.5.5.5和1.1.1.1

[2019-09-10 12:44:41.101] [info] Core started.
[2019-09-10 12:44:41.497] [info] The default gateway before configuring routes:
[2019-09-10 12:44:41.499] [info] { gateway: '10.0.0.1', interface: '以太网' }
[2019-09-10 12:44:41.504] [info] The TUN interface before configuring routes:
[2019-09-10 12:44:41.505] [info] { address: '10.255.0.2', interface: 'mellow-tap0' }
[2019-09-10 12:44:41.506] [info] 2019/09/10 12:44:41 Start session stater.
2019/09/10 12:44:41 TAP device name: mellow-tap0
2019/09/10 12:44:41 Set mellow-tap0 with net/mask: 10.255.0.2/255.255.255.0 through DHCP
2019/09/10 12:44:41 Set mellow-tap0 with DNS: 223.5.5.5,1.1.1.1 through DHCP

Mellow做网关时 ，PC测试为FullCone 但 Switch 和 PS4 测试网络NAT类型分别是F和第三类

单独设置了UDP出口(SS)，PC测试是 FullCone （PC跑Mellow也是Full），但是PS4和NS都没有改善NAT。看Mellow日志NS是走了UDP出口。是哪里的问题呢？

搭配 ssr-libev 使用的问题

您好，我想将 Mellow 搭配 ssr 使用，目前尝试在本地运行 ssr 的 libev 版本，但是会导致连接失败；同样的配置，使用 ss 连接则没问题。cfg.json 的内容如下：

{
  "outbounds": [
    {
      "protocol": "socks",
      "settings": {
        "servers": [
          {
            "address": "127.0.0.1",
            "port": 9009
          }
        ]
      }
    },
    {
      "protocol": "freedom",
      "settings": {
        "domainStrategy": "UseIP"
      },
      "tag": "direct"
    }
  ],
  "routing": {
    "domainStrategy": "IPIfNonMatch",
    "rules": [
      {
        "app": ["ss-local", "ssr"],
        "type": "field",
        "outboundTag": "direct"
      }
    ]
  }
}

查看 ssr-libev 的输出信息，发现一直在报错：Request did not begin with TLS handshake.
在 Mellow 的 statistics 中发现，ssr 进程的所有 Download Bytes 均为 0.
请问该如何解决呢，谢谢

[新手问题] Mellow负载均衡能否自动更换可用代理

开发者，你好！

问题描述：Mellow负载均衡能否 自动选择可用outbound
原因：地区运营商间歇屏蔽 特定地址TCP连接，需要手动更换outbound

0.1.4版使用json配置文件，无法正常启动

Windows 0.1.3和0.1.4版本，选择json配置文件（该json在0.1.2版正常使用），都无法正常启动连接。没办法，只能重新建立了一个conf文件使用。

另外，能否增加一个按钮，可以快速查看”当前配置“（类似kitsunebi）

关于conf文件的配置，还有两个小问题
localhost = 127.0.0.1 这一行的作用是啥？
可不可以使用类似 DOMAIN-SUFFIX DOMAIN-FULL 之类的配置

dnsmasq监听0.0.0.0时Mellow拿不到代理服务器IP

Update:

和ss无关，dnsmasq监听在0.0.0.0造成的问题。

---

环境

• 系统 macOS 10.13.6
• Mellow 0.1.6

尝试使用如下格式 shadowsocks 协议代理无法连接网络，

Test, ss, ss://chacha20-ietf:[email protected]:10xxx

但是相同协议链接 ss://xxxx 在 V2RayU 能够正常使用。对比 "Running Confg" 配置和V2RayU中代理配置，未见ss协议内容部分有区别。此外，若使用其他Shadowsocks客户端配置本地代理监听在1080，而Mellow使用此1080口Socks代理也能正常连接。

大佬考虑做openwrt的luci吗？

win mac linux Android ios都有了，就差openwrt啦，期待大佬一统江湖！

Please give me instructions on how to configure

Looks great project, but don't know how to configure it, please take valuable time to point me to configure it, can I?
Or give me a tutorial, I follow the tutorial to learn.
I really need to learn configuration, please help me, thank you.

DNS中使用localhost导致DNS失效

猜测原因可能是mellow启动后，系统默认DNS变成了mellow的，导致这个DNS查询由mellow发出，mellow接受，无限循环。
可以考虑在启动前把localhost替换为本地DNS。

localhost在需要使用本地DNS，并且需要连接不同网络（本地DNS不同时）会相当有用。

下面是https://www.v2ray.com/chapter_02/04_dns.html 中关于localhost的解释

当值为"localhost"时，表示使用本机预设的 DNS 配置。
当使用 localhost 时，本机的 DNS 请求不受 V2Ray 控制，需要额外的配置才可以使 DNS 请求由 V2Ray 转发。

0.16版本出现Catalina状态栏上占位，但不显示图标的问题

mellow在正常工作，但图标空白，只是在状态栏上占据一个位置，点击可以打开面板。Catalina(19A602),目前的最新版本。

MELLOW0.0.7 安装完毕报错

MOLLOW 0.0.7 windows 版本在windows10上安装完毕报错，错误提示如图