[Support] Help with socks5 on Heroku

Hello.
I trying:

~/bin $ ./chisel_linux_amd64 server --port 9312 --socks5
2017/08/27 18:08:00 server: SOCKS5 Enabled
2017/08/27 18:08:00 server: Fingerprint 2b:01:b4:8b:26:a5:24:5a:e2:b8:02:fa:58:96:ee:35
2017/08/27 18:08:00 server: Listening on 9312

but got

./chisel_linux_amd64 client --fingerprint 2b:01:b4:8b:26:a5:24:5a:e2:b8:02:fa:58:96:ee:35  https://pacific-refuge-52999.herokuapp.com:9312 1080:socks
2017/08/27 21:10:49 client: Connecting to wss://pacific-refuge-52999.herokuapp.com:9312
2017/08/27 21:10:49 client: tunnel#1 127.0.0.1:1080=>socks: Listening
2017/08/27 21:10:50 client: Retrying in 100ms...
2017/08/27 21:10:52 client: Retrying in 200ms...
2017/08/27 21:10:53 client: Retrying in 400ms...
2017/08/27 21:10:55 client: Retrying in 800ms...
2017/08/27 21:10:57 client: Retrying in 1.6s...

What am I doing wrong?

telnet pacific-refuge-52999.herokuapp.com 9312
Trying 23.23.116.0...
Trying 23.21.155.56...
Trying 23.23.120.204...
Trying 23.23.117.76...
Trying 23.21.142.10...
Trying 23.21.45.51...
Trying 23.21.181.176...
Trying 23.23.126.158...
telnet: Unable to connect to remote host: Connection refused

Start by reproducing the server and client commands shown in the issue, then check the Heroku deployment and whether port 9312 is reachable. Compare the server's listening behavior with the client's retry logs and telnet connection refusal. Done means identifying the configuration or deployment cause and confirming that the SOCKS5 tunnel connects successfully.