Unbit

do you have logs of the vpn-ws server ? are you sure nginx is correctly communicating with it ?

you should post nginx configuration and the full comand line of the vpn-ws server

ensure nginx has write access over /run/vpn.sock, eventually strace the vpn-ws process to udnerstand what is going on

I think adding an header in the response with the api version could be a good solution: X-uwsgi.it-Api-Version: 1

ok, the same thing applies, it can add a request header specifying the version it expects

Note: we need to only protect port 999 (currently we have only iptables rule protecting it) port 999 is where the tuntap router is bound

This will be required for implementing the solution described here: #18

Well if suid apps can be run in a container it is a security problem (expecially for users having their custom distros). I think your second config misses a line...

Consider integrating it into the api, every container could have a number of SocketMonitor objects mapped to it

Hi, maybe it is better to open it for https://github.com/20tab/uwsgiit_console as it looks like a gui bug.