# Docker Hub: You have reached your pull rate limit

**URL:** https://travis-ci.community/t/docker-hub-you-have-reached-your-pull-rate-limit/10517
**Category:** Travis CI Discussions & Feedback
**Tags:** docker
**Created:** [November 10, 2020, 2:23pm UTC](https://travis-ci.community/t/docker-hub-you-have-reached-your-pull-rate-limit/10517 "2020-11-10T14:23:07Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)
#### Post date: [November 10, 2020, 2:28pm UTC](https://travis-ci.community/t/docker-hub-you-have-reached-your-pull-rate-limit/10517/2 "2020-11-10T14:28:50Z")

</div>

> [@"iv undefined" in openssl invocation](https://travis-ci.community/t/iv-undefined-in-openssl-invocation/6614/6):
>
> Check if your build is getting this encrypted variable. E.g. PR builds don’t have access to encrypted variables (unless the PR branch is from the same repository).

> [@"iv undefined" in openssl invocation](https://travis-ci.community/t/iv-undefined-in-openssl-invocation/6614/7):
>
> So what’s the solution to the PRs from forks in github?

> [@"iv undefined" in openssl invocation](https://travis-ci.community/t/iv-undefined-in-openssl-invocation/6614/8):
>
> @abhisekp To not use encrypted files, or a least not use them in external PR builds. Anything that you give external PRs access to is effectively public information because they contain untrusted code. An external pull request can be detected in build logic with this Bash condition (see [https://docs.travis-ci.com/user/environment-variables/#default-environment-variables](https://docs.travis-ci.com/user/environment-variables/#default-environment-variables)): [[$TRAVIS\_PULL\_REQUEST != "false" && $TRAVIS\_PULL\_REQUEST\_SLUG != "$TRAVIS\_REPO\_SLUG"]]

---

_[View the full topic](https://travis-ci.community/t/docker-hub-you-have-reached-your-pull-rate-limit/10517)._