Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Bitbucket can't start on 443 over HTTPS.

Alikhan Damirov
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 28, 2019

Hello,

my configuration file look like:

#>*******************************************************
#> Migrated to database at jdbc:oracle:thin:@//bitbucketdb.kapitalho.az:1521/bitdb
#> Updated by Bit Bucket Admin on 2018-08-15T14:26:02.593+04:00
#>*******************************************************
jdbc.driver=oracle.jdbc.driver.OracleDriver
jdbc.url=jdbc:oracle:thin:@//bitbucketdb.XXX.XX:1521/bitdb
jdbc.user=bitdbadmin
server.port=443
server.ssl.enabled=true
server.ssl.key-store=/etc/ssl/certs/fullchain.jks
server.ssl.key-store-password=123456


Please view the log file: 

2019-01-28 12:38:11,585 INFO [main] o.s.boot.SpringApplication 
. ____ _ __ _ _
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/ ___)| |_)| | | | | || (_| | ) ) ) )
' |____| .__|_| |_|_| |_\__, | / / / /
=========|_|==============|___/=/_/_/_/
:: Spring Boot :: (v1.5.12.RELEASE)


2019-01-28 12:38:11,947 INFO [main] c.a.b.i.b.BitbucketServerApplication Starting BitbucketServerApplication on bitbucket.kapitalbank.az with PID 14447 (/opt/atlassian/bitbucket/5.12.0/app/WEB-INF/classes started by atlbitbucket in /)
2019-01-28 12:38:11,947 INFO [main] c.a.b.i.b.BitbucketServerApplication No active profile set, falling back to default profiles: default
2019-01-28 12:38:14,229 INFO [main] c.a.b.i.boot.log.BuildInfoLogger Starting Bitbucket 5.12.0 (02c9a7a built on Mon Jul 09 08:19:52 AZT 2018)
2019-01-28 12:38:14,229 INFO [main] c.a.b.i.boot.log.BuildInfoLogger JVM: Oracle Corporation OpenJDK 64-Bit Server VM 1.8.0_181-b13
2019-01-28 12:38:16,501 ERROR [main] o.a.catalina.core.StandardService Failed to start connector [Connector[HTTP/1.1-443]]
org.apache.catalina.LifecycleException: Failed to start component [Connector[HTTP/1.1-443]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
at org.springframework.boot.context.embedded.tomcat.TomcatEmbeddedServletContainer.addPreviouslyRemovedConnectors(TomcatEmbeddedServletContainer.java:265)
at org.springframework.boot.context.embedded.tomcat.TomcatEmbeddedServletContainer.start(TomcatEmbeddedServletContainer.java:208)
at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.startEmbeddedServletContainer(EmbeddedWebApplicationContext.java:297)
at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.finishRefresh(EmbeddedWebApplicationContext.java:145)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546)
at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:122)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
at com.atlassian.bitbucket.internal.boot.BitbucketServerApplication.start(BitbucketServerApplication.java:246)
at com.atlassian.bitbucket.internal.boot.BitbucketServerApplication.main(BitbucketServerApplication.java:82)
at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
at com.atlassian.bitbucket.internal.launcher.BitbucketServerLauncher.start(BitbucketServerLauncher.java:151)
at com.atlassian.bitbucket.internal.launcher.BitbucketServerLauncher.main(BitbucketServerLauncher.java:99)
... 5 frames trimmed
Caused by: org.apache.catalina.LifecycleException: Protocol handler start failed
at org.apache.catalina.connector.Connector.startInternal(Connector.java:1020)
... 16 common frames omitted
Caused by: java.net.SocketException: Permission denied
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
... 16 common frames omitted
2019-01-28 12:38:20,685 WARN [spring-startup] c.a.stash.internal.home.HomeLock Failed to write process information into the lock file
java.nio.channels.ClosedByInterruptException: null
at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
at sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:216)
at com.atlassian.stash.internal.home.HomeLock.acquireLock(HomeLock.java:127)
at com.atlassian.stash.internal.home.HomeLock.lock(HomeLock.java:98)
at com.atlassian.sbitdbadmintash.internal.home.HomeLockAcquirer.lock(HomeLockAcquirer.java:58)
at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:151)
at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:687)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:525)
at javax.servlet.GenericServlet.init(GenericServlet.java:158)
at java.lang.Thread.run(Thread.java:748)
... 27 frames trimmed

 

 The final error:

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

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.

2019-01-28 12:39:24,615 INFO [main] c.a.b.i.boot.log.BuildInfoLogger Bitbucket 5.12.0 has shut down

 

Can someone tell me what i'm doing wrong ?

Thanks in advance.

1 answer

0 votes
Charly [DEISER]
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.
January 28, 2019

Hi @Alikhan Damirov

In your configuration file you have:

server.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

There you have all the info you need to secure your bitbucket web access using HTTPS.

Hope this helps!

Charly [DEISER]
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.
January 28, 2019

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

What you are doing right now is using the Tomcat to secure your connection but this can be the cause of a lot of performance issues.

Alikhan Damirov
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 28, 2019

Hi @Charly [DEISER].

Thanks for your reply. 

Before creating this task i'm checking port usage via netsat and lsof. 

There are no any processess which use this port. 

I accepted your advice and configure nginx as reverse proxy and problem is fixed. 

Thanks you!

But, why this port is in use when i'm start the bitbucket - i'm really don't understand. 

Thank you again!

Charly [DEISER]
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.
January 28, 2019

Hi @Alikhan Damirov

In that case probably the problem was a wrong configuration setup. i'm glad you were able to configure the connection using nginx.

Regards

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events