Cannot run agent node returns weird 404 Error

[backrunner]

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1. Create a Chatflow
2. Add agent node
3. Connect the agent node with input and output
4. Run it

✔️ Expected Behavior

No errors

❌ Actual Behavior

Run failed: Failed to transform agent message: PluginInvokeError: {"args":{},"error_type":"Exception","message":"invoke llm model failed: request failed with status code: 404 and respond with: {"code": "not_found", "message": "The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.", "status": 404}\n"}

[backrunner]

I just upgraded my Dify from v0.15.3 to v1.0.0, and the agent strategy tool has been reinstalled, there was nothing changed, still got this 404 error.

[dosubot]

Hey @backrunner! I'm here to help you with any bugs, questions, or contributions you have for Dify. I'll do my best to assist you while we wait for a human maintainer. Let's squash those bugs together! 🤖

The 404 error you're encountering when running an agent node in Dify version 1.0.0 is likely because this version has not been officially released yet. The system works normally when rolled back to version v0.15.3. It is recommended to continue using the stable version 0.15.3 until version 1.0.0 is officially released ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[backrunner]

Tried reinstalling the model plugin, or reinstalling the agent strategy, or restart the whole docker stack, none of them worked.
There's no error log in the outputs of api container or plugin-daemon container, could not locate which request triggered the 404 error.
The normal chat node works as expectation, only the agent node will trigger the error.

[tcodehuber]

I was also confused by this issue.

[AreChen]

一样出错

[James-Dao]

I've seen many people encounter this issue, so it feels like it might be a problem with the product itself.

[James-Dao]

I also encountered the same problem, both the Azure's OpenAI's GPT-4o and GPT-4 have issues.

[AreChen]

I solved it. My problem was due to missing envparameters in the langgenius/dify-api & langgenius/dify-plugin-daemon section.

langgenius/dify-api
43ab7c2

      PLUGIN_REMOTE_INSTALL_HOST: ${EXPOSE_PLUGIN_DEBUGGING_HOST:-localhost}
      PLUGIN_REMOTE_INSTALL_PORT: ${EXPOSE_PLUGIN_DEBUGGING_PORT:-5003}

langgenius/dify-plugin-daemon
#14850 (comment)

    depends_on:
      - db

[backrunner]

I solved it. My problem was due to missing envparameters in the langgenius/dify-api & langgenius/dify-plugin-daemon section.

langgenius/dify-api 43ab7c2

      PLUGIN_REMOTE_INSTALL_HOST: ${EXPOSE_PLUGIN_DEBUGGING_HOST:-localhost}
      PLUGIN_REMOTE_INSTALL_PORT: ${EXPOSE_PLUGIN_DEBUGGING_PORT:-5003}

langgenius/dify-plugin-daemon #14850 (comment)

    depends_on:
      - db

I tried this solution with setting EXPOSE_PLUGIN_DEBUGGING_HOST to localhost, plugin_daemon or my host domain, none of the values worked, still got the 404 error. Also tried reinstalling the agent strategy plugin after tweaked the env params.
Other plugins work right, only the agent node cannot run normally, which is really weird.

[backrunner]

Talked with the developer, here's a solution:

DO NOT EDIT PLUGIN_DIFY_INNER_API_KEY in the .env.
Just recover it to the default value in .env.example

PLUGIN_DIFY_INNER_API_KEY=QaHbTe77CtuXmsfyhR7+vRjI/+XbV1AaFy691iy+kGDv2Jvy0/eAh8Y1