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,459,434
Community Members
 
Community Events
176
Community Groups

Bitbucket SSL bitbucket.properties

Hello! I've followed a series of guides and community posts but am unable to start my BitBucket instance.

I get the following error:

***************************
APPLICATION FAILED TO START
***************************

Description:

The Tomcat connector configured to listen on port 8492 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 8492, or configure this application to listen on another port.

2018-09-12 12:33:31,198 INFO  [main]  c.a.b.i.boot.log.BuildInfoLogger Bitbucket 5.14.0 has shut down

My bitbucketproperties is as follows:

server.port=8092
server.address=10.1.3.17
server.redirect-port=8492
server.compression.enabled=true
server.compression.mime-types=text/css,text/html,text/javascript,text/json,text/plain,text/xml,text/x-javascript,\application/javascript,application/json,application/x-javascript,application/vnd.git-lfs+json

server.additional-connector.1.port=8492
server.additional-connector.1.address=10.1.3.17
server.additional-connector.1.secure=true
server.additional-connector.1.scheme=https
server.additional-connector.1.ssl.protocol=TLSv1.2
server.additional-connector.1.ssl.enabled=true
server.additional-connector.1.server.ssl.key-store=C:/CERTIFICATES/ExtremeWildcard.jks
server.additional-connector.1.ssl.key-store-password=***
server.additional-connector.1.ssl.key-password=***
server.additional-connector.1.ssl.key-alias=bitbucket
server.additional-connector.1.proxy-port=8492
server.additional-connector.1.ssl.client-auth=want
server.additional-connector.1.ssl.key-store-type=JKS

 I cannot see what would be causing this not to start.

Kind regards,

Kai

1 comment

edwin Rising Star Sep 13, 2018

Hi @Kai Leppanen,

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

There is multiple entries in your file for port 8492. Did you get this resolved?

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events