Unbit

Have you installed and executed the server part ?

./vpn-ws-client /dev/tap0 wss://mydomain.com:port/vpn will do the trick

Which domain are you using in place of mydomain.com ? it looks like the system is not able to resolve it

you have to fix your ssl certificates in nginx. -9807 means "invalid certificate chain" If you do not have a valid certificate use the --no-verify option

once the tunnel is established you should route all (or part) of your traffic to the vpn interface. One of the ways (on osx) is: ``` route add default ```...

``` sudo route add my_vps_ip 182.16.0.1 ``` the problem is here, you have to set a default gw route not a route to the server

You have to set the default gw: ``` route add default 182.16.0.1 ``` before this, check 182.16.0.1 is reachable pinging it Oh and obviously hold a route to the vps:...

can you paste your routing table (the osx one) after the connection is established ?

it looks like you are not enabling the network interface like explained here: https://github.com/unbit/vpn-ws#the---exec-trick

Hi, you can add the --no-verify option to avoid certificate verification. Which webserver are you using ? are curl and the vpn-ws-client using the same libssl version ? npn is...