Hello,
As the title says, I am currently creating a system to access multiple Ignition servers through an Nginx reverse proxy server. I have not found a clean solution for this yet, and was wondering if anyone has experience doing this.
Ideally each server would be under it's own subpath, so:
company. com/ignition-one/
company. com/ignition-two/
However, it seems when Ignition tries to open a websocket connection, both try to connect to ws://company-proxy/ which could not be resolved.
It seems for Ignition to sent proper websocket connections, It needs either a subdomain, or a port, so:
ignition-two. company.com/
ignition-one. company.com/
OR
company. com:4000/
company. com:4001/
I have got the system working with ports, however this is not optimal, as there will potentially be ~40 servers connected (most traffic will not go through the reverse proxy), as well as other applications, so having clear names would be best.
Does anyone have experience setting up multiple servers under a reverse proxy? Is there some way to serve Ignition from a subpath, or a subdomain?
Thanks in advance for the feedback! 
Subpath, no. Subdomain, yes.
For the latter, just tell Ignition that its public hostname is that subdomain. You'll likely want the proxy to handle SSL, and have Ignition trust the proxy's substitute client headers.
3 Likes
We have about a dozen development gateways running behind Traefik, each accessible by subdomain (client-subdomain.dev.our-company.com).
Yeah this is how we do it.
Care to post your site configuration?