Missed Team ’24? Catch up on announcements here.

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

bitbucket not working after configured the SSL

laknath July 23, 2019

Getting below error after config the nbitbucket.properties file. Please assist. 

The Tomcat connector configured to listen on port 7990 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 7990, or configure this application to listen on another port. 2019-07-24 09:22:12,415 INFO [main] c.a.b.i.boot.log.BuildInfoLogger Bitbucket 6.4.1 has shut down 

 

 

 

1 answer

0 votes
Alexis Robert
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 24, 2019

Hi @laknath , 

 

can you share what is in your bitbucket.properties configuration file ? 

Also, make sure that you don't already have a zombie instance of Bitbucket still running (you may reboot your server for example if you're not sure).

 

Let me know if this helps, 

 

--Alexis

laknath July 24, 2019

Hi @Alexis Robert 

Pls refer the below.

 

server.port=7990
server.ssl.enabled=true
server.ssl.key-store=/opt/atlassian/bitbucket.jks
server.ssl.key-store-password=dexter@123

Alexis Robert
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 24, 2019

Hi @laknath , 

 

can you add 

server.scheme=https

to your bitbucket.properties file and restart Bitbucket ? 

 

Thanks, 

 

--Alexis

Like laknath likes this
laknath July 28, 2019

now getting below error while integrate with jira users  with bitbuckcet directory. 

 

Pls refer the below application error

Connection test failed. Response from the server:
javax.net.ssl.SSLPeerUnverifiedException: Certificate for <10.62.160.66> doesn't match any of the subject alternative names: [*]

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events