TAC shows a blank page when accessed through AWS Elastic Load Balancer

[Anonymous]

I've recently installed a TAC server in AWS and placed behind an Elastic Load Balancer (ELB).  The ELB directs port 80 incoming to port 80 on the TAC server; it also passes 443 (https) traffic to port 80 on the TAC server. When I access http://my.server/org.talend.administrator, everything works fine.  If I instead go through https://my.server/org.talend.administrator, I receive a blank page instead of the login page.  What do I need to modify so that the login page displays properly over https through a load balancer?

[Anonymous]

We are facing the same issue.
We had a TAC 6.1 running in http behing a AWS HTTPS ELB which was receiving 443 request and transfering it to our server on port 80.
Everything was working fine but since we upgraded to TAC 7.x it's not working anymore. I can just see a blank page and no error are showing up.
If we use HTTP during the whole process it works fine.
Please let us know how to fix this behavior.

[Anonymous]

This worked for me.  Note that by doing this, you'll start getting the blank page when going to 80; only HTTPS will work if you modify it this way.

First, comment these sections in server.xml:

  <!--

 <Connector port="8080" protocol="HTTP/1.1"

           connectionTimeout="20000"

           redirectPort="8443" />

-->

<!-- A "Connector" using the shared thread pool-->

<!--

<Connector executor="tomcatThreadPool"

          port="8080" protocol="HTTP/1.1"

          connectionTimeout="20000"

           redirectPort="8443" />

-->

Then, add the following Connector, changing "your.url.here.com" to the DNS entry for your load balancer:

<Connector

  port="8080"

  protocol="HTTP/1.1"

  proxyPort="443"

  scheme="https"

  secure="true"

  proxyName="your.url.here.com"

  connectionTimeout="20000"

  URIEncoding="UTF-8"

/>

Hope this helps!

[Anonymous]

Oh, and restart your server once you've changed server.xml

[Anonymous]

TI had to clear the temp and work folders and i worked fine after a restart!

Thank you very much for your help!

[hshermes]

Hi

We have the same issue . We are offloading ssl configuration at the ELB level and using http for TAC. So like User >> HTTPS: Amazon ELB(SSL)>> HTTP: TAC 8080. 

When we first configured ALB with https listener the url to loadbalancer returned black page. We tried the workaround mentioned above and it worked and as mentioned the Direct connect using http is not working and it now returns a blank page.

Is there any way to make this work? During the instance when ALB is unavaailable we want to be able to log into individual instances using http.

We also found the issue seems to be on TAC only  the MDM Tac  which we also use seems to work both HTTPS ALB and HTTP direct to instance with default configuration on server.xml