Hi, I have setup a Stingray Traffic Manager to load balance a cluster of Node.js instances running on Joyant's Cloud infrastructure.  I am currently running into,  "No 'Access-Control-Allow-Origin' errors".  I understand why this is happening.  I need to enable my virtual server to allow Cross Origin Resource Sharing (CORS).  I don't know where to do that in the Stingray admin console.  Here is how I am currently managing my setup: 1) I Created a virtual server mapped to a subdomain and DNS, for example, "dashboard.mydomain.com". 2) Next I created 2 instances in my Pool, "dashboard1.mydomain.com" and "dashboard2.mydomain.com". 3) When I point my browser to the virtual server, "dashboard.mydomain.com", I get rerouted to "dashboard2.mydomain.com" as expected.  I have never been rerouted to the "dashboard1" instance.  When I initially set up the pool, I added "dashboard1" then "dashboard2".  Overall, I'm assuming this is ok.  I guess when the load increases "dashboard1" will eventually be used?  My application is written in JavaScript and uses XHR to make AJAX requests.  XHR honors the same origin policy so the server must allow cross domain access by setting the following response headers to enable CORS: 'Access-Control-Allow-Origin', '*' 'Access-Control-Allow-Methods', 'GET,PUT,POST,DELETE' My cluster instances, "dashboard1.mydomain.com" and "dashboard2.mydomain.com" are already configured for CORS.  I can independently make cross origin requests to those servers without issue.  However, when a cross domain request is made against the virtual server, "dashboard.mydomain.com", I get the "No 'Access-Control-Allow-Origin' errors".  I do have the ability to SSH into the virtual server, but I don't know how to configure it for CORS or know what web server it runs.  Any help would be greatly appreciated.  Thanks. Maxx  ... View more