agent running error

[githubscholarls]

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.4.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1. Add https://marketplace.dify.ai/plugins/junjiem/mcp_sse? theme=system This plug-in, the authorization link is { "playwright": { "url": "http://host.docker.internal:8931/sse" } }
2. Configure npx @playwright/mcp@latest --port 8931 to link to run locally
3. Add the agent tool, select the deepseek-r1 model,

Run, enter text: Open https://xxxxx.com, wait for 5 seconds, locate the id equal to form_item_phoneNumber and enter the account number 166xxxx0391, then locate the id equal to form_item_password and enter the password labc123, then click Login, and then select Develop and Test this enterprise, wait for 2 seconds to locate the input input initiation process of type=search, and click the initiation process that pops up below, click the work summary in the process list on this new page, then locate the text input after the topic, enter the test automation text, and finally click the Submit button

✔️ Expected Behavior

No response

❌ Actual Behavior

[dosubot]

The error you're seeing is likely caused by one of these common issues in self-hosted Docker setups:

• Environment variables for plugin communication are missing or misconfigured. Double-check that PLUGIN_REMOTE_INSTALL_HOST, PLUGIN_REMOTE_INSTALL_PORT, PLUGIN_DIFY_INNER_API_KEY, and INNER_API_KEY_FOR_PLUGIN are set correctly in your Docker environment. Do not edit PLUGIN_DIFY_INNER_API_KEY—restore it to the default from .env.example if it's been changed. Reference
• Avoid using localhost or 127.0.0.1 for service endpoints inside Docker; use host.docker.internal or the correct service name instead. Reference
• A 404 or PluginInvokeError usually means the agent node can't reach the internal API endpoint for tool invocation, often due to the above misconfigurations. Reference
• DNS or firewall issues (like GFW) can block plugin communication—ensure your Docker containers can resolve and reach the plugin service. Reference

The specific DOM error (NotFoundError: Failed to execute 'removeChild' on 'Node') is likely coming from the Playwright MCP plugin or the automation script itself, not Dify core. This can happen if the script tries to interact with a DOM node that no longer exists (for example, due to page navigation or timing issues). Try simplifying your automation steps or adding waits/checks to ensure elements exist before interacting.

If you still see the error after checking the above, review the Playwright MCP logs and browser console for more details. There are no known compatibility issues between deepseek-r1 and the MCP SSE plugin, but only models supporting tool-calling (function call or ReACT) are visible in the Agent node.

Recent Dify 1.4.2 changes restored agent moderation and improved plugin extension performance, but did not introduce breaking changes for this workflow. Reference

Let me know if you need help with specific logs or configuration details.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}