Proxies: Worker was unable to load function: The argument 'id' must be a non-empty string.

[iyerusad]

Error message cropped up today when locally running functions:

LanguageWorkerConsoleLog[error] Worker was unable to load function letsencrypt-proxy: 'TypeError [ERR_INVALID_ARG_VALUE]: The argument 'id' must be a non-empty string. Received '''

Haven't changed proxy configs in a while - appears to be either unexpected schema change or bug/regression in Azure Functions Core Tools/Function Runtime.

Removed node_modules, bin, obj, etc and did npm i. Same result.

---

Azure Functions Core Tools: 2.7.1373 - Commit hash: cd9bfca)
Function Runtime Version: 2.0.12507.0

proxies.json (config hasn't changed in a while)

{
  "$schema": "http://json.schemastore.org/proxies",
  "proxies": {
    "letsencrypt-proxy": {
        "matchCondition": {
            "route": "/.well-known/acme-challenge/{*restOfPath}",
            "methods": ["GET"]
        },
        "backendUri": "https://localhost/api/letsencrypt/{restOfPath}"
    }
  }
}

[ahmedelnably]

@iyerusad Is this a proxy only function app, if you have other functions, what language are they using

[iyerusad]

No, it has over 10 Azure functions running on Node.

[MECLab-Keags]

Having the same issue here with javascript function on Node.

[ahmedelnably]

@pragnagopa is this a known issue?

[pragnagopa]

@mhoeger - Can you please take a look?

[harshitsanghvi]

Having the same issue, using Node.

[iyerusad]

Was getting following error today

Exceeded language worker restart retry count for runtime:node. Shutting down Functions Host
Application is shutting down...

Updated from node 10.14.1 to 10.16.1 (latest LTS) resolved this particular issue.

Proxies issue still persists.

[david0178418]

Similar issue. However, the error seems to be benign. The proxy seems to operate as expected in this simple case. Not sure if a more complex case would surface some issue:

[benc-uk]

Same problem, came out of nowhere
Also using Node

[billbliss]

Seeing the same problem today when running locally in VS Code.

Azure Functions Core Tools (2.7.1575 Commit hash: b7750e7)
Function Runtime Version: 2.0.12625.0
Node v10.15.3

Is there a workaround anyone knows about?

[billbliss]

I shut down VS Code and manually killed two instances of Node.js. There were about 20 instances of the "Runtime Broker" process running (I had been writing code and testing for several hours) and I killed all of those. I restarted VS Code and was able to debug again. If I had to guess, I'd say there's a process leakage bug.