We are having a problem that occurs not very often, but it is annoying.
We try to run composer in a pipeline step and to install pimcore v11 packages that sometimes fails.
It is always the same error and we do not have a clue what the problem could be, because these are public repositories but the result is either a connection timeout or permission denied.
Does anyone have a hint what could cause the problem, because we cannot control the connection params, it should just work.
Following the error:
Downloading php-http/discovery (1.19.4)
Failed to download php-http/discovery from dist: curl error 28 while downloading https://api.github.com/repos/php-http/discovery/zipball/0700efda8d7526335132360167315fdab3aeb599: Connection timeout after 10002 ms
Now trying to download from source
- Syncing php-http/discovery (1.19.4) into cache
In Git.php line 471:
Failed to clone https://github.com/php-http/discovery.git via https, ssh pr
otocols, aborting.
Cloning into bare repository '/composer/cache/vcs/https---github.com-php-
http-discovery.git'...
fatal: unable to access 'https://github.com/php-http/discovery.git/': Fai
led to connect to github.com port 443 after 131203 ms: Connection timed out
- git@github.com:php-http/discovery.git
Cloning into bare repository '/composer/cache/vcs/https---github.com-php-
http-discovery.git'...
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Hi Andreas,
I would recommend creating a support ticket for this issue, as we're probably going to need additional debug information and check the build logs.
You can create a ticket via https://support.atlassian.com/contact/#/; in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as a product. When you are asked to provide the workspace URL, please make sure you enter the URL of the workspace that is on a paid billing plan to proceed with ticket creation.
Kind regards,
Theodora
Hello,
Looks like a global issue, we have this timeout in 1 out of 10 pipeline runs, for some months.
Maybe there is something wrong in bitbucket runners network.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nicolas,
You can create a ticket with the support team for investigation.
I provided the steps to create a support ticket in my previous reply.
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.