# Whitelistable IP range for build containers

**URL:** <https://discuss.bitrise.io/t/whitelistable-ip-range-for-build-containers/2664>\
**Category:** Question & Answer\
**Created:** [September 8, 2017, 10:08pm UTC](https://discuss.bitrise.io/t/whitelistable-ip-range-for-build-containers/2664 "2017-09-08T22:08:14Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![bootstraponline](https://avatars.discourse-cdn.com/v4/letter/b/c68b51/32.png) [@bootstraponline](https://discuss.bitrise.io/u/bootstraponline)\
**Post date:** [September 9, 2017, 2:35am UTC](https://discuss.bitrise.io/t/whitelistable-ip-range-for-build-containers/2664/2 "2017-09-09T02:35:02Z")

</div>

> Restrict by IP: configure your server to only allow connections from certain IP addresses. We don’t recommend this solution, as even if you restrict the IP range to [bitrise.io](http://bitrise.io) build machine IPs, that means that anyone who runs builds on [bitrise.io](http://bitrise.io) will be allowed to communicate with your servers. Additionally, we only have fix IPs for our Mac build machines, the Linux stacks are hosted on Google Compute Engine and we use emphemeral IPs there, so the range is GCE’s ephemeral IP range.
> 
> [How to configure bitrise to access an internally hosted git repository](http://discuss.bitrise.io/t/how-to-configure-bitrise-to-access-an-internally-hosted-git-repository/85)

---

_[View the full topic](https://discuss.bitrise.io/t/whitelistable-ip-range-for-build-containers/2664)._