Jira SSL on Ubuntu Server not Working

[Brandon Smith]

Hey all. 

I know this has a couple of articles on here and I have followed them to try and get this working.

I am on a fresh headless ubuntu 18.04 server.
I have created a keystore following the advanced configuration instructions in this guide https://confluence.atlassian.com/adminjiraserver/running-jira-applications-over-ssl-or-https-938847764.html
I have created my CSR and provided it to my CA and received a wild card cert using this command keytool -certreq -alias jira -file my_file.csr -keystore <JIRA_HOME>jira.jks

My CA gave me a PKCS#7 key with extension .p7b
I have imported the key using the instructions in this guide https://www.namecheap.com/support/knowledgebase/article.aspx/9441/33/installing-an-ssl-certificate-on-tomcat/
using this command keytool -import -trustcacerts -alias tomcat -file yourcertificate.p7b -keystore yourkeystore.jks

I am able to reach Jira at https://10.x.x.x:8080 but it states it is not secure.

I have reconfigured my server.xml file in many different ways.
This is my most recent attempt.
Thank you for taking the time to take a look at this. Any input you might have is appreciated.

<Connector port="8080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;" 
    SSLEnabled="true" clientAuth="false" maxThreads="150" sslProtocol="TLS"
    minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
    maxHttpHeaderSize="8192" protocol="HTTP/1.1"
    useBodyEncodingForURI="true" redirectPort="443"
    acceptCount="100" disableUploadTimeout="true" bindOnInit="false"
    secure="true" scheme="https" proxyName="*.mydomain.com" proxyPort="8443"
    keyAlias="jira" keystoreFile="/opt/atlassian/jira/jirs.jks"
    keystorePass="CHANGEME" keystoreType="JKS"/> 

[Brandon Smith · Accepted solution]

I was attempting to access the server by IP. Since this did not match the domain, *.domain.com, it reported the connection was not secure. Once I had my DNS records in place and was access the site from, jira.domain.com, it reported the connection was secure.