kimw

@koolwiki Try following commands on server box. * `free -m` * `uname -a`

@koolwiki My guess is the issue is occured cause of swap limitation. AFAIK the swap issue is a known golang issue. Try, * Change to a larger swap VPS will...

Did you try to build GQ from source? There's some new patch since the last release out.

@hybtoy It's just a suggestion. Maybe it works, maybe not. Let's see it. --- BTW, build GQ from source code is easy to practice. 1. Download the binary package from...

Here's the remove steps maybe is useful for you, 1. Remove user's workspace, `rm -rf ~/go` 2. Remove user's bash envs ```sh sed -i -e '/^export PATH=\/usr\/local\/go\/bin:$PATH$/d;' ~/.bashrc sed -i...

@hybtoy Please try the attached one, which should output like, ```text 2018-04-09 19:49:23 INFO: initializing acl... 2018-04-09 19:49:23 INFO: plugin "/usr/local/bin/gq-server" enabled 2018-04-09 19:49:23 INFO: initializing ciphers... aes-128-gcm 2018-04-09 19:49:23...

> Have you considered the possibility that NAT might mess with your cache? Namely, if two clients behind the same NAT router try to connect to the same server with...

More words: If a shadowsocks server supports only countable user/users, it's abnormal behavior too. -- Following on this idea, maybe a later SIP should about exchange shadowsocks in a kind...

> I wonder if a better option is to define a new SOCKS command. Why overload the existing commands (CONNECT), and make their implementations more complicated, if you can have...

> If an app can try SOCKS command, it already know the server password. @studentmain Not at all. The APP, which trying to make connections thru SOCKS, only knows about:...