![]() ![]() \n at processTicksAndRejections (internal/process/task_queues. \n at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) \n at emitErrorNT (internal/streams/destroy.js:92:8) \n at TLSSocket.socketErrorListener ( http_client.js:426:9) \n at ClientRequest.emit (events.js:310:20) (C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\node_modules\node-fetch\lib\index.js:1461:11) Reason: self signed certificate in certificate chain Same issue over here when I go from the Storage account downward.įails with Blob containers, file share, queues and tables ! (C:\Users\bill.blakey\AppData\Local\Programs\Microsoft Azure Storage Explorer\resources\app\node_modules\node-fetch\lib\index.js:1461:11)\n at ClientRequest.emit (events.js:310:20)\n at TLSSocket.socketErrorListener (_http_client.js:426:9)\n at TLSSocket.emit (events.js:310:20)\n at emitErrorNT (internal/streams/destroy.js:92:8)\n at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)\n at processTicksAndRejections (internal/process/task_queues.js:84:21)", "stack": "FetchError: request to failed, reason: self signed certificate in certificate chain\n at ClientRequest. "message": "request to failed, reason: self signed certificate in certificate chain", Persisesther, did what you found and tried fix the issue? I'm getting what looks to be the same error: I should be able to view containers present within the storage account in Azure Storage Explorer, just as i can view them at Additional Context Currently, there are two supported emulators: Azure Storage Emulator (Windows only) Azurite (Windows, macOS, or Linux) If your emulator is listening on the default ports, you can use the Local
0 Comments
Leave a Reply. |