Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bitbucket Pipeline - Wget Timeout

Hi, community

WGET (Apache resources)

In a bitbucket pipeline, I have defined some simple bash for getting Apache Ant resources and I frequently got a connection timeout. The following snippet is the result of Wget when it timeouts:

--2021-11-29 11:46:30--

Resolving (, 2a01:4f8:172:2ec5::2

Connecting to (||:443... failed: Connection timed out.

Connecting to (|2a01:4f8:172:2ec5::2|:443... failed: Network is unreachable.


I provide the single step to simulate the error (used image:amazoncorretto:11)

 if [[ ! -d /opt/apache-ant-1.10.8 || ! -f /opt/apache-ant-1.10.8/bin/ant ]]; then 

echo "Ant directory not exists!"


tar -xzf apache-ant-1.10.8-bin.tar.gz -C /opt

Temporary solution:  I restart the pipeline until a Wget success.
Note: On my localhost, I never experienced this type of error for reaching Apache. Is docker introducing a TLS problem or other issues? Is there a way to fix this connectivity problem?

1 answer

0 votes
Mark C Atlassian Team Feb 17, 2022

Hi @Jacopo Orlandini

Thank you for reaching out to the community.

I did try to run the wget command below in my test Pipelines.
However, I'm able to download the file without issue.
My YAML file configuration looks like below:

image: amazoncorretto:11

    - step:
        name: Test
          - yum install wget -y
          - wget

Would it be possible for you to confirm if you're still experiencing the same issue?

Mark C

At this stage, this problem does not occur anymore and I ran multiple pipelines in the meanwhile. Thank you for your investigation. 

Like Mark C likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

3,449 views 3 10
Read article

Atlassian Community Events