Describe the bug
Websocket and SSH connections times out in 30 seconds
To Reproduce
Steps to reproduce the behavior (Websocket):

Steps to reproduce the behavior (SSH):

Expected behavior
SSH and websocket connections should no time out
Desktop (please complete the following information):
Additional context
Duplicate of https://github.com/Jigsaw-Code/outline-server/issues/85
Confirmed by @fortuna on https://github.com/Jigsaw-Code/outline-server/issues/85#issuecomment-498804252
Thank you all.
It seems that this is an issue specific to our Electron-based clients: Windows and Linux.
I checked whether we were disabling the timeout for ss-local, but it seems we are:
https://github.com/Jigsaw-Code/outline-client/blob/91a46da368f35faffa4b81efa6919fd334206224/src/electron/process_manager.ts#L340
@alalamav any ideas? Maybe it's something to do with tun2socks?
Hi @helnokaly, we are working on a fix (#634) to this issue. shadowsocks-libev v3.3.0 disables client timeouts and I have verified that with this update ssh and websockets do not timeout. I'll follow up once the fix has been merged.
Fixed and released. See https://github.com/Jigsaw-Code/outline-server/issues/85
Most helpful comment
Hi @helnokaly, we are working on a fix (#634) to this issue. shadowsocks-libev v3.3.0 disables client timeouts and I have verified that with this update ssh and websockets do not timeout. I'll follow up once the fix has been merged.