You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Description:
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.
Action:
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
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: https://confluence.atlassian.com/bitbucketserver/securing-bitbucket-server-with-tomcat-using-ssl-776640127.html
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: https://confluence.atlassian.com/bitbucketserver/proxying-and-securing-bitbucket-server-776640099.html
Regards,
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.
Regards,
Ram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Team the issue got fixed after creating a new PFX file and updated in the server.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.