Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Https does work - Jira

I have "Verify the certificate exists within the KeyStore", but when I run with "https...", it's doesn't work

2 answers

0 votes
Dirk Ronsmans Community Leader Apr 09, 2021

Hi @Nataliia Pavlenko ,

i'm assuming you are using a Server/Datacenter setup (your tags mention a lot of cloud)?

Could you maybe elaborate a bit on the issue (a screenshot could help but also more words describing what is going on/what you've already tried/...)

If so, did you also enable the right connectors on your tomcat configuration (server.xml) for https? 

Hi @Dirk Ronsmans ,

I have a server, and this instuction https://confluence.atlassian.com/adminjiraserver/running-jira-applications-over-ssl-or-https-938847764.html#RunningJIRAapplicationsoverSSLorHTTPS-commandline

I do this :

  1. Generate the Java KeyStore
  2. Verify the certificate exists within the KeyStore

Then I edit the HTTPS connector so that it has the parameters that point to the KeyStore in server.xml and run start-jira.sh
When jira started, she's stay only this 

Screenshot from 2021-04-09 11-33-50.png

Dirk Ronsmans Community Leader Apr 09, 2021

well even tho it says it's ready to serve it does mention your tomcat is misconfigured:

image.png

did you maybe upgrade and copy over your old server.xml? Cause these files change with versions

I do this, but have the same

Screenshot from 2021-04-09 11-55-43.png

Dirk Ronsmans Community Leader Apr 09, 2021

No, don't copy your old file. You actually have to use the file that comes with the installation and adjust that server.xml connector

Here's the explanation

https://confluence.atlassian.com/jirakb/jira-server-startup-fails-with-tomcat-misconfigured-error-958453799.html

I have this in my server.xml

Well Jira says you don't..  did you uncomment the connector?

Also, since it is "ready to serve" what happens when you actually browse to it (http and https)?

Dirk Ronsmans Community Leader Apr 09, 2021

Since you have 2 connectors could you also add the handling to the 8443 connector

relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>" 

I did it and it went further but again stopped at something else and my site only loading and stop

Screenshot from 2021-04-09 13-04-20.png

Dirk Ronsmans Community Leader Apr 09, 2021

That will just take time.. don't see anything in the logs.. 

I would give it a couple of minutes. If you did upgrade it will need to run a bunch of maintenance tasks too

@Dirk Ronsmans When I want go to https://localhost:8443/ it's doesn't work, but when go to http://localhost:8080 it's works

it's weird because I want to go to that address and that's why I change it all

Dirk Ronsmans Community Leader Apr 09, 2021

Well that makes sense.. your connector is 8080 (http) which redirects to 8443 (https)

When you go to http://localhost:8080 are you redirected to HTTPS or it remains HTTP?

If you want only HTTPS, why not just remove the HTTP connector and change the port on your HTTPS connector?

It doesn't redirect to 8080, I tried to comment out the code with http://localhost:8080/ so that only 8443, it's doesn't work

in this case, https://localhost:8443/ it simply does not open

Dirk Ronsmans Community Leader Apr 09, 2021

If I were you I'd start fresh with the out of the box server.xml (for the version you currently have) and

  1. start with a single connector (HTTP)
  2. move to a single HTTPS connector
  3. if you need it set up a redirect but for that I would even suggest using a Reverse proxy system

You about something like this, when I used only one. If yes, I tried it, it's doesn't work

Screenshot from 2021-04-09 14-28-10.png

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Why everyone using Jira must be GDPR-compliant

Did you know that penalties up to 4 % of the yearly company turnover are possible in case of GDPR violations? GDPR regulations are currently mainly relevant for companies in the EU, but countries lik...

49 views 0 0
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you