"socket hang up" errors between Node.js back end and third-party API

[lgrover]

I am trialing the free version of bolt.new, and am prototyping an app that uses data from the SEC XBRL API. Bolt originally used node-fetch to communicate between the Node back end the SEC API, and triggered "socket hang up" errors every time it tried to access the API. Some online sources suggested there might be an issue with node-fetch, so I asked Bolt to use Axios instead. That continues to trigger the "socket hang up" error on every API request.

The SEC API requires certain headers in the request but, reviewing the source code, it looks like the headers are correct. I suspected it might be an issue with the API refusing connections (i.e. for a blocked IP), however, I previously got 403 forbidden errors when trying to access this API from a blocked IP. Bolt looks like it is not getting any data at all.

What could be causing this issue?

[arnoldmukisa]

i'm experiencing this as well.

when running npx prisma generate

Downloading Prisma engines for Node-API for debian-openssl-1.1.x [ ] 0%Error: request to https://binaries.prisma.sh/all_commits/605197351a3c8bdd595af2d2a9bc3025bca48ea2/debian-openssl-1.1.x/libquery_engine.so.node.gz.sha256 failed, reason: socket hang up