Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,558,376
Community Members
 
Community Events
184
Community Groups

HTTP to HTTPS redirection on confluence

Hi Team,

 

I would like to ask your help on applying SSL on confluence. We have done the steps from 1 - 5 of this document https://confluence.atlassian.com/conf613/running-confluence-over-ssl-or-https-964961473.html however, we encounter error on accessing the site. 

Redirection from old 8090 url is different from 8443 URL. For example:

Old HTTP URL is: http://servername:8090 
New HTTPS UR is: https://servername.domain.com:8443

When we change web.xml as stated in step 5 of this document https://confluence.atlassian.com/conf613/running-confluence-over-ssl-or-https-964961473.html, we encountered mismatched address issue on certificate. How can we delete or avoid or is there a way that we can set the new name on web.xml or server.xml files? Thank you.

mismatched_error.JPG

2 comments

Anton Chemlev - Toolstrek -
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 18, 2019

Hi,

What is the site address you issued certificate for?

Our previous URL is  http://(servername):8090/ not FQDN. The certificate has FQDN means  servername.company.com

http://servername.company.com:8443/

We have done some proxying on the server.xml that resolves the problem.

Modify the server.xml, since we have working http://servername, we need to do proxying and comment out default port.

> Comment out the Connector port="8090" code block
>Uncomment Connector port="8443", you can change it to 443 so users will not adding 8443 at the end of the URL.
>Add <Connector port="8090" protocol="HTTP/1.1" proxyName="example.com" connectionTimeout="20000" redirectPort="443"> this is an addition for the redirection to work, you need to redirect the site to a different name say http://servername.com to https://example.com.

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events