1. Attempting to run git push with LFS content over HTTPS returns
Authentication required: Authorization error: https://my-repo.example.com/rest/git-lfs/storage/KEY/core/3259926e58a6d4e0b4551574a2666d8763ba51dec95aba14006cf4c1d69f9b7b
Check that you have proper access to the repository
error: failed to push some refs to 'https://my-repo.example.com/scm/KEY/core.git'
2. When executed with set GIT_TRACE=1 I see following error codes:
23:11:51.075721 trace git-lfs: tq: starting transfer adapter "basic"
23:11:51.076719 trace git-lfs: HTTP: PUT https://my-repo.example.com/rest/git-lfs/storage/KEY/core/3259926e58a6d4e0b4551574a2666d8763ba51dec95aba14006cf4c1d69f9b7b
23:11:51.241317 trace git-lfs: HTTP: 401B | 34 KB/s
23:11:51.241317 trace git-lfs: HTTP: {"errors":[{"context":null,"message":"You are not currently licensed to use Bitbucket.\nPlease contact your administrator to resolve this issue.","exceptionName":"com.atlassian.bitbucket.auth.InactiveUserAuthenticationException"}]}
3. The BitBucket is under reverse proxy of Apache2 over SSL. Pushing without LFS data works just fine
If you need any more information I'll be glad to provide them
Version: Bitbucket v6.10.0
---
I find it a bit rude to mark as SPAM when this is actual issue (especially as you don't allow direct contact for us - starter users)
The solution, if anyone come here from Google:
- after updating BitBucket, the cert profiles will not be moved automatically. I had missed root CA for my SSL, therefore the SSL was "untrusted" by the BitBucket. The solution is to move cert files manually into jre/security/cacert
Still, the error message is misleading...
