Can't connect to Bitbucket Server
Following the instructions on https://confluence.atlassian.com/bitbucket/getting-started-with-vs-code-969520759.html I get a 404 when using my normal password and a 401 when using a personal access token.
From my keychain I have removed all items starting with atlas code_, removed all settings in the extension and restarted VS Code but to no avail.
I can however connect to my Bitbucket Cloud account.
Jira and Bitbucket 2.4.2
Jira v8.5.1
Bitbucket v? (cannot find the version) - I work at Signify, maybe that helps you to identify the version
VSCode 1.42.1
OSX 10.15.3
Comments (10)
-
Account Deactivated -
reporter Not sure, can ask the IT guys. I can however connect to the BB Server using IntelliJ and the Bitbucket Linky Plugin - can create PR’s as well.
-
reporter BTW, I can also connect to the Jira Server in VSC. Just the connection to the BB Server isn’t working.
-
I think i have the same issue.
Getting this when i try to connect our “custom BB site” with username password and custom self signed cert:
Request failed with status code 404
The output console with debug mode:
Error: Error authenticating with Bitbucket: Error: Request failed with status code 404 Error: Authentication error: Error authenticating with Bitbucket: Error: Request failed with status code 404
The server is up and i can reach it in the browser.
Jira part with the same settings works without any problem.
vscode version: 1.45.0 (insider)
Extension version: 2.5.1
BB version: 6.3.2 (server)
jira version: v8.2.1#802001 (server) -
Account Deactivated Can you please open up the Atlassian Settings page and on the General tab make usre Output level is set to debug and check the Enable Curl logging switch and try again?
It should give you a curl command with the request it’s trying to make. Can you please let me know what the request that’s getting the 404 is?
Thanks!
-
I think I have the same problem. I’m a gitnoob and would like to try to use this tool.
In the Bitbutcket tab, I’m able to successfully log into the Bitbucket cloud but above the authentication, I was getting a 404.
I discovered that I had logged into both the Jira cloud and the BitBucket cloud with the Bitbucket account. I deleted the Jira account, which solved the 404 error, but I still get “activating Bitbucket features failed” when I open VS. I then deleted http://atlassian.com from the connectivity but still get the error.
Under the general tab, I set the miscellaneous output to debug and the debug to output curl, but I don’t see any output.
-
Account Deactivated @textualDev Can you update to the latest version of the extension (2.6.4) and check if you still see the
activating Bitbucket features failed
message? -
reporter I’ve updated to 2.6.4 and the integration with custom Jira site works, just like before However, the integration with a custom Bitbucket site still consistently errors on Authentication. Bitbucket Cloud integration works as expected.
-
Same issue here @Peter Lorent . @{557057:3695b794-cde3-43a2-99aa-c0fc6151b754} I have enabled the curl output: (commented out anything I thought might be sensitive.
[2020-07-23 16:57:02:386] curl -X GET -H "User-Agent:atlascode/2.x axios/0.19.2" -H "X-Atlassian-Token:no-check" -H "Content-Type:application/json" -H "Authorization:Basic *************" "https://bitbucket.********.com/rest/api/1.0/users/**********?avatarSize=64" [2020-07-23 16:57:02:386] ---------------------------------------------------------------------- [2020-07-23 16:57:03:084] Error: Error authenticating with Bitbucket: Error: Request failed with status code 401 [2020-07-23 16:57:03:084] Error: Authentication error: Error authenticating with Bitbucket: Error: Request failed with status code 401
-
Account Deactivated @Kenneth Bonar What happens if you copy/paste that curl command into a terminal and run it? Do you still get a 401? If so, can you double check your credentials?
Basically, when you enter you “login” to a custom Bitbucket site with the extension, we just save your credentials in your keychain and then execute that curl command to retrieve your own user info as a test to make sure your credentials are correct. Meaning, there’s not really a way to “login” since we are using APIs without session cookies.
So if that above curl command is failing in a terminal, it means that the Basic auth is failing in general for some reason.
- Log in to comment
@Peter Lorent Are you behind a proxy server for your BB server?