Unable to deploy code to app builder. Error: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed

[Smitha-Git-Repo-Public]

Expected Behaviour :

• Deployment to App Builder must be successful without any errors.

Actual Behaviour:

• Getting the below error during deployment.

× Deploying web assets for 'application'
 »   Error: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.

Environment Info

$ aio info
 »   Warning: @adobe/aio-cli update available from 10.3.3 to 11.0.0.
 »   Run npm install -g @adobe/aio-cli to update.
  System:
    OS: Windows 11 10.0.26100
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i7-1265U
    Memory: 15.43 GB / 31.44 GB
  Binaries:
    Node: 24.0.1 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 11.3.0 - C:\Program Files\nodejs\npm.CMD
  Virtualization:
    Docker: 28.0.4 - C:\Program Files\Docker\Docker\resources\bin\docker.EXE
  npmGlobalPackages:
    @adobe/aio-cli: Not Found
  Proxies:
    http: (not set)
    https: (not set)
  CLI plugins:
    core:
      @adobe/aio-cli 10.3.3
      @adobe/aio-cli-plugin-app 13.3.0
      @adobe/aio-cli-plugin-app-dev 2.1.2
      @adobe/aio-cli-plugin-app-storage 1.1.0
      @adobe/aio-cli-plugin-app-templates 2.0.3
      @adobe/aio-cli-plugin-auth 4.0.1
      @adobe/aio-cli-plugin-certificate 2.0.1
      @adobe/aio-cli-plugin-config 5.0.1
      @adobe/aio-cli-plugin-console 5.0.1
      @adobe/aio-cli-plugin-events 4.0.1
      @adobe/aio-cli-plugin-info 4.0.1
      @adobe/aio-cli-plugin-runtime 7.1.0
      @adobe/aio-cli-plugin-telemetry 2.0.2
      @oclif/plugin-autocomplete 3.2.34
      @oclif/plugin-help 6.2.32
      @oclif/plugin-not-found 2.4.3
      @oclif/plugin-plugins 5.4.46
      @oclif/plugin-warn-if-update-available 3.1.46
    user:
      @adobe/aio-cli-plugin-aem-rde 1.3.9
      @adobe/aio-cli-plugin-asset-compute 4.1.0
      @adobe/aio-cli-plugin-cloudmanager 4.2.4

#### Sample Code that illustrates the problem

#### Logs taken while reproducing problem
$ aio app deploy --verbose
 »   Warning: [@Adobe Express](https://adobe.enterprise.slack.com/team/W8U4C0NQG)/aio-cli update available from 10.3.3 to 11.0.0.
 »   Run npm install -g [@Adobe Express](https://adobe.enterprise.slack.com/team/W8U4C0NQG)/aio-cli to update.
:information_source: Log forwarding is not updated: no configuration is provided
:heavy_check_mark: Built 9 action(s) for 'application'
:information_source: bundling C:\Sams-Club-Project\New folder\dm-to-aem-sync\web-src/**/*.html
:heavy_check_mark: Building web assets for 'application'
:information_source: Info: Deploying package [dm-to-aem-sync]...
:information_source: Info: package [dm-to-aem-sync] has been successfully deployed.
:information_source: Success: Deployment completed successfully.
:information_source: No actions deployed for 'application'
:information_source: warning: an existing deployment will be overwritten
:heavy_multiplication_x: Deploying web assets for 'application'
 »   Error: RequestTimeout: Your socket connection to the server was not read from or written to within the timeout
 »    period. Idle connections will be closed.
 »       at throwDefaultError (C:\Users\sasharathna\AppData\Roaming\npm\node_modules\@adobe\aio-cli\node_modules\@s
 »   mithy\smithy-client\dist-cjs\index.js:422:20)
 »       at C:\Users\sasharathna\AppData\Roaming\npm\node_modules\@adobe\aio-cli\node_modules\@smithy\smithy-client
 »   \dist-cjs\index.js:431:5
 »       at de_CommandError (C:\Users\sasharathna\AppData\Roaming\npm\node_modules\@adobe\aio-cli\node_modules\@aws
 »   -sdk\client-s3\dist-cjs\index.js:5202:14)
 »       at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
 »       at async C:\Users\sasharathna\AppData\Roaming\npm\node_modules\@adobe\aio-cli\node_modules\@smithy\middlew
 »   are-serde\dist-cjs\index.js:36:20
 »       at async C:\Users\sasharathna\AppData\Roaming\npm\node_modules\@adobe\aio-cli\node_modules\@aws-sdk\middle
 »   ware-sdk-s3\dist-cjs\index.js:488:18
 »       at async C:\Users\sasharathna\AppData\Roaming\npm\node_modules\@adobe\aio-cli\node_modules\@smithy\middlew
 »   are-retry\dist-cjs\index.js:312:38
 »       at async C:\Users\sasharathna\AppData\Roaming\npm\node_modules\@adobe\aio-cli\node_modules\@aws-sdk\middle
 »   ware-flexible-checksums\dist-cjs\index.js:318:18
 »       at async C:\Users\sasharathna\AppData\Roaming\npm\node_modules\@adobe\aio-cli\node_modules\@aws-sdk\middle
 »   ware-sdk-s3\dist-cjs\index.js:110:22
 »       at async C:\Users\sasharathna\AppData\Roaming\npm\node_modules\@adobe\aio-cli\node_modules\@aws-sdk\middle
 »   ware-sdk-s3\dist-cjs\index.js:137:14

[aiojbot]

JIRA issue created: https://jira.corp.adobe.com/browse/ACNA-4048

[shazron]

This issue outlines the cause: aws/aws-sdk-js-v3#6805 and the fix is to update a third party dependency to v4 in aio-lib-web "@smithy/node-http-handler": "^4.0.2"

It is a network latency issue during a handshake.

I've tested the fix on the internal VPNs with aio app deploy and the fix works.

However, we can't release this fix without re-testing the proxy fixes from aio-lib-web@7.0.5.
When the fix is released (v7.0.6), to get the fix you will just reinstall the aio-cli.

[shazron]

PR adobe/aio-lib-web#226