-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: connect EAFNOSUPPORT ::1:80 #561
Comments
Hmm. I don't know much about AWS Lambda, but I do know we have quite a few customers using it and I've never heard of any compatibility issues between Plaid and AWS Lambda or of anyone encountering that error code (I searched our entire Zendesk -- the error EAFNOSUPPORT doesn't seem to appear in any support ticket we've ever received). As a result, I'm guessing this could potentially be an issue with the AWS Lambda configuration? I'm not sure if this will help at all, but https://github.com/aws-samples/aws-plaid-demo-app is an example of a demo app that uses AWS Lambda with the Python client library. |
|
Thanks @phoenixy1, this is a good lead. Circling back on this today to see if the config needs to be tweaked. Thanks for the sanity check - will follow-up. |
This was due to an invalid/malformed Would this project consider tighter type defs for |
Has anyone had any luck using this in AWS Lambda? Per the title, I'm assuming the endpoints are IPv6 which Lambda does not support for outbound calls.
Any tricks? Or am I interpretting that Axios error wrong?
What I've tried: modify
createRequestFunction
in common.ts to force IPv4 in hopes that the Plaid API network interface support both. No dice. I'm using this for alinkTokenCreate
request.The text was updated successfully, but these errors were encountered: