After local deployment, generate an apikey and configure it in Dify with an error message

[cauduan]

After local deployment, generate an apikey and configure it in Dify with an error message
PluginInvokeError: {"args":{},"error_type":"ToolProviderCredentialValidationError","message":"HTTPConnectionPool(host='127.0.0.1', port=8081): Max retries exceeded with url: /api/v1/core/crawl-requests/?page=1\u0026page_size=1 (Caused by NewConnectionError('\u003curllib3.connection.HTTPConnection object at 0x7005dc5a5e20\u003e: Failed to establish a new connection: [Errno 111] Connection refused'))"}

[amirasaran]

Hey @cauduan
Thanks for contacting us and using WaterCrawl.

If you're running both Watercrawl and Dify using separate Docker Compose setups, you may encounter network isolation issues.

Why?

When you run two separate docker-compose projects, each creates its own internal Docker network. That means:

• Dify cannot access localhost or 127.0.0.1:8081 on your host from inside its own container, because those addresses refer to the container itself — not your host machine or the other containers.

---

✅ Solution Options

Option 1: Use host.docker.internal (Docker Desktop only)

If you're using Docker Desktop (on macOS, Windows, or recent Linux setups), you can configure your tool in Dify with:

http://host.docker.internal:8081

This special hostname lets containers reach the host machine’s network, including any local service (like Watercrawl) running on localhost:8081.

---

Option 2: Use your machine's IP address

If host.docker.internal doesn't work (e.g. on native Linux without Docker Desktop), you can find your local IP like this:

On Linux/macOS:

ip a | grep inet

On Windows (Command Prompt):

ipconfig

Look for something like 192.168.x.x (your LAN IP).

Then, in your Dify configuration, set the plugin/tool base URL to:

http://192.168.x.x:8081

---

Just make sure that:

• Watercrawl is bound to 0.0.0.0 instead of 127.0.0.1 so it’s accessible from outside the container.
• Your firewall or Docker settings allow connections to that port.

[cauduan]

Thank you so much. Your explanation was spot-on, and it solved the problem that had been bothering me all afternoon.