Error on ubuntu 18.04 client

[s-nobakht]

I have a problem on Ubuntu 18.04 LTS. I setup a server with Shadowsocks & Cloak using HirbodBehnam's script. Everything works fine with Windows & Android clients. But, unfortunately, I could not use the client in Ubuntu 18.04 as Hirbod described in here. I double and triple checked the entire workflow. Everything seems good but, I do not have access to internet through the client. I also described the issue here. The log of our listening server on the client is as below:

sn@sn-pc:~/apps/cloak$ ss-local -s xxx.xxx.xxx.xxx -p 443 -l 1080 -k "xxxxxxxxxx" -m chacha20-ietf-poly1305 --plugin ./ck-client-linux-amd64-2.1.2 --plugin-opts ./ckclient.json
 2019-12-21 01:52:06 INFO: plugin "./ck-client-linux-amd64-2.1.2" enabled
 2019-12-21 01:52:06 INFO: initializing ciphers... chacha20-ietf-poly1305
 2019-12-21 01:52:06 INFO: listening at 127.0.0.1:1080
INFO[0000] Listening on TCP 127.0.0.1:52745 for shadowsocks client 
INFO[0003] Attemtping to start a new session            
DEBU[0003] All underlying connections established       
INFO[0003] Session 3683454610 established               
DEBU[0033] attempting to actively close session 3683454610 
DEBU[0033] a connection for session 3683454610 has closed: read tcp 192.168.100.18:57834->xxx.xxx.xxx.xxx:443: use of closed network connection 
DEBU[0033] a connection for session 3683454610 has closed: read tcp 192.168.100.18:57826->xxx.xxx.xxx.xxx:443: use of closed network connection 
DEBU[0033] a connection for session 3683454610 has closed: read tcp 192.168.100.18:57832->xxx.xxx.xxx.xxx:443: use of closed network connection 
DEBU[0033] a connection for session 3683454610 has closed: read tcp 192.168.100.18:57830->xxx.xxx.xxx.xxx:443: use of closed network connection 
DEBU[0033] session 3683454610 closed gracefully         
INFO[0068] Attemtping to start a new session            
DEBU[0068] All underlying connections established       
INFO[0068] Session 1997913006 established 

My ckclient.json file is like-this:

{
	"Transport": "direct",
	"ProxyMethod": "shadowsocks",
        "EncryptionMethod":"plain",
        "UID":"MY-UID",
        "PublicKey":"MY-PUBLIC-KEY",
        "ServerName":"www.bing.com",
        "NumConn":4,
        "BrowserSig":"chrome",
        "StreamTimeout": 300
}

I checked the shadowsocks server on my client. It seems that is in a proper status:

sn@sn-pc:~$ systemctl status shadowsocks-libev
● shadowsocks-libev.service - Shadowsocks-libev Default Server Service
   Loaded: loaded (/lib/systemd/system/shadowsocks-libev.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2019-12-21 02:14:58 +0330; 1min 7s ago
     Docs: man:shadowsocks-libev(8)
 Main PID: 9722 (ss-server)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/shadowsocks-libev.service
           └─9722 /usr/bin/ss-server -c /etc/shadowsocks-libev/config.json -u

Dec 21 02:14:58 sn-pc systemd[1]: Started Shadowsocks-libev Default Server Service.

[cbeuw]

Hi, what does the log say for ck-server? Can you see the new session? Does it provide a reason for closing the sessions?

[s-nobakht]

@cbeuw Sorry for late.
The server log is as below:

ck-server[32707]: time="2020-01-18T05:42:56-08:00" level=info msg="Session closed" UID="znIN89zggdGKtJPNt7R9F1Q==" reason="Received a closing notification frame" sessionID=1932201206