SSL not showing servlet

Hi, I migrated from a previous version of Jira to JIRA (v6.2#6252-sha1:aa34325), working with http everything looks fine. But when I've enabled https at server.xml, and I point my browser to localhost:8443 it's not presenting the login page, instead it tries to download an empty file:

server.xml:

<Connector port="8443" maxHttpHeaderSize="8192" SSLEnabled="true"

maxThreads="150" minSpareThreads="25"

enableLookups="false" disableUploadTimeout="true" useBodyEncodingForURI="true"

acceptCount="100" scheme="https" secure="true"

clientAuth="false" sslProtocol="TLS"

keystoreFile="**masked**" keystorePass="**masked**" />

I can find the port up and running, and no error at catalina.log:

Mar 30, 2014 12:09:10 AM org.apache.catalina.core.AprLifecycleListener init

INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Atlassian\JIRA 4.3\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\;.

Mar 30, 2014 12:09:10 AM org.apache.coyote.AbstractProtocol init

INFO: Initializing ProtocolHandler ["http-bio-8080"]

Mar 30, 2014 12:09:10 AM org.apache.coyote.AbstractProtocol init

INFO: Initializing ProtocolHandler ["http-bio-8443"]

Mar 30, 2014 12:09:11 AM org.apache.catalina.startup.Catalina load

INFO: Initialization processed in 1365 ms

Mar 30, 2014 12:09:11 AM org.apache.catalina.core.StandardService startInternal

INFO: Starting service Catalina

Mar 30, 2014 12:09:11 AM org.apache.catalina.core.StandardEngine startInternal

INFO: Starting Servlet Engine: Apache Tomcat/7.0.47

Thanks in advance.

2 answers

This widget could not be displayed.

Do you bhave the redirect port in the non-ssl connector within server.xml? If possible you should try to use the JIRA Configuration Tool and see if results differ.

Using the browsers "developer tools" or a desktop proxy tool like WireShark will give you an idea if redirects are happening, and what the blank page if comimg from.

Manua; via tomcat - https://confluence.atlassian.com/display/JIRA050/Running+JIRA+over+SSL+or+HTTPS#RunningJIRAoverSSLorHTTPS-ConfigureHTTPSinTomcat

Auto Config via ui toOL

https://confluence.atlassian.com/display/JIRA/Running+JIRA+over+SSL+or+HTTPS

I tried with the autoconfig, and it's still not working.

This widget could not be displayed.
I tried with the autoconfig, and it's still not working.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

292 views 5 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you