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.<anonymous> (/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)
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.
@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.