Hello. Since last few days, I am getting this error in one of my NodeJS app that uploads files to S3. It works at 4 locations without issues but at one location is is giving this error at particular times of day.
Using "aws-sdk": "^2.1018.0",
error: Inaccessible host: mnv-saas-gold-db.s3.us-east-2.amazonaws.com' at port undefined'. This service may not be available in the us-east-2' region. {"label":"MnV SaaS DAS-DB-backup-restore","metadata":{"code":"UnknownEndpoint","hostname":"mnv-saas-gold-db.s3.us-east-2.amazonaws.com","originalError":{"code":"NetworkingError","errno":-4046,"hostname":"mnv-saas-gold-db.s3.us-east-2.amazonaws.com","message":"write EPROTO","region":"us-east-2","retryable":true,"syscall":"write","time":"2023-12-07T03:08:40.661Z"},"region":"us-east-2","retryable":true,"stack":"Error: Inaccessible host: mnv-saas-gold-db.s3.us-east-2.amazonaws.com' at port undefined'. This service may not be available in the us-east-2' region.\n at Request.ENOTFOUND_ERROR (C:\MyUploader\node_modules\aws-sdk\lib\event_listeners.js:577:46)\n at Request.callListeners
(C:\MyUploader\node_modules\aws-sdk\lib\sequential_executor.js:106:20)\n at Request.emit
(C:\MyUploader\node_modules\aws-sdk\lib\sequential_executor.js:78:10)\n at Request.emit
(C:\MyUploader\node_modules\aws-sdk\lib\request.js:686:14)\n at error
(C:\MyUploader\node_modules\aws-sdk\lib\event_listeners.js:409:22)\n at ClientRequest.<anonymous>
(C:\MyUploader\node_modules\aws-sdk\lib\http\node.js:99:9)\n at ClientRequest.emit (events.js:315:20)\n at ClientRequest.EventEmitter.emit (domain.js:486:12)\n at TLSSocket.socketErrorListener (_http_client.js:469:9)\n at TLSSocket.emit (events.js:315:20)\n at TLSSocket.EventEmitter.emit (domain.js:486:12)\n at emitErrorNT (internal/streams/destroy.js:106:8)\n at emitErrorCloseNT (internal/streams/destroy.js:74:3)\n at processTicksAndRejections (internal/process/task_queues.js:80:21)","time":"2023-12-07T03:08:40.661Z"},"timestamp":"2023-12-06 20:08:40"}
Output of ping and trace is:
C:\Windows\system32>ping mnv-saas-gold-db.s3.us-east-2.amazonaws.com
Pinging s3-r-w.us-east-2.amazonaws.com [3.5.131.158] with 32 bytes of data:
Reply from 3.5.131.158: bytes=32 time=53ms TTL=56
Reply from 3.5.131.158: bytes=32 time=54ms TTL=56
Reply from 3.5.131.158: bytes=32 time=51ms TTL=56
Reply from 3.5.131.158: bytes=32 time=51ms TTL=56
Ping statistics for 3.5.131.158:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 54ms, Average = 52ms
C:\Windows\system32>tracert mnv-saas-gold-db.s3.us-east-2.amazonaws.com
Tracing route to s3-r-w.us-east-2.amazonaws.com [52.219.84.176]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 12 ms 12 ms 68.149.160.1
3 * 12 ms 15 ms rc2we-be136-1.ed.shawcable.net [64.59.185.53]
4 14 ms 14 ms 13 ms 24.244.59.133
5 13 ms 13 ms 15 ms 24.244.59.253
6 14 ms 19 ms 13 ms rc2we-be212.ed.shawcable.net [24.244.58.85]
7 15 ms 12 ms 14 ms rc2ar-be7.ed.shawcable.net [66.163.70.130]
8 31 ms 36 ms 31 ms rc3sc-be1.wp.shawcable.net [66.163.70.77]
9 45 ms 43 ms 43 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134]
10 45 ms 42 ms 42 ms 99.82.178.252
11 50 ms 47 ms 54 ms 52.93.249.105
12 48 ms 44 ms 43 ms 52.95.62.61
13 * * * Request timed out.
14 53 ms 54 ms 61 ms 108.166.252.11
15 51 ms 53 ms 53 ms 108.166.248.33
16 52 ms 53 ms 59 ms 108.166.248.53
17 52 ms 51 ms 55 ms 108.166.248.53
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 53 ms 54 ms 52 ms s3-r-w.us-east-2.amazonaws.com [52.219.84.176]
Trace complete.
C:\Windows\system32>
