nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

HTTPs for JIRA with Letsencrypt

Weiqi Yao

Hello,

I am currently working on integrate our JIRA website with Letsencrypt to implement HTTPs to our JIRA website. Since I am a newbie on the SSL/certificate implemtation, and our JIRA based on Tomcat/Nginx, which I have no experience before. I tried to follow this guide , but I got time out errors after configure that. I noticed the browser did redirect my http request to https, but the website became unavailable after that.

I am wondering if someone done the same thing maybe can help me out, or share some idea?

Thanks,

Weiqi

Accepted answers

Weiqi Yao

Finally I found the issue is just because of my EC2 security group is blocking the port 8443. The SSL certificate implementation is correct.

All comments

Alexey Matveev

Hello,

SSL certificate has nothing to do with integration. SSL secures traffic. That is all. Try the official Altassian guide on how to setup SSL:

https://confluence.atlassian.com/adminjiraserver071/running-jira-applications-over-ssl-or-https-802593051.html

Weiqi Yao

Hello Alex,

Thank you for the quick reply. I did checked the official docs on how to implement the SSL for JIRA, but that doesn't exactly fit for my situation.

I am using letsencrypt signed cert, here is what I did:

1. Use keytool to create an new Java keystore first.

2. Use keytool to create CSR from above keystore

3. Use Letsencrypt script certbot-auto to get an public certificate based on the CSR file

4. Use keytool to import this public cert into an Java Keystore.

After above 4 steps, I followed the official document edit the server.xml file, point it to my Keystore. Howefver, I again got timing out error on port 8443(I didn't tried the redirect step yet) .

Do you see any possibilities may cause the timing out error?

Thanks!

Weiqi Yao

Looks like the issue is not about the SSL/certificate, but more about the networking side.

Because I've tried check the port 8443 via openssl command on jira server itself and it succeed, returns:

Verify return code: 0 (ok)

However, when I use the same command on other servers, just replaced the "localhost" to <my jira public domain name>, I again got time out error message:

[root@sandbox02 certs]# openssl s_client -CApath /etc/ssl/certs/ -connect <my jira domain>.com:8443
 socket: Connection timed out
 connect:errno=110

But I did see the server is listening on port 8443, why the server won't respond to HTTPs requests? Actually, more likely the HTTPs request from outside even cannot been established.

Thanks!

Alexey Matveev

If the server does not respond to an http request, then check if there is no firewall.

Weiqi Yao

Finally I found the issue is just because of my EC2 security group is blocking the port 8443. The SSL certificate implementation is correct.

Nathan Brand

There is an excellent guide to setting up letsencrypt with tomcat over at the letsencrypt community site: https://community.letsencrypt.org/t/configuring-lets-encrypt-with-tomcat-6-x-and-7-x/32416

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-core

ssl

https