"no DAV locking support" errors while pushing to Bitbucket
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
"no DAV locking support" errors while pushing to Bitbucket and some other errors on the UI.
Diagnosis
Issue 1: XML error: not well-formed (invalid token)
The following errors can be seen while trying to push via Git terminal:
1
2
3
4
5
git push
XML error: not well-formed (invalid token)
error: no DAV locking support on '<https URL>'
fatal: git-http-push failed
error: failed to push some refs to '<https URL>'The issue could be intermittent and get resolve automatically within a few minutes.
Issue 2: The requested URL was rejected. Please consult with your administrator.
You might also see the following message in the UI when you try to access the Bitbucket URL:
The requested URL was rejected. Please consult with your administrator.
Your support ID is: <XXXXXXXXXXXXXXXX>
Issue 3: "You appeared to have cloned an empty repository" during clone
Check if there's a specific user who encountered the issue "You appear to have cloned an empty repository" during this test. Also try to clone the repository over SSH and confirm if you encounter the same error on SSH as well.
Cause
Issue 1
The Git push/pull failures could be caused by OS patching or even due to the proxy.
Issue 2/3
There could be some issue at F5 side and causing the message to occur when you try to access Bitbucket.
Solution
Firstly, for all the above issues, work with the networking team to resolve any firewall or F5/VPN related issues.
Issue 1
Check the Git client and server version, you need a Git 1.6.6+ in order to support the smart-http protocol
There could also be some issue after OS patching and that causes the
httpfailure ofgit push/pull.Try to bypass proxy: How do I bypass a proxy for Bitbucket Server
Issue 2
This error is related to F5. Check with your network team to review F5/VPN in the network in place.
Issue 3
Restart Bitbucket, that also works in resolving this issue and you'll be able to clone successfully.
Was this helpful?