When invoking new order in hello-world: "errorCode": "ERR_DIRECT_INVOKE", "message": "invoke API is not ready"

[gary-desroches]

Expected Behavior

== APP == Got a new order! Order ID: 42
== APP == Successfully persisted state.

Actual Behavior

"errorCode": "ERR_DIRECT_INVOKE",
"message": "invoke API is not ready"

Steps to Reproduce the Problem

Follow the instructions on Windows 10 to install and init dapper 1.0.0 in Docker, then cloning and running the hello-world app on your local machine. Get to the point where you POST a new order with the following URL and body data.

http://localhost:3500/v1.0/invoke/nodeapp/method/neworder

{
  "data": {
    "orderId": "42"
  } 
}

[seanfitzg]

I'm getting a similar error on windows 10. I've created a .net core demo application at https://github.com/seanfitzg/HomeCookingApi.

Started with:
dapr run --app-id recipe-app --app-port 80 --dapr-http-port 3500 dotnet run

Running:
curl http://localhost:3500/v1.0/invoke/recipe-app/method/recipes

Returns:
{"errorCode":"ERR_DIRECT_INVOKE","message":"invoke API is not ready"}

I wonder if there is an issue with .net core invocation on Win10. I don't think I'm doing anything wrong.

[sjf10050]

npm install express --save
the app.js require module 'express'

[wcs1only]

So, we regularly validate our quickstarts in Windows, and I am able to run this one without issue on a Windows 10 machine. Dapr relies on mDNS for service discovery while running locally. We have received reports of users having trouble when certain security/firewall/VPN software blocks access to mDNS. Are you running any firewalls/VPN software on your machine?

Depending on the product, you may be able to re-enable mDNS for localhost connections to allow service discovery to work correctly locally.

[seanfitzg]

I'm getting a similar error on windows 10. I've created a .net core demo application at https://github.com/seanfitzg/HomeCookingApi.

Started with:
dapr run --app-id recipe-app --app-port 80 --dapr-http-port 3500 dotnet run

Running:
curl http://localhost:3500/v1.0/invoke/recipe-app/method/recipes

Returns:
{"errorCode":"ERR_DIRECT_INVOKE","message":"invoke API is not ready"}

I wonder if there is an issue with .net core invocation on Win10. I don't think I'm doing anything wrong.

fyi, this response helped to sort out my issue: dapr/dapr#2954 (comment)

[wcs1only]

Ah, glad you were able to sort this out. We've also made some changes to the way dapr run works in v1.2 that should make it a little more obvious that daprd has failed with an error.