Internal error: failed to create or connect to the perfect build environment. Don't worry, build should restart soon

Bitrise Build Issue Report template

Description of the issue

Builds repeatedly fail with the message:

Internal error: failed to create or connect to the perfect build environment. Don’t worry, build should restart soon.


On… (non-OS specific)

If on which stack? If not on on what operating system? (Plus any other information you can share)

The “Hobby” pricing tier.

I assume the stack is the “StandardMachine” - LINUX 2xCPU (n1)

Not applicable - build doesn’t even start.


  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? : EVERY TIME
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? : 12th August 2018

Local reproduction

Can it be reproduced on your own Mac/PC by following our local debug guide? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what will get when it does a git clone in the clean environment! If possible please note which sections you tried.

Local reproduction: Linux / Android (docker based) stack builds

Can it be reproduced by running the build locally, after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( Bitrise CLI )? If no, can it be reproduced with Docker (using the same docker images / environment we use on Related guide: Redirecting… .

Build log

No log to share.

Duplicate of Internal error: failed to create or connect to the perfect build environment ?


Status page is showing all green / 100% uptime… is that just the website?

Hi @nickgrealy,

Sorry for the inconvenience caused! Our team is investigating the issue. We are not yet sure about what could be causing the issue, but the status page should be up-to-date now and we’ll be posting details on the investagion/resolution.

Hi @nickgrealy ,
​The issue should be resolved now and the builds should be able to start on the MacOS machines. Sorry for the inconvenience caused!

1 Like