community
cancel
Showing results for 
Search instead for 
Did you mean: 

alteryx server Discussions

Find answers, ask questions, and share expertise about Alteryx Server.
#SANTALYTICS

The highly anticipated Alteryx Community tradition is back! We hope you'll join us!

Learn More
We will be upgrading the Gallery to our 2019.4 release this Saturday, December 7th beginning at 9:00am MT. We expect the outage to take last approx. 2.5 hours.

alteryx AWS ALB SSL

Highlighted
Atom

I need to set up alteryx server gallery to use SSL and allow our users to connect through an application load balancer. I've configured an ssl cert on the ALB and have a self signed ssl cert on the alteryx server (for the time being) however I can't open the gallery while using the alb dns name. It works fine if I use the server FQDN. When accessing it via the ALB, all I get in chrome is "

Analytics Gallery

 
Loading...
 
whereas if I use IE, it just shows a blank page. Is this because the SSL and dns names are for the ALB and alteryx server itself are different? If so, is there any way we can have a SSL cert for the servers FQDN but still use something like https://alteryx-gallery.somedomain.com ? I tried changing the friendly name in MMC with the above setup to alteryx-gallery.somedomain.com but that did not change a thing. If I use https://alteryx-gallery.somedomain.com in the gallery URL config the service fails to start even if I have a SSL cert (self signed at this point) for this url
 
Looking at the console in chrome, there's a lot of 400 errors
 
Failed to load resource: the server responded with a status of 400 ()
/gallery/css/cloud.css?v=12345 Failed to load resource: the server responded with a status of 400 ()
cloud.header.css Failed to load resource: the server responded with a status of 400 ()
/gallery/css/cloud.footer.css?v=12345 Failed to load resource: the server responded with a status of 400 ()
production.css Failed to load resource: the server responded with a status of 400 ()
production.js:199 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
send @ production.js:199
production.js Failed to load resource: the server responded with a status of 400 ()

Hello,

I have a Gallery with similar configuration and users are complaining because of a lot of HTTP 400 errors.

My Gallery is being an AWS ALB. I have an SSL cert on the ALB and a self-signed on the gallery server. 

Were you able to resolve your problem and if you don't mind sharing what did you do I appreciate it.

 

Thank you,

 

Mario.