sst: SST DEV results in :443 connection refused (2)

Having issues with lambda invocations. Running sst/examples/aws-lambda-stream out the box. Resources are created without error, but upon invoking, lambda logs give:

2024/12/08 01:18:28 INFO waiting for interrupt signal
2024/12/08 01:18:28 ERROR run failed err="dial tcp :443: connect: connection refused"
INIT_REPORT Init Duration: 99.38 ms	Phase: invoke	Status: error	Error Type: Runtime.ExitError

This was closed in https://github.com/sst/sst/issues/5184

sst version: 3.3.59

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 8
  • Comments: 17 (3 by maintainers)

Most upvoted comments

this should be fixed

Hmm we might need some logs for this. @thdxr

@ngocmanh1712 or anybody else still having an issue with the latest sst?

I still have having “sst dev is not running” issue with latest 3.4.16

Lambda logs image

when call api, it returns this image

@jayair Ok, just tried SST v3.4.3. I had previously tried a few 3.2.x and 3.3.x build without success.

Keeping it simple, trying a fresh /examples/aws-lambda-stream -> npm install -> npx sst dev.

I noticed the initial deployment took a good bit longer (deleting and starting worker from logs). Deployed fine, hit the url. Got a couple “sst dev is not running” responses. Looked at lambda deployment and noted this time the env vars SST_APPSYNC_HTTP and SST_APPSYNC_REALTIME are actually populated now. Saw 200’s in lambda logs so invoked the url again and got the expected response.

So, tldr, seems good! Probably fixed from some of the “dev: improve sst dev not connected scnearios” patches. Thanks.

downgrading to 3.2.76 works again

I’ve tried downgrading to other 3.2.X versions and still facing same issue.

downgrading to 3.2.76 works again