Your socket connection to the server was not read from or written to within the timeout period.

[mikexavier]

I'm encountering an issue with AssetFiles sst:aws:BucketFiles in both an Astro and Next.js site. One project has both in a monorepo and I just set up a fresh Astro site today, and ran into the same issue.

Error Frontend sst:aws:Astro → FrontendAssetFiles sst:aws:BucketFiles Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.

Temporary workaround

If I run sst remove, delete the .sst directory, then redeploy, it rarely works. Otherwise, I need to manually delete everything, including SSM parameters, and start again. The first fresh deploy works, subsequent deployments result in the same error.

Troubleshooting Attempts

• sst refresh sst refresh sst refresh too many sst refresh's
• Yup, turned it off and on.
• Checked for large files being uploaded (one site has a few images, max 140kb; the other totals around 1.5mb of images).
• Tried a different network.
• Checked for proxies or dropped connection issues.

Additional Info.

When I hunt around the interwebs, I can find some references to

s3 putObject

The error you have received indicates that S3 never received your request or it's related data, this eventually resulted in S3 timing out the connection due to idleness.

This can occur in instances where network connectivity is impacted by one or more following:

- Poor Network Connectivity
- Misconfigured Routers/Gateways
- Misconfigured Firewall/Proxy or Transparent Proxy
- Usage of Deep Packet Inspection (such as those which re-write HTTP headers) found some Firewalls
- Operating System that has either misconfigured network configuration or is not capable of dynamic MTU adjustments
- There may be other network or system related issues which could additionally also cause similar behavior.

---

I've tried to run through these checks, and can't find anything obvious... but could also be looking in the wrong places.

"brandymarsh" on discord seemed to be having a similar issue under different conditions

I'm not even sure where to start troubleshooting this. Let me know what you need from me that might help!

[jayair]

Can you share some steps to reproduce this?

Edit: Related, is this on dev or deploy?