# Balena push not working **URL:** \ **Category:** balenaOS\ **Tags:** support, docker, network\ **Created:** [September 15, 2025, 10:38pm UTC](https://forums.balena.io/t/balena-push-not-working/374804 "2025-09-15T22:38:35Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![erlam](https://avatars.discourse-cdn.com/v4/letter/e/b9bd4f/32.png) [@erlam](https://forums.balena.io/u/erlam)\ **Post date:** [September 15, 2025, 10:38pm UTC](https://forums.balena.io/t/balena-push-not-working/374804/1 "2025-09-15T22:38:35Z")
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](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](https://www.balena.io/docs/reference/balena-cli/#support-faq-and-troubleshooting) I’ve updated my balena CLI and still the same issue. It seems similar to this issue (from 6 years ago): > [@Problem building - read ECONNRESET](https://forums.balena.io/t/problem-building-read-econnreset/24087/31): > > The build gets stuck installing npm libraries, and suddenly breaks. (This only happens when using “balena-emulated”)@BryanMontes, this could be an incompatibility with QEMU: i.e., your builds fail with emulation and require native ARM hardware. The build crashes when trying to get libraries from a repo and throws An error occurred: read ECONNRESET (this happens when pushing to master or balena-nocache) The ECONNRESET error was associated with a native ARM server (arm03) that has now been… Is there any advice or help anyone can provide for this? ---
**Author:** ![erlam](https://avatars.discourse-cdn.com/v4/letter/e/b9bd4f/32.png) [@erlam](https://forums.balena.io/u/erlam)\ **Post date:** [September 15, 2025, 10:44pm UTC](https://forums.balena.io/t/balena-push-not-working/374804/2 "2025-09-15T22:44:26Z")
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. ---
**Author:** ![rosswesleyporter](https://avatars.discourse-cdn.com/v4/letter/r/bc79bd/32.png) [@rosswesleyporter](https://forums.balena.io/u/rosswesleyporter)\ **Post date:** [September 16, 2025, 11:55pm UTC](https://forums.balena.io/t/balena-push-not-working/374804/3 "2025-09-16T23:55:54Z")
Hi @erlam, We opened [Incident: Builder partially degraded service](https://status.balena.io/incidents/jvfk2vgnfqbc). 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? ---
**Author:** ![erlam](https://avatars.discourse-cdn.com/v4/letter/e/b9bd4f/32.png) [@erlam](https://forums.balena.io/u/erlam)\ **Post date:** [September 17, 2025, 6:01pm UTC](https://forums.balena.io/t/balena-push-not-working/374804/4 "2025-09-17T18:01:17Z")
Hi @rosswesleyporter Yes, I’m still experiencing this issue. ![Screenshot 2025-09-17 at 10.59.14 AM](https://global.discourse-cdn.com/balena/original/2X/d/df6d380af16aeac7bf851efe7c6358290a003f9e.png) Here’s my balena cli version too: `balena --version` = 22.3.4 Is there anything else I can do? ---
**Author:** ![rojasyal](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/rojasyal/32/9712_2.png) [@rojasyal](https://forums.balena.io/u/rojasyal)\ **Post date:** [September 17, 2025, 6:47pm UTC](https://forums.balena.io/t/balena-push-not-working/374804/5 "2025-09-17T18:47:07Z")
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. ---
**Author:** ![rosswesleyporter](https://avatars.discourse-cdn.com/v4/letter/r/bc79bd/32.png) [@rosswesleyporter](https://forums.balena.io/u/rosswesleyporter)\ **Post date:** [September 17, 2025, 8:18pm UTC](https://forums.balena.io/t/balena-push-not-working/374804/6 "2025-09-17T20:18:20Z")
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.