Hello.
I encountered a problem using wireguard-ui unix-sockets behind an nginx reverse-proxy. The reason was the default file mode of the unix-socket, which I couldn't fix by chmod'ing before starting wireguard-ui, because wireguard-ui would always reset the file mode.
My fix in the code sets the socket to be world read-writable. This enables the nginx reverse-proxy to use it without problems.
Hello. I encountered a problem using wireguard-ui unix-sockets behind an nginx reverse-proxy. The reason was the default file mode of the unix-socket, which I couldn't fix by chmod'ing before starting wireguard-ui, because wireguard-ui would always reset the file mode.
My fix in the code sets the socket to be world read-writable. This enables the nginx reverse-proxy to use it without problems.