Error Uploading File

[charliefjohnson]

We're seeing the following error when trying upload a file:

bir-server-app_1 | Error : { FetchError: request to https://content.dropboxapi.com/2/files/upload failed, reason: getaddrinfo EAI_AGAIN content.dropboxapi.com content.dropboxapi.com:443
bir-server-app_1 | at ClientRequest.<anonymous> (/usr/src/app/node_modules/cross-fetch/node_modules/node-fetch/index.js:133:11)
bir-server-app_1 | at ClientRequest.emit (events.js:198:13)
bir-server-app_1 | at TLSSocket.socketErrorListener (_http_client.js:401:9)
bir-server-app_1 | at TLSSocket.emit (events.js:198:13)
bir-server-app_1 | at emitErrorNT (internal/streams/destroy.js:91:8)
bir-server-app_1 | at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
bir-server-app_1 | at process._tickCallback (internal/process/next_tick.js:63:19)
bir-server-app_1 | name: 'FetchError',
bir-server-app_1 | message:
bir-server-app_1 | 'request to https://content.dropboxapi.com/2/files/upload failed, reason: getaddrinfo EAI_AGAIN content.dropboxapi.com content.dropboxapi.com:443',
bir-server-app_1 | type: 'system',
bir-server-app_1 | errno: 'EAI_AGAIN',
bir-server-app_1 | code: 'EAI_AGAIN' }

Not sure where to look as to find the issue.  This just happens on a single server.  We have a similar server that is running the same app and it works just fine.

[Greg-DB]

Based on "getaddrinfo EAI_AGAIN" it looks like this is a DNS issue, so I recommend debugging the DNS setup being used by the affected server to see why it may not be able to look up the Dropbox API content server hostname. You may need to contact the administrator of your DNS server (or switch to a different one).