Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Bitbucket does not start

burak.turgut
burak.turgut February 22, 2019

After upgrading to 6.01, bitbucket did not started this morning and workarounds does not help , either. 

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

Description:

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-02-22 12:13:17,869 INFO [main] c.a.b.i.boot.log.BuildInfoLogger Bitbucket 6.0.1 has shut down

but my configfile is 

server.require-ssl=true
server.redirect-port=8443
server.secure=true
server.scheme=https
server.proxy-port=80

When I enter the bitbucket address I receive: 

502 - Web server received an invalid response while acting as a gateway or proxy server.

Any help will be highly appreciated. 

Answer
Watch
Like Be the first to like this
9895 views

2 answers

0 votes
Julian Governale
Julian Governale
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
March 21, 2024

For anyone else who only sees the last section of the error, it can be a bit misleading.  Review the full error in the application log to understand the full error.  In the few times we have seen this issue, it was due to the following factors

  • SSL cert being used had the wrong password set up in the bitbucket properties files or server.xml file (depending on version)
  • The permissions to the cert file were not set back up after the upgrade and bitbucket couldn't read the cert file 

For some reason, the error indicates the port is in use, but in our case, it was not, the application couldn't access the SSL to start the connection on the indicated port.

Reply
0 votes
Alexis Robert
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.
Become a leader
February 22, 2019

Hi @burak.turgut , 

 

did you follow the Atlassian documentation when implementing SSL ? I think at least your "server.proxy-port=80" is wrong and should be 

server.port=8443

 

Let me know if it works, 

 

--Alexis 

View More Comments
burak.turgut
burak.turgut February 22, 2019

Thanks for your help @Alexis Robert 

when I change that I am receiving 

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

Description:

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

2019-02-22 12:52:11,158 INFO [main] c.a.b.i.boot.log.BuildInfoLogger Bitbucket 6.0.1 has shut down

But netstat does not showing any process on that port 

 

Proto Local Address Foreign Address State
TCP 0.0.0.0:80 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:135 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:443 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:445 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:1801 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:2103 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:2105 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:2107 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:2701 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:3389 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:5985 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:33541 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:47001 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:49664 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:49665 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:49666 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:49667 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:49668 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:49669 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:49670 SVPIIS115TR1802:0 LISTENING
TCP 0.0.0.0:49671 SVPIIS115TR1802:0 LISTENING
TCP 127.0.0.1:7992 SVPIIS115TR1802:0 LISTENING
TCP 127.0.0.1:7993 SVPIIS115TR1802:0 LISTENING
TCP 127.0.0.1:63390 SVPIIS115TR1802:0 LISTENING
TCP 127.0.0.1:64536 SVPIIS115TR1802:64537 ESTABLISHED
TCP 127.0.0.1:64537 SVPIIS115TR1802:64536 ESTABLISHED
TCP 127.0.0.1:64538 SVPIIS115TR1802:64539 ESTABLISHED
TCP 127.0.0.1:64539 SVPIIS115TR1802:64538 ESTABLISHED
TCP 127.0.0.1:64540 SVPIIS115TR1802:64541 ESTABLISHED
TCP 127.0.0.1:64541 SVPIIS115TR1802:64540 ESTABLISHED
TCP 127.0.0.1:64542 SVPIIS115TR1802:64543 ESTABLISHED
TCP 127.0.0.1:64543 SVPIIS115TR1802:64542 ESTABLISHED
TCP 127.0.0.1:64544 SVPIIS115TR1802:64545 ESTABLISHED
TCP 127.0.0.1:64545 SVPIIS115TR1802:64544 ESTABLISHED
TCP 127.0.0.1:64546 SVPIIS115TR1802:64547 ESTABLISHED
TCP 127.0.0.1:64547 SVPIIS115TR1802:64546 ESTABLISHED
TCP 127.0.0.1:64548 SVPIIS115TR1802:64549 ESTABLISHED
TCP 127.0.0.1:64549 SVPIIS115TR1802:64548 ESTABLISHED
TCP 127.0.0.1:64550 SVPIIS115TR1802:64551 ESTABLISHED
TCP 127.0.0.1:64551 SVPIIS115TR1802:64550 ESTABLISHED
TCP 127.0.0.1:64552 SVPIIS115TR1802:64553 ESTABLISHED
TCP 127.0.0.1:64553 SVPIIS115TR1802:64552 ESTABLISHED
TCP 127.0.0.1:64554 SVPIIS115TR1802:64555 ESTABLISHED
TCP 127.0.0.1:64555 SVPIIS115TR1802:64554 ESTABLISHED
TCP 127.0.0.1:64556 SVPIIS115TR1802:64557 ESTABLISHED
TCP 127.0.0.1:64557 SVPIIS115TR1802:64556 ESTABLISHED
TCP 127.0.0.1:64558 SVPIIS115TR1802:64559 ESTABLISHED
TCP 127.0.0.1:64559 SVPIIS115TR1802:64558 ESTABLISHED
TCP 127.0.0.1:64560 SVPIIS115TR1802:64561 TIME_WAIT
TCP 192.168.188.191:80 host-82-222-226-198:54674 ESTABLISHED
TCP 192.168.188.191:80 host-82-222-245-134:64735 ESTABLISHED
TCP 192.168.188.191:139 SVPIIS115TR1802:0 LISTENING
TCP 192.168.188.191:3389 192.168.7.83:49507 ESTABLISHED
TCP 192.168.188.191:62833 40.67.252.206:https ESTABLISHED
TCP 192.168.188.191:62890 SVPDBS004TR1801:10123 ESTABLISHED
TCP 192.168.188.191:63385 40.67.254.36:https ESTABLISHED
TCP 192.168.188.191:64454 ankara-110:https TIME_WAIT
TCP 192.168.188.191:64455 ankara-110:https TIME_WAIT
TCP 192.168.188.191:64462 151.139.236.192:https TIME_WAIT
TCP 192.168.188.191:64463 151.139.236.192:https TIME_WAIT
TCP 192.168.188.191:64464 104.28.12.54:https TIME_WAIT
TCP 192.168.188.191:64465 104.28.12.54:https TIME_WAIT
TCP 192.168.188.191:64471 vip1:https TIME_WAIT
TCP 192.168.188.191:64472 152.70.32.11:https TIME_WAIT
TCP 192.168.188.191:64473 152.70.32.11:https TIME_WAIT
TCP 192.168.188.191:64475 68.232.35.116:https TIME_WAIT
TCP 192.168.188.191:64498 host-213-14-249-131:4343 TIME_WAIT
TCP 192.168.188.191:64505 95.85.28.202:https CLOSE_WAIT
TCP 192.168.188.191:64531 ec2-52-30-92-203:https CLOSE_WAIT
TCP 192.168.188.191:64562 40.77.226.249:https TIME_WAIT
TCP 192.168.188.191:64572 host-213-14-249-131:4343 ESTABLISHED
TCP 192.168.188.191:64573 PKT-AMS-01:https ESTABLISHED
TCP 192.168.188.191:64574 PKT-AMS-01:https ESTABLISHED
TCP 192.168.188.191:64575 95.85.28.202:https ESTABLISHED
TCP 192.168.188.191:64576 95.85.28.202:https ESTABLISHED
TCP [::]:80 SVPIIS115TR1802:0 LISTENING
TCP [::]:135 SVPIIS115TR1802:0 LISTENING
TCP [::]:443 SVPIIS115TR1802:0 LISTENING
TCP [::]:445 SVPIIS115TR1802:0 LISTENING
TCP [::]:1801 SVPIIS115TR1802:0 LISTENING
TCP [::]:2103 SVPIIS115TR1802:0 LISTENING
TCP [::]:2105 SVPIIS115TR1802:0 LISTENING
TCP [::]:2107 SVPIIS115TR1802:0 LISTENING
TCP [::]:2701 SVPIIS115TR1802:0 LISTENING
TCP [::]:3389 SVPIIS115TR1802:0 LISTENING
TCP [::]:5985 SVPIIS115TR1802:0 LISTENING
TCP [::]:33541 SVPIIS115TR1802:0 LISTENING
TCP [::]:47001 SVPIIS115TR1802:0 LISTENING
TCP [::]:49664 SVPIIS115TR1802:0 LISTENING
TCP [::]:49665 SVPIIS115TR1802:0 LISTENING
TCP [::]:49666 SVPIIS115TR1802:0 LISTENING
TCP [::]:49667 SVPIIS115TR1802:0 LISTENING
TCP [::]:49668 SVPIIS115TR1802:0 LISTENING
TCP [::]:49669 SVPIIS115TR1802:0 LISTENING
TCP [::]:49670 SVPIIS115TR1802:0 LISTENING
TCP [::]:49671 SVPIIS115TR1802:0 LISTENING
TCP [::1]:7992 SVPIIS115TR1802:0 LISTENING
TCP [::1]:7993 SVPIIS115TR1802:0 LISTENING

Like
Alexis Robert
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.
Become a leader
February 22, 2019

yes that's weird, I don't see anywhere port 8443 in your output.

Maybe you can try restarting the server just in case ? 

Like
burak.turgut
burak.turgut February 22, 2019

I already did :) not helping 

Like
burak.turgut
burak.turgut February 22, 2019

May this be the reason? 

Caused by: java.lang.IllegalArgumentException: Integrity check failed: java.security.UnrecoverableKeyException: Failed PKCS12 integrity checking

Like
Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
TAGS
AUG Leaders

Atlassian Community Events

    See all events