I've been using laravel forge for a long time with my bit bucket account. However suddenly I'm getting this error: I've contacted their customer support and said that this is simply the response they're getting from bitbucket. What can I do to investigate this?

No worries - glad you got sorted.

Yes, the user has proper access and I tried to refresh the token few times also, unliked the user and attached another user with role Admin. The same thing. I did a workaround now, and it worked. I have imported the repository to GitHub and installed the site via GitHub then I updated the GIT remote using custom to the BitBucket repository again. Thanks for your suggestions Matt.

Have you tried updating your server provider config? For example, I was using Linode and had to create a 2nd version of it to allow new access keys etc... ## EDIT ## And you are definitely a user on your bitbucket project repo? - pointing out the obvious I know!

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

cannot connect laravel forge to bitbucket

Abdullah Bakhach

I've been using laravel forge for a long time with my bit bucket account. However suddenly I'm getting this error:

Laravel Forge _ prod1-n 2018-07-30 20-24-53.png

I've contacted their customer support and said that this is simply the response they're getting from bitbucket. What can I do to investigate this?

Accepted answers

All comments

Abdullah Bakhach

when I try to add the ssh key from forge to bitbucket, it claims that someone else is already using it:

Laravel Forge _ prod1-n 2018-07-31 16-53-11.png

Andy White_tf3lrg

Did you solve this issue? I'm suddenly having problems with Forge and Bitbucket communicating too

vkcash

I have the same problem. Did anybody solve it? Please, help.

nicolas_r

Same problem here. Used it for a year without hassle. And now that I urgently need to redeploy it doesn't longer work. Nevertheless the SSH key in general settings, is correct...