title: "How to use NGINX as a reverse-proxy server for a Node.js application using socket.io"
---
Despite the long name of the article, I have a feeling this may apply to more people than I might think.
If you have a Node.js application which needs socket.io connections that you want to pass throgh nginx's `reverse_proxy` directive then this is the article for you!
You *must* seperate the socket.io sockets and the static resources.
* The socket connections can be routed through the default `$host/socket.io` if you want to ease modifications to the source code.
* The connections to your main npm Node.js application can be routed through the relevant directory.
Here is the relevant part of my `projects.tait.tech.conf` file: