curl: socket hang up with http requests

[psinger]

I am running bolt.new locally, and I try to access a different API hosted locally.

But I always end up getting socket hang up error. When accessing external apis it seems to sometimes work, but only with https.
I tried locally to allow all origins on the hosted api, but that did not change anything.
Actually also locally with https failed with the socket error.

But maybe to simplify my question: How to access another localhost service running on the same host?

Any idea how to solve this?

[Nemikolh]

Hey @psinger!

So WebContainer resolves localhost to services running inside of it, which makes reaching services exposed on localhost of your host a bit harder. It's actually a security feature: it's part of the sandboxing like you'd have with a tool like docker.

We have added a fallback on StackBlitz itself (which is an action the user must opt-in to) but it's not available on the WebContainer API, which bolt uses under the hood.

However, you could get it to work if:

• You don't refer to localhost inside WebContainer, so you do something like:

curl http://foobar:1234

• You have configured foobar to resolve to 127.0.0.1 in your /etc/hosts or equivalent
• Your service has Access-Control-Allow-Origin to * (or you return WebContainer's origin but this is unique and needs some extra logic)

[psinger]

Thanks @Nemikolh - so to confirm the steps:

1. On my host machine I map foobar to 127.0.0.1, via /etc/hosts
2. Then in bolt.new websocket environment I try to access it
3. I tried just doing curl in the console there via curl http://foobar:1234 - but I still get socket hangup error, without more details

[samdenty]

you can also use http://foo.localhost:3000 instead of setting up a etc/hosts

[psinger]

@samdenty ah that might actually work, thanks - will report back

[psinger]

Seems like GET requests work with this approach, but POST requests get stuck and have this socket error again.