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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.