bitbucket DIY backup lock bitbucket failed with 503 error

[Bozhao Jiang]

I'm getting 503 error when trying to lock bitbucket with mvc/maintenance/lock call. My bitbucket instance is running behind apache httpd server. Any idea how to fix it? 

The command and error messages:

/usr/bin/curl -L -v -f -u xxx:xxx https://bitbucket.xxx.com/mvc/maintenance/lock

* About to connect() to bitbucket.xxx.com port 443 (#0)

*   Trying x.x.x.x ...

* Connected to bitbucket.xxx.com (x.x.x.x) port 443 (#0)

* Initializing NSS with certpath: sql:/etc/pki/nssdb

*   CAfile: /etc/pki/tls/certs/ca-bundle.crt

  CApath: none

* SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

* Server certificate:

*         start date: Nov 07 18:10:00 2018 GMT

*         expire date: Nov 06 18:10:00 2021 GMT

*         common name: bitbucket.xxx.com

* Server auth using Basic with user 'xxx'

> GET /mvc/maintenance/lock HTTP/1.1

> Authorization: Basic SHVkc29uOkh1ZHMwbjEy

> User-Agent: curl/7.29.0

> Host: bitbucket.xxx.com

> Accept: */*

>

* The requested URL returned error: 503

* Closing connection 0

curl: (22) The requested URL returned error: 503

[Dave Theodore [Coyote Creek Consulting] · Accepted solution]

Is your script using the curl command you list? That is a REST API call, so you will need to send a payload in order for the call to do what you want it to. Your command doesn't include any command.

If you use the Atlassian provided client, it should just work. We use it frequently and haven't had issues with it. Here's the doc. It's easiest to run it locally on the Bitbucket server.  When you do that, you can simply point to http://127.0.0.1:7990 (assuming you haven't changed the default port.) That will bypass your proxy and any SSL related challenges that may be involved.

[Bozhao Jiang]

Awesome. You are right, pointing to 127.0.0.1:7990 works. Thanks much for the help!