[build] SQLSTATE[HY000] [2002] Connection timed out

[Dev1]

Hello,

My YML file, but facing issue [build] SQLSTATE[HY000] [2002] Connection timed out :
Please explain why this happend.

image: quay.io/hypernode/deploy:3-php8.1-node18

pipelines:

  branches:

    staging:

      - step:

          name: Build

          script:

            - hypernode-deploy build -vvv

            - php deploy-static.php

          services:

          - mysql

          artifacts:

            - build/**

          caches:

            - composer

      - step:

          name: Deploy

          deployment: staging

          script:

            - mkdir -p ~/.ssh

            - echo "$SSH_PRIVATE_KEY" | base64 --decode > ~/.ssh/id_rsa

            - chmod 600 ~/.ssh/id_rsa

            - eval "$(ssh-agent -s)"

            - ssh-add ~/.ssh/id_rsa

            - ssh-keyscan [REDACTED]>> ~/.ssh/known_hosts

            - hypernode-deploy deploy staging -vvv

            - php deploy-static.php

definitions:

  services:

    mysql:

      image: mysql:5.7

      variables:

        MYSQL_DATABASE: [REDACTED]

        MYSQL_USER: [REDACTED]

        MYSQL_PASSWORD: [REDACTED]

        MYSQL_RANDOM_ROOT_PASSWORD: [REDACTED]

[Jim Knepley - ReleaseTEAM]

Hi @Dev1. Welcome to the community.

"Connection timed out" means that the build runner tried to connect to a system (like a database) and didn't get a response. This is different from "Connection refused," which indicates the remote system actively rejecting the connection, usually because the service isn't running.

In my experience, your error is a network connectivity issue, often caused by a firewall or ACL between the runner and the database, or sometimes a misconfigured route between subnets.

[Dev1]

hypernode-systemctl whitelist add database 34.233.65.54 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 34.196.8.197 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 44.194.7.14 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 34.199.54.113 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 34.232.25.90 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 34.232.119.183 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 34.236.25.177 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 35.171.175.212 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 52.54.90.98 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 52.202.195.162 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 52.203.14.55 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 52.204.96.37 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 34.218.156.209 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 34.218.168.212 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 52.41.219.63 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 35.155.178.254 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 35.160.177.10 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 34.216.18.129 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 3.216.235.48 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 34.231.96.243 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 44.199.3.254 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 174.129.205.191 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 44.199.127.226 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 44.199.45.64 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 3.221.151.112 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 52.205.184.192 --description "Bitbucket Pipelines" &&
hypernode-systemctl whitelist add database 52.72.137.240 --description "Bitbucket Pipelines"

we have whitelists ips but getting same issue

[Ben]

Hi @Dev1 

If whitelisting does not resolve the issue, please raise a support ticket. You have a paid workspace and are entitled to support from our support team. A ticket is required for our engineers to access your workspace and check your YML/build logs/environment in detail:

• https://support.atlassian.com/

Please let me know your timezone if you are having difficulties raising a ticket, and I will raise one on your behalf.

Cheers!

- Ben (Bitbucket Cloud Support)

[Ben]

Hi @Dev1 

I am echoing what Jim has commented on this post. The connection timing out implies that the remote database server you're trying to connect to may be blocking the connection. Please refer to our IP address documentation - particularly the "Valid IP addresses for Bitbucket Pipelines build environments" subheading and ensure these are whitelisted:

• https://support.atlassian.com/bitbucket-cloud/docs/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall/

If you need further support, please raise a support ticket. You have a paid workspace and are entitled to support from our support team. A ticket is required for our engineers to access your workspace and check your YML/build logs/environment in detail:

• https://support.atlassian.com/

Also - I redacted sensitive information, as this is a public forum and you have shared your remote database URL and its password publicly...

Cheers!

- Ben (Bitbucket Cloud Support)

[Dev1]

we are still getting issue: please check below error

task magento:config:import
[staging:test.hypernode.io] ssh '-p' '22' '-A' '-o' 'ControlMaster=auto' '-o' 'ControlPersist=60' '-o' 'ControlPath=/dev/shm/app@test.hypernode.io:22' 'app@test.hypernode.io' ': c87a2fbba333724371e3; bash -ls'
[staging:test.hypernode.io] run php /data/web/apps/test.hypernode.io/releases/15/./bin/magento app:config:status
[staging:test.hypernode.io] Warning: include(/data/web/apps/test.hypernode.io/releases/15/vendor/composer/../../generated/code/Magento/Framework/App/ResourceConnection/Proxy.php): Failed to open stream: No such file or directory in /data/web/apps/test.hypernode.io/releases/15/vendor/composer/ClassLoader.php on line 571
[staging:test.hypernode.io] error in magento2.php on line 121:
[staging:test.hypernode.io] exit code 1 (General error)
done magento:config:import 574ms
ERROR: Task magento:config:import failed!

[Ben]

Hi @Dev1 

I have raised a support ticket on your behalf, please check your email for further correspondence.

In future- for any pipelines issues, troubleshooting requires access to your workspace and build environment which is only possible with a support ticket (our system requires this from us) so you may raise a support ticket here:

https://support.atlassian.com/contact/

Cheers!

- Ben (Bitbucket Cloud Support)