Getting 401 issues when pushing code 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
User is having issues pushing code to Bitbucket.
Environment
Bitbucket 7.15.0
Yet Another Commit Checker
Diagnosis
The following is seen in the GIT client logs:
1
2
3
4
5
6
7
8
9
10
11
12
13
Enumerating objects: 78, done.
Counting objects: 100% (78/78), done.
Delta compression using up to 12 threads
Compressing objects: 100% (18/18), done.
Writing objects: 100% (23/23), 2.29 KiB | 1.15 MiB/s, done.
Total 23 (delta 8), reused 0 (delta 0)
10:31:52.601447 pkt-line.c:80 packet: sideband< \2Push rejected by YACC (c).-.(c) (c).-.(c) (c).-.(c) (c).-.(c) (c).-.(c) / ._. \ / ._. \ / ._. \
remote: Push rejected by YACC
remote:
...
10:31:52.765729 pkt-line.c:80 packet: sideband< \2ternal error: Unexpected response received. Status code: 401. Check server logs for details.
remote: refs/heads/BIT-1234-13-0: b08ec91551362110752eab23c66b921b2a18d7b8: JIRA: Internal error: Unexpected response received. Status code: 401. Check server logs for details.
remote: Bitbucket logs show:
1
Unexpected response received. Status code: 401Cause
This is caused by third-party plugin Yet Another Commit Checker.
Solution
It is recommended to revisit the plugin configuration for the affected repository.
Also, you may want to either look to upgrade this plugin if possible and see if that resolves the issue, or that you look to disable this plugin entirely.
Otherwise, you can consult with the support resources for the vendor of this plugin for assistance with this behavior, as this is not something that was created or is maintained by Atlassian.
Was this helpful?