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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

New SSL Certificate Not Loading in Bitbucket Server

We have uploaded the new SSL Certificate for Bitbucket in the linux server and when we try to start the bitbucket server we are getting below error 
We use that only refer the pfx file(new file)
PFB - Error 


The Tomcat connector configured to listen on port 443 failed to start. The port may already be in use or the connector may be misconfigured.


Verify the connector's configuration, identify and stop any process that's listening on port 443, or configure this application to listen on another port.

2022-07-18 10:42:11,490 INFO  [main]  c.a.b.i.boot.log.BuildInfoLogger Bitbucket 5.12.0 has shut down

Whenever we tried to install the new certificate. the java process is not listening on 443 and getting the log as port utilized by some other service. we have also checked the 443 has not been used for any service

1 answer

0 votes

Hi @Engineering Services :

As per the error, its not related to certificate issue. Please, find the process which is using port 443, It looks like there is a different application using that port (usually nginx or apache)

Check this site:

Please, use below commands:

sudo lsof -i -P -n | grep LISTEN
sudo netstat -tulpn 


By the way i would recommend using an apache or nginx reverse proxy configuration:



Mahesh Shinde

Mahesh, thanks for your suggestion.

When we checked from our end we could see whenever we install the certificate and starting the bitbucket service. It is started with different port number and it is not listening on port 443. We have also verified that 443 is not been used by any services.



Team the issue got fixed after creating a new PFX file and updated in the server.

Like Mahesh Shinde likes this

Glad to hear, that issue got fix.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events