# 408 Request Timeout when doing balena push **URL:** \ **Category:** Product support\ **Created:** [January 11, 2025, 12:41pm UTC](https://forums.balena.io/t/408-request-timeout-when-doing-balena-push/372786 "2025-01-11T12:41:09Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![BrianPTL](https://avatars.discourse-cdn.com/v4/letter/b/a587f6/32.png) [@BrianPTL](https://forums.balena.io/u/BrianPTL)\ **Post date:** [January 11, 2025, 12:41pm UTC](https://forums.balena.io/t/408-request-timeout-when-doing-balena-push/372786/1 "2025-01-11T12:41:09Z")
Hi, I am constantly getting errors today when trying `balena push`. It happened 80% of the time yesterday and 100% of the time today: ```bash Remote builder responded with HTTP error: 408 Request Timeout ``` Balena Status shows “All Systems Operational”: [https://status.balena.io/](https://status.balena.io/) Is there something wrong on my side? ---
**Author:** ![BrianPTL](https://avatars.discourse-cdn.com/v4/letter/b/a587f6/32.png) [@BrianPTL](https://forums.balena.io/u/BrianPTL)\ **Post date:** [January 11, 2025, 1:22pm UTC](https://forums.balena.io/t/408-request-timeout-when-doing-balena-push/372786/2 "2025-01-11T13:22:23Z")
Debug output (username and fleet name redacted): ```bash Packaging the project source...[Debug] Tarring complete in 1370 ms [debug] Connecting to builder at https://builder.balena-cloud.com/v3/build?slug=our_username%2Four_fleet&dockerfilePath=&emulated=false&nocache=false&headless=false&isdraft=false Remote builder responded with HTTP error: 408 Request Timeout ExpectedError: Remote builder responded with HTTP error: 408 Request Timeout at Request. (/snapshot/balena-cli/build/utils/remote-build.js:250:21) at Object.onceWrapper (node:events:633:26) at Request.emit (node:events:518:28) at Request.emit (node:domain:488:12) at Request.onRequestResponse (/snapshot/balena-cli/node_modules/request/request.js:1059:10) at ClientRequest.emit (node:events:530:35) at ClientRequest.emit (node:domain:488:12) at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:693:27) at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17) at TLSSocket.socketOnData (node:_http_client:535:22) at TLSSocket.emit (node:events:518:28) at TLSSocket.emit (node:domain:488:12) at addChunk (node:internal/streams/readable:559:12) at readableAddChunkPushByteMode (node:internal/streams/readable:510:3) at Readable.push (node:internal/streams/readable:390:5) at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23) ``` ---
**Author:** ![BrianPTL](https://avatars.discourse-cdn.com/v4/letter/b/a587f6/32.png) [@BrianPTL](https://forums.balena.io/u/BrianPTL)\ **Post date:** [January 13, 2025, 9:21am UTC](https://forums.balena.io/t/408-request-timeout-when-doing-balena-push/372786/3 "2025-01-13T09:21:18Z")
It’s working this morning. I have not changed anything on my side. I suspect there was a service down on the Balena side that was not reflected in the Balena Status page that has since been fixed. ---
**Author:** ![mpous](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/mpous/32/4742_2.png) [@mpous](https://forums.balena.io/u/mpous)\ **Post date:** [January 13, 2025, 3:06pm UTC](https://forums.balena.io/t/408-request-timeout-when-doing-balena-push/372786/4 "2025-01-13T15:06:16Z")
Hello @BrianPTL first of all welcome to the balena community! Thanks for confirming that suddently it built well today! I will ping the team and check what could happen 2 days ago! Let us know if we can help you with anything else! ---
**Author:** ![mpous](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/mpous/32/4742_2.png) [@mpous](https://forums.balena.io/u/mpous)\ **Post date:** [January 13, 2025, 3:51pm UTC](https://forums.balena.io/t/408-request-timeout-when-doing-balena-push/372786/5 "2025-01-13T15:51:26Z")
@BrianPTL do you by any chance run with debug logs via the CLI when you were having issues? We don’t see anything on our side but it could have been a regional networking issue, or something else we would need to track down with more log messages. Thanks! ---
**Author:** ![pgiotis](https://avatars.discourse-cdn.com/v4/letter/p/ebca7d/32.png) [@pgiotis](https://forums.balena.io/u/pgiotis)\ **Post date:** [February 21, 2025, 8:14am UTC](https://forums.balena.io/t/408-request-timeout-when-doing-balena-push/372786/6 "2025-02-21T08:14:10Z")
Hello I have the same issue ```auto Remote builder responded with HTTP error: 408 Request Timeout ExpectedError: Remote builder responded with HTTP error: 408 Request Timeout ``` I face this issue only if I push via a Starlink connection. With landline connection is ok. Any workaround? Thanks ---
**Author:** ![mpous](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/mpous/32/4742_2.png) [@mpous](https://forums.balena.io/u/mpous)\ **Post date:** [February 21, 2025, 11:14am UTC](https://forums.balena.io/t/408-request-timeout-when-doing-balena-push/372786/7 "2025-02-21T11:14:18Z")
Hello @pgiotis could you please confirm how are you pushing? is your connectivity through Starlink? is your release very big? Thanks ---
**Author:** ![pgiotis](https://avatars.discourse-cdn.com/v4/letter/p/ebca7d/32.png) [@pgiotis](https://forums.balena.io/u/pgiotis)\ **Post date:** [February 21, 2025, 12:37pm UTC](https://forums.balena.io/t/408-request-timeout-when-doing-balena-push/372786/8 "2025-02-21T12:37:41Z")
I am pushing with command. ```auto balena push fleet-slug ``` Yes, my connectivity is through Starlink. It seems that the .dockerignore that I have in the root folder does not work and trying to push the node\_modules. I manually delete the node\_modules and after that the push action is complete. You can see the .dockerignore below ```auto build/ node_modules/ .next ``` ---
**Author:** ![mpous](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/mpous/32/4742_2.png) [@mpous](https://forums.balena.io/u/mpous)\ **Post date:** [February 21, 2025, 6:00pm UTC](https://forums.balena.io/t/408-request-timeout-when-doing-balena-push/372786/9 "2025-02-21T18:00:17Z")
thanks for sharing that removing the node\_modules worked properly @pgiotis Let us know how we can help you more!