A0deploy export command returns an error on one machine only

Help
,
1

Hi all,
I’ve setup a0deploy cli on two machines. 1 of the machines works perfectly but, the other returns an error when I run a simple export command:

error: The request failed and the interceptors did not return an alternative response

response
at BaseAPI.fetch (C:\Users\user\AppData\Roaming\npm\node_modules\auth0-deploy-cli\node_modules\auth0\dist\cjs\lib\runtime.js:84:27)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async OAuth.request (C:\Users\user\AppData\Roaming\npm\node_modules\auth0-deploy-cli\node_modules\auth0\dist\cjs\lib\runtime.js:115:26)
at async grant (C:\Users\user\AppData\Roaming\npm\node_modules\auth0-deploy-cli\node_modules\auth0\dist\cjs\auth\base-auth-api.js:86:22)

it’s definitely not authentication as this same command works on another machine (on another network) and config.json files are exactly the same/

now , on the machine with the error, netstat shows that the connection is time_wait and does not get established. However, using postman, I can request tokens against the same URL and as well, use API calls without an issue. I can also get to the domain on port 443.

I’m starting to think this could be TLS related and will dig further but, figured to ask the community if they have seen this before.

Or, perhaps the application is locked down to a specific IP, however, I can’t see anywhere on the console that this would be the case.

Thanks all,

Seth

3

Hi @sefrat,

Welcome to the Auth0 Community!

I found an internal case where the same error was received with the Deploy CLI. The fix came from the customer’s security/networking team. Since it couldn’t run the export command, it was blocked from running. According to their Network/Security Team: “The error was due to a networking/certificate issue.” Your TLS-related inclination looks to be correct!

Additionally, here is our Community Knowledge Solution that discusses this error: [The fix came from the customer’s security/networking team since it couldn’t run the export command, it was blocked from running.

Based on the Network/Security Team: "the issue was due to a networking/certificate issue "](Solution for Error "The Request Failed and the Interceptors did not Return an Alternative Response")

Thanks,

Mary Beth

4

Excellent find Marybeth. Much appreciated.

1 Like