# Deploy network errors

**URL:** <https://travis-ci.community/t/deploy-network-errors/7153>\
**Category:** Deployment\
**Tags:** deployment, script-deployment, github-releases\
**Created:** [February 8, 2020, 5:32pm UTC](https://travis-ci.community/t/deploy-network-errors/7153 "2020-02-08T17:32:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![DanySK](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/danysk/32/1399_2.png) [@DanySK](https://travis-ci.community/u/DanySK)\
**Post date:** [February 8, 2020, 5:32pm UTC](https://travis-ci.community/t/deploy-network-errors/7153/1 "2020-02-08T17:32:25Z")

</div>

Hi,  
are the deploy network commands wrapped with `travis_retry` internally? Every some time, I get build failures like [this one](https://travis-ci.org/DanySK/Experiment-2019-FGCS-Self-Integration/jobs/647434233)\*:

```auto
Failed to open TCP connection to api.github.com:443 (Connection timed out - connect(2) for "api.github.com" port 443) (Faraday::TimeoutError)

```

It’s my understanding that behind the scenes Travis uses such function to prevent this kind of failures. Does it do it also for releases deploy?

- [archived link](http://archive.ph/S81vB), in case I need to re-run the build.