![]() "access-control-allow-credentials": "true", ![]() Please check that the expected payload is built as per the protocol, and check the key being used. "message": "The input authorization token can't serve the request. With the generated key, I can load the included UI for managing the local emulator instance, but I then can't create Databases or Containers (without resetting the emulator and starting it again normally, eg: without the AllowNetworkAccess and related settings).Īttempting to use the included Explorer to create a Database returns. But this caused more problems with no benefit. It is all on the same (Windows) host (with the Node.js application running in Docker on the same host as the Emulator is installed). I thought perhaps I needed to enable the networking functionality. The emulator and delete the emulator's data directory To enable network access for the first time, the user should shut down KeyFile=file_name or /Key=contents_of_file. You can use /GenKeyFile=file_name to generateĪ file with a random key upfront. Specify the /AllowNetworkAccess option at the command-line, whichĪlso requires that you specify /Key=key_string or You can run the emulator on a local network. In such case, you need to enable access to the emulator on a Up the emulator on one machine and want to access it from other If you have multiple machines using a single network, and if you set Upon trying to post from the Node app to the URI provided in the Emulator Quickstart ( the error returned is.Įrror: connect ECONNREFUSED 127.0.0.1:8081 : As per these instructions.Įnable access to emulator on a local network ![]() I have a Node.js based app, and am using the Azure/cosmos-sign package to generate the correct headers via the generateHeaders method to save a JSON object in the local Cosmos Emulator. Bug, or user error? Why do the instructions for enabling networking/https not seem to work? Details: Can post to Azure Cosmos, but not with only with (which seems utterly bizare as the latter is supposedly built upon the former.) This is not ideal (as the message signing portion alone is very lightweight with REST API directly).
0 Comments
Leave a Reply. |