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
Highlighted

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 Community Leader 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
Community showcase
Published in Bitbucket

Powering DevOps with Bitbucket Server & Data Center

Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster   ! While we’re all excited about the new improvements to Bitbucket ...

1,542 views 0 6
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