Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

fatal: could not read Username for 'https://bitbucket.org': No such device or address

stuart.stephen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 17, 2023

We have a Jenkins pipeline that checks out the code from https://bitbucket.org/company/repo.git. This has been working fine for the last 3-4 years, but started failing over the weekend with the error "fatal: could not read Username for 'https://bitbucket.org': No such device or address".

The issue does not occur during checkout, that seems fine, but instead when we run the command "git fetch --prune --prune-tags origin" on the checked out workspace.

We found a solution to include the username and password in the URL, which is fine, it seems to work, but various posts on here seem to suggest switching to SSH keys instead.

  1. Why did it break? We did not update any software.
  2. Is the https://user:pass@bitbucket.org/company/repo.git a good solution, or should we be looking to move to SSH for longevity?

Thanks,
Stuart

1 answer

0 votes
Syahrul
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 17, 2023

G'day @stuart.stephen 

Welcome to the community.

I have reviewed the recent changes and existing customer reports, and I can confirm that there have been no recent changes or reports of customers experiencing the same issue.

However, it's challenging to pinpoint the exact cause since the Jenkins server is hosted on your end. That said, I can confirm that using username:app_password behavior aligns with the expected outcome when using HTTPS.

To prevent similar issues in the future, I recommend switching to SSH.

I hope this information is helpful.

Regards,
Syahrul

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events