# balena deploy fails without any details exposed

**URL:** <https://forums.balena.io/t/balena-deploy-fails-without-any-details-exposed/367919>\
**Category:** balenaOS\
**Tags:** support\
**Created:** [May 11, 2023, 9:43pm UTC](https://forums.balena.io/t/balena-deploy-fails-without-any-details-exposed/367919 "2023-05-11T21:43:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![RodrigoM](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/rodrigom/32/5690_2.png) [@RodrigoM](https://forums.balena.io/u/RodrigoM)\
**Post date:** [May 11, 2023, 9:43pm UTC](https://forums.balena.io/t/balena-deploy-fails-without-any-details-exposed/367919/1 "2023-05-11T21:43:46Z")

</div>

Hi there,

We are trying to do a deployment of an application w/ barely any changes but we continuously see this error (`[Error] Deploy failed`).  
No further details are available, even when we run it with `--debug` flag.

How can we identify the cause of the problem?  
We are using Balena CLI 15.2.3 and macOS 13.3.1 (a).

```auto
balena deploy swx-edge-amd64-dev \
--build \
--source deploy-edge-amd64-dev \
--projectName swx-amd64 \
--multi-dockerignore --debug

```

```auto
[Build] aws-gg Successfully built 322df5988533
[Build] aws-gg Successfully tagged swx-amd64_aws-gg:latest
[Build] aws-gg Image size: 1.28 GB
[Build] swx-db Image size: 545.73 MB
[Build] swx-broker Image size: 799.85 MB
[Build] swx-schemes Image size: 1.73 GB
[Build] swx-stream-db Image size: 883.79 MB
[Build] swx-stream-db-cli Image size: 821.68 MB
[Build] Built 6 services in 3:06
[Info] Creating release...
[Error] Deploy failed

ServerError
    at wrapResponseError (/usr/local/lib/balena-cli/node_modules/@balena/compose/dist/release/models.js:59:19)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async Bluebird.map.concurrency (/usr/local/lib/balena-cli/node_modules/@balena/compose/dist/release/api.js:39:25)
From previous event:
    at processImmediate (internal/timers.js:464:21)
From previous event:
    at Object.create (/usr/local/lib/balena-cli/node_modules/@balena/compose/dist/release/api.js:38:20)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async createRelease (/usr/local/lib/balena-cli/build/utils/compose.js:47:40)
    at async runSpinner (/usr/local/lib/balena-cli/build/utils/compose_ts.js:817:16)
    at async deployProject (/usr/local/lib/balena-cli/build/utils/compose_ts.js:767:22)
    at async DeployCmd.deployProject (/usr/local/lib/balena-cli/build/commands/deploy.js:152:27)
    at async DeployCmd.run (/usr/local/lib/balena-cli/build/commands/deploy.js:50:25)
    at async DeployCmd._run (/usr/local/lib/balena-cli/node_modules/@oclif/command/lib/command.js:43:20)
    at async Config.runCommand (/usr/local/lib/balena-cli/node_modules/@oclif/config/lib/config.js:175:24)
    at async CustomMain.run (/usr/local/lib/balena-cli/node_modules/@oclif/command/lib/main.js:27:9)
    at async CustomMain._run (/usr/local/lib/balena-cli/node_modules/@oclif/command/lib/command.js:43:20)
    at async /usr/local/lib/balena-cli/build/app.js:76:13
    at async Promise.all (index 2)
    at async oclifRun (/usr/local/lib/balena-cli/build/app.js:94:5)
    at async Object.run (/usr/local/lib/balena-cli/build/app.js:107:9)
    at async run (/usr/local/lib/balena-cli/bin/run:20:2)

```

---

<div class="post-metadata">

**Author:** ![RodrigoM](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/rodrigom/32/5690_2.png) [@RodrigoM](https://forums.balena.io/u/RodrigoM)\
**Post date:** [May 11, 2023, 9:47pm UTC](https://forums.balena.io/t/balena-deploy-fails-without-any-details-exposed/367919/2 "2023-05-11T21:47:48Z")

</div>

It seems related to Internet connectivity. We switched to Wi-Fi and the deploy succeeded.  
Is there any configuration for timeouts etc in Balena CLI?