2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
This has to do with the underlying OS configuration. The error message comes from the OS, and is only passed to Node.js. Perhaps the file descriptor limit is reached, by some other tenant?
con risposta 2 mesi fa
-1
This is more of a Node.js issue than an AWS-specific issue.
If you look at your error message, you'll see node:dns
. This means it's probably a DNS issue. Node is having trouble resolving the domain name. I've seen these errors before, and they can frequently be resolved by adjusting how to call the function. I suggest trying to call in the string format where you have built the URL:
const req = https.request('https://myUrl.co.il/login', function(res) { // ... });
If you need to provide additional options, you can insert the options object between the URL and function.
con risposta un anno fa
Contenuto pertinente
- Come posso risolvere gli errori dei codici di stato HTTP 502 e HTTP 500 (lato server) di AWS Lambda?AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
@Jason Butz Thanks! I tried that but it didnt solved the issue. Also , maybe node having trouble resolving domain name but it hard to me to understand why it can solve it in my local development but failed in aws lambda. Do you have more suggestions? (based on your answere i found temp solution with using ip instead domain name , but also i must add rejectunauthorized , somthing i tried to avoid)