Balena push not working

Product support balenaOS
, ,
1

I’m doing a balena push from the CLI which was working for me last week, but this week I’ve been hitting this error:

| Uploading source package to https://builder.balena-cloud.com[debug] received HTTP 200 OK
[debug] handling message: {“type”:“metadata”,“resource”:“buildLogId”,“value”:“3666978”}
ECONNRESET: The server aborted pending request

ReadError: The server aborted pending request
at IncomingMessage. (/usr/local/lib/balena-cli/node_modules/got/dist/source/core/index.js:809:31)
at Object.onceWrapper (node:events:632:28)
at IncomingMessage.emit (node:events:530:35)
at origin.emit (/usr/local/lib/balena-cli/node_modules/@szmarczak/http-timer/dist/source/index.js:43:20)
at IncomingMessage._destroy (node:_http_incoming:221:10)
at _destroy (node:internal/streams/destroy:122:10)
at IncomingMessage.destroy (node:internal/streams/destroy:84:5)
at TLSSocket.socketCloseListener (node:_http_client:478:11)
at TLSSocket.emit (node:events:530:35)
at node:net:346:12
at TCP.done (node:_tls_wrap:650:7)

For further help or support, visit:
balena CLI Documentation | balena

I’ve updated my balena CLI and still the same issue. It seems similar to this issue (from 6 years ago):

Is there any advice or help anyone can provide for this?

Problem building - read ECONNRESET
2

The command I’ve been trying to run to update my fleet looks like this:

balena push erlam/my-fleet --multi-dockerignore --debug --nocache

It just seems to get hung up on the builder. The status page doesn’t show any outages at the time that i’m running these too.

3

Hi @erlam,

We opened Incident: Builder partially degraded service. It’s current status is Monitoring: A fix has been implemented and we are monitoring the results. So it is not fully resolved. But it would be helpful to know - are you still experiencing the issue?

4

Hi @rosswesleyporter

Yes, I’m still experiencing this issue.

Screenshot 2025-09-17 at 10.59.14 AM
Screenshot 2025-09-17 at 10.59.14 AM1608×566 82.7 KB

Here’s my balena cli version too: balena --version = 22.3.4

Is there anything else I can do?

5

This happens for two reasons:

  1. Bad indentation in docker-compose.yml → the CLI reads it but fails to parse.

  2. Not being in the correct folder → it can’t find the project and throws a connection or context error.

6

Hi @erlam, thank you for the report. The incident above is being actively monitored and worked on. If this is indeed the the cause in your case, then the best thing to do is monitor the incident. Note that you can subscribe to email notifications there.