langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-23 04:55:28 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Installing dify1.0 using Docker container How to use HTTP-PROXY to access Google and use Google tools #8811

New Issue
Closed
opened 2026-02-21 18:27:49 -05:00 by yindo · 16 comments
yindo commented 2026-02-21 18:27:49 -05:00
Owner
Copy Link
Copy Source

Originally created by @Twinhead880 on GitHub (Mar 1, 2025).

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Installing dify1.0 using Docker container
How to use HTTP-PROXY to access Google and use Google tools

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @Twinhead880 on GitHub (Mar 1, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Installing dify1.0 using Docker container How to use HTTP-PROXY to access Google and use Google tools ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the stale label 2026-02-21 18:27:49 -05:00
yindo closed this issue 2026-02-21 18:27:49 -05:00
yindo commented 2026-02-21 18:27:49 -05:00
Author
Owner
Copy Link
Copy Source

@Twinhead880 commented on GitHub (Mar 1, 2025):

Installing dify1.0 using Docker container
How to use HTTP-PROXY to access Google and use Google tools

@Twinhead880 commented on GitHub (Mar 1, 2025): Installing dify1.0 using Docker container How to use HTTP-PROXY to access Google and use Google tools
yindo commented 2026-02-21 18:27:49 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 1, 2025):

I found some relevant information that might help you with configuring HTTP-PROXY in Dify version 1.0 to access Google services. Although there isn't a direct solution available, there are some related discussions and issues that might provide insights:

  1. Similar Discussions:

  2. Configuration for External Services:

    • To enable access to external services like Google, you need to modify the /dify/data/ssrf_proxy/squid.conf file. Add the URLs, ports, and domains of the external services you want to access directly into this configuration file. This will whitelist the services while maintaining SSRF protection [3][4].

Unfortunately, there isn't a specific guide or template for setting up HTTP-PROXY with Docker in the Dify documentation. You might need to experiment with the configuration or check the discussions for any updates or community solutions.

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

@dosubot[bot] commented on GitHub (Mar 1, 2025): <!-- Answer --> I found some relevant information that might help you with configuring HTTP-PROXY in Dify version 1.0 to access Google services. Although there isn't a direct solution available, there are some related discussions and issues that might provide insights: 1. **Similar Discussions**: - [How to set up VPN or proxy for dify containers deployed with Docker](https://github.com/langgenius/dify/discussions/14196) discusses setting up a VPN or proxy for Dify containers, which might be relevant to your needs <sup>[[1]](https://github.com/langgenius/dify/discussions/14196)</sup>. - [how to use http proxy at tool？](https://github.com/langgenius/dify/discussions/9604) is another discussion that might provide useful information on using HTTP proxy with Dify <sup>[[2]](https://github.com/langgenius/dify/discussions/9604)</sup>. 2. **Configuration for External Services**: - To enable access to external services like Google, you need to modify the `/dify/data/ssrf_proxy/squid.conf` file. Add the URLs, ports, and domains of the external services you want to access directly into this configuration file. This will whitelist the services while maintaining SSRF protection <sup>[[3]](https://github.com/langgenius/dify/issues/13702)</sup><sup>[[4]](https://github.com/langgenius/dify/issues/12575)</sup>. Unfortunately, there isn't a specific guide or template for setting up HTTP-PROXY with Docker in the Dify documentation. You might need to experiment with the configuration or check the discussions for any updates or community solutions. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/7c759d82-2cf4-4f19-a87b-a5acb5a844b7?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/7c759d82-2cf4-4f19-a87b-a5acb5a844b7?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/7c759d82-2cf4-4f19-a87b-a5acb5a844b7?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/7c759d82-2cf4-4f19-a87b-a5acb5a844b7?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7c759d82-2cf4-4f19-a87b-a5acb5a844b7?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/7c759d82-2cf4-4f19-a87b-a5acb5a844b7?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/7c759d82-2cf4-4f19-a87b-a5acb5a844b7?feedback_type=other)</sup>
yindo commented 2026-02-21 18:27:49 -05:00
Author
Owner
Copy Link
Copy Source

@Twinhead880 commented on GitHub (Mar 1, 2025):

How to modify Squid configuration file
/dify/data/ssrf_proxy/squid.conf

How to modify Squid configuration file
Give me an example, if I want to access the following domain name
host='en.wikipedia.org', port=80

@Twinhead880 commented on GitHub (Mar 1, 2025): How to modify Squid configuration file /dify/data/ssrf_proxy/squid.conf How to modify Squid configuration file Give me an example, if I want to access the following domain name host='en.wikipedia.org', port=80
yindo commented 2026-02-21 18:27:49 -05:00
Author
Owner
Copy Link
Copy Source

@Twinhead880 commented on GitHub (Mar 1, 2025):

@dosu

@Twinhead880 commented on GitHub (Mar 1, 2025): @dosu
yindo commented 2026-02-21 18:27:49 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 1, 2025):

To modify the Squid configuration file at /dify/data/ssrf_proxy/squid.conf to access the domain 'en.wikipedia.org' on port 80, you need to add an ACL (Access Control List) entry and an allow rule for the domain. Here's an example of how you can do this:

# Add this ACL entry to define the domain
acl allowed_domains dstdomain .en.wikipedia.org

# Allow access to the domain on port 80
http_access allow allowed_domains

Add these lines to the appropriate section of your squid.conf file and restart the Squid service for the changes to take effect [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

@dosubot[bot] commented on GitHub (Mar 1, 2025): <!-- Answer --> To modify the Squid configuration file at `/dify/data/ssrf_proxy/squid.conf` to access the domain 'en.wikipedia.org' on port 80, you need to add an ACL (Access Control List) entry and an allow rule for the domain. Here's an example of how you can do this: ```plaintext # Add this ACL entry to define the domain acl allowed_domains dstdomain .en.wikipedia.org # Allow access to the domain on port 80 http_access allow allowed_domains ``` Add these lines to the appropriate section of your `squid.conf` file and restart the Squid service for the changes to take effect <sup>[[1]](https://github.com/langgenius/dify/issues/12575)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/9f0f1a95-57a3-4307-8675-5df92d8e635c?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/9f0f1a95-57a3-4307-8675-5df92d8e635c?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/9f0f1a95-57a3-4307-8675-5df92d8e635c?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/9f0f1a95-57a3-4307-8675-5df92d8e635c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9f0f1a95-57a3-4307-8675-5df92d8e635c?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/9f0f1a95-57a3-4307-8675-5df92d8e635c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9f0f1a95-57a3-4307-8675-5df92d8e635c?feedback_type=other)</sup>
yindo commented 2026-02-21 18:27:50 -05:00
Author
Owner
Copy Link
Copy Source

@Twinhead880 commented on GitHub (Mar 1, 2025):

Configured in docker-compose.yaml
HTTP_PROXY: ' http://192.168.31.114:7897 '
HTTPS_PROXY: ' http://192.168.31.114:7897 '
NO_PROXY: "localhost,127.0.0.1,.example.com,weaviate,qdrand,db,redis,web,worker,plugin_daemon"

I configured it in the configuration file/dify/data/srf_proxy/squid.conf

Add this ACL entry to define the domain

acl allowed_domains dstdomain .en.wikipedia.org

Allow access to the domain on port 80

http_access allow allowed_domains

Still reporting an error, unable to access
Failed to transform tool message: PluginInvokeError: {"args":{},"error_type":"ConnectionError","message":"HTTPConnectionPool(host='en.wikipedia.org', port=80): Max retries exceeded with url: /w/api.php?meta=siteinfo\u0026siprop=languages\u0026format=json\u0026action=query (Caused by NewConnectionError('\u003curllib3.connection.HTTPConnection object at 0x7f87d1525eb0\u003e: Failed to establish a new connection: [Errno 101] Network is unreachable'))"}

Do we need to configure it elsewhere?

@Twinhead880 commented on GitHub (Mar 1, 2025): Configured in docker-compose.yaml HTTP_PROXY: ' http://192.168.31.114:7897 ' HTTPS_PROXY: ' http://192.168.31.114:7897 ' NO_PROXY: "localhost,127.0.0.1,.example.com,weaviate,qdrand,db,redis,web,worker,plugin_daemon" I configured it in the configuration file/dify/data/srf_proxy/squid.conf # Add this ACL entry to define the domain acl allowed_domains dstdomain .en.wikipedia.org # Allow access to the domain on port 80 http_access allow allowed_domains Still reporting an error, unable to access Failed to transform tool message: PluginInvokeError: {"args":{},"error_type":"ConnectionError","message":"HTTPConnectionPool(host='en.wikipedia.org', port=80): Max retries exceeded with url: /w/api.php?meta=siteinfo\u0026siprop=languages\u0026format=json\u0026action=query (Caused by NewConnectionError('\u003curllib3.connection.HTTPConnection object at 0x7f87d1525eb0\u003e: Failed to establish a new connection: [Errno 101] Network is unreachable'))"} Do we need to configure it elsewhere?
yindo commented 2026-02-21 18:27:50 -05:00
Author
Owner
Copy Link
Copy Source

@Twinhead880 commented on GitHub (Mar 1, 2025):

@dosu

@Twinhead880 commented on GitHub (Mar 1, 2025): @dosu
yindo commented 2026-02-21 18:27:50 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 1, 2025):

To resolve the "Network is unreachable" error when trying to access 'en.wikipedia.org', ensure the following configurations are correctly set:

  1. Docker Proxy Configuration: Make sure your Docker environment is correctly set up to use the HTTP and HTTPS proxies. You should not need to manually set HTTP_PROXY and HTTPS_PROXY in the docker-compose.yaml if you're using the latest version of Dify, as it handles proxy settings automatically [1].

  2. Squid Configuration: Verify that your Squid configuration in /dify/data/ssrf_proxy/squid.conf is correctly set up. You've already added the ACL for 'en.wikipedia.org', which is correct. Ensure that the Squid service is restarted after making changes to the configuration file.

  3. Network Configuration: Check your network settings to ensure that the proxy server at http://192.168.31.114:7897 is reachable from the Docker environment. This includes verifying that the proxy server is running and accessible from the network where your Docker containers are hosted.

  4. WSL2 Configuration (if applicable): If you're using WSL2, ensure that networkingMode=mirrored and autoProxy=true are set in your .wslconfig file, and that your system proxy is correctly configured on Windows [1].

If these steps do not resolve the issue, consider checking for any firewall or network restrictions that might be blocking access to the proxy or the target domain.

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

@dosubot[bot] commented on GitHub (Mar 1, 2025): <!-- Answer --> To resolve the "Network is unreachable" error when trying to access 'en.wikipedia.org', ensure the following configurations are correctly set: 1. **Docker Proxy Configuration**: Make sure your Docker environment is correctly set up to use the HTTP and HTTPS proxies. You should not need to manually set `HTTP_PROXY` and `HTTPS_PROXY` in the `docker-compose.yaml` if you're using the latest version of Dify, as it handles proxy settings automatically <sup>[[1]](https://github.com/langgenius/dify/issues/11839)</sup>. 2. **Squid Configuration**: Verify that your Squid configuration in `/dify/data/ssrf_proxy/squid.conf` is correctly set up. You've already added the ACL for 'en.wikipedia.org', which is correct. Ensure that the Squid service is restarted after making changes to the configuration file. 3. **Network Configuration**: Check your network settings to ensure that the proxy server at `http://192.168.31.114:7897` is reachable from the Docker environment. This includes verifying that the proxy server is running and accessible from the network where your Docker containers are hosted. 4. **WSL2 Configuration (if applicable)**: If you're using WSL2, ensure that `networkingMode=mirrored` and `autoProxy=true` are set in your `.wslconfig` file, and that your system proxy is correctly configured on Windows <sup>[[1]](https://github.com/langgenius/dify/issues/11839)</sup>. If these steps do not resolve the issue, consider checking for any firewall or network restrictions that might be blocking access to the proxy or the target domain. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/a482b9f3-d278-4781-adf5-308633a21aac?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/a482b9f3-d278-4781-adf5-308633a21aac?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/a482b9f3-d278-4781-adf5-308633a21aac?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/a482b9f3-d278-4781-adf5-308633a21aac?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a482b9f3-d278-4781-adf5-308633a21aac?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/a482b9f3-d278-4781-adf5-308633a21aac?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a482b9f3-d278-4781-adf5-308633a21aac?feedback_type=other)</sup>
yindo commented 2026-02-21 18:27:50 -05:00
Author
Owner
Copy Link
Copy Source

@Twinhead880 commented on GitHub (Mar 1, 2025):

How to restart Squid service?
@dosu

@Twinhead880 commented on GitHub (Mar 1, 2025): How to restart Squid service? @dosu
yindo commented 2026-02-21 18:27:50 -05:00
Author
Owner
Copy Link
Copy Source

@Twinhead880 commented on GitHub (Mar 1, 2025):

@dosu

@Twinhead880 commented on GitHub (Mar 1, 2025): @dosu
yindo commented 2026-02-21 18:27:50 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 1, 2025):

To restart the Squid service within your Docker setup, you can follow these steps:

  1. Access the Docker Container: First, you need to access the container running Squid. You can do this by executing:

    docker exec -it <container_name_or_id> /bin/bash

    Replace <container_name_or_id> with the actual name or ID of your Squid container.

  2. Restart Squid: Once inside the container, restart the Squid service by running:

    squid -k reconfigure

    This command reloads the Squid configuration without stopping the service.

  3. Exit the Container: After restarting Squid, you can exit the container by typing exit.

If you encounter any issues, ensure that the container is running and that you have the necessary permissions to execute these commands.

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

@dosubot[bot] commented on GitHub (Mar 1, 2025): <!-- Answer --> To restart the Squid service within your Docker setup, you can follow these steps: 1. **Access the Docker Container**: First, you need to access the container running Squid. You can do this by executing: ```bash docker exec -it <container_name_or_id> /bin/bash ``` Replace `<container_name_or_id>` with the actual name or ID of your Squid container. 2. **Restart Squid**: Once inside the container, restart the Squid service by running: ```bash squid -k reconfigure ``` This command reloads the Squid configuration without stopping the service. 3. **Exit the Container**: After restarting Squid, you can exit the container by typing `exit`. If you encounter any issues, ensure that the container is running and that you have the necessary permissions to execute these commands. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/4fb0d2cc-0c7a-40ea-8a72-6cd48f72319f?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/4fb0d2cc-0c7a-40ea-8a72-6cd48f72319f?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/4fb0d2cc-0c7a-40ea-8a72-6cd48f72319f?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/4fb0d2cc-0c7a-40ea-8a72-6cd48f72319f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4fb0d2cc-0c7a-40ea-8a72-6cd48f72319f?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/4fb0d2cc-0c7a-40ea-8a72-6cd48f72319f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4fb0d2cc-0c7a-40ea-8a72-6cd48f72319f?feedback_type=other)</sup>
yindo commented 2026-02-21 18:27:50 -05:00
Author
Owner
Copy Link
Copy Source

@Twinhead880 commented on GitHub (Mar 1, 2025):

Still reporting an error! Unable to use Google tools

Failed to transform tool message: PluginInvokeError: {"args":{},"error_type":"ConnectionError","message":"HTTPConnectionPool(host='en.wikipedia.org', port=80): Max retries exceeded with url: /w/api.php?meta=siteinfo\u0026siprop=languages\u0026format=json\u0026action=query (Caused by NewConnectionError('\u003curllib3.connection.HTTPConnection object at 0x7f0ba1043aa0\u003e: Failed to establish a new connection: [Errno 101] Network is unreachable'))"}

@Twinhead880 commented on GitHub (Mar 1, 2025): Still reporting an error! Unable to use Google tools Failed to transform tool message: PluginInvokeError: {"args":{},"error_type":"ConnectionError","message":"HTTPConnectionPool(host='en.wikipedia.org', port=80): Max retries exceeded with url: /w/api.php?meta=siteinfo\u0026siprop=languages\u0026format=json\u0026action=query (Caused by NewConnectionError('\u003curllib3.connection.HTTPConnection object at 0x7f0ba1043aa0\u003e: Failed to establish a new connection: [Errno 101] Network is unreachable'))"}
yindo commented 2026-02-21 18:27:50 -05:00
Author
Owner
Copy Link
Copy Source

@Twinhead880 commented on GitHub (Mar 1, 2025):

@dosu

@Twinhead880 commented on GitHub (Mar 1, 2025): @dosu
yindo commented 2026-02-21 18:27:50 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 1, 2025):

To resolve the "Network is unreachable" error when using Google tools with the HTTP-PROXY configuration in Dify 1.0, you should enable the configuration for unregistered ports in the squid.conf.template file. Specifically, uncomment the line:

# acl SSL_ports port 1025-65535   # Enable the configuration to resolve this issue: https://github.com/langgenius/dify/issues/12792

By uncommenting this line, you allow the use of unregistered ports, which may be necessary for the Google tools to function correctly through the proxy [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

@dosubot[bot] commented on GitHub (Mar 1, 2025): <!-- Answer --> To resolve the "Network is unreachable" error when using Google tools with the HTTP-PROXY configuration in Dify 1.0, you should enable the configuration for unregistered ports in the `squid.conf.template` file. Specifically, uncomment the line: ```plaintext # acl SSL_ports port 1025-65535 # Enable the configuration to resolve this issue: https://github.com/langgenius/dify/issues/12792 ``` By uncommenting this line, you allow the use of unregistered ports, which may be necessary for the Google tools to function correctly through the proxy <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker/ssrf_proxy/squid.conf.template)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/21b48d0a-7488-495b-b3d3-02e1da1c4da8?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/21b48d0a-7488-495b-b3d3-02e1da1c4da8?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/21b48d0a-7488-495b-b3d3-02e1da1c4da8?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/21b48d0a-7488-495b-b3d3-02e1da1c4da8?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/21b48d0a-7488-495b-b3d3-02e1da1c4da8?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/21b48d0a-7488-495b-b3d3-02e1da1c4da8?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/21b48d0a-7488-495b-b3d3-02e1da1c4da8?feedback_type=other)</sup>
yindo commented 2026-02-21 18:27:50 -05:00
Author
Owner
Copy Link
Copy Source

@Twinhead880 commented on GitHub (Mar 1, 2025):

I have modified the Squid configuration file and removed the comments

acl SSL_ports port 1025-65535 # Enable the configuration to resolve this issue: https://github.com/langgenius/dify/issues/12792

But the effect hasn't changed, it still reports an error

Failed to transform tool message: PluginInvokeError: {"args":{},"error_type":"ConnectionError","message":"HTTPConnectionPool(host='en.wikipedia.org', port=80): Max retries exceeded with url: /w/api.php?meta=siteinfo\u0026siprop=languages\u0026format=json\u0026action=query (Caused by NewConnectionError('\u003curllib3.connection.HTTPConnection object at 0x7f53710ea6c0\u003e: Failed to establish a new connection: [Errno 101] Network is unreachable'))"}

@dosu

@Twinhead880 commented on GitHub (Mar 1, 2025): I have modified the Squid configuration file and removed the comments # acl SSL_ports port 1025-65535 # Enable the configuration to resolve this issue: https://github.com/langgenius/dify/issues/12792 But the effect hasn't changed, it still reports an error Failed to transform tool message: PluginInvokeError: {"args":{},"error_type":"ConnectionError","message":"HTTPConnectionPool(host='en.wikipedia.org', port=80): Max retries exceeded with url: /w/api.php?meta=siteinfo\u0026siprop=languages\u0026format=json\u0026action=query (Caused by NewConnectionError('\u003curllib3.connection.HTTPConnection object at 0x7f53710ea6c0\u003e: Failed to establish a new connection: [Errno 101] Network is unreachable'))"} @dosu
yindo commented 2026-02-21 18:27:50 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 1, 2025):

To address the "Network is unreachable" error, consider the following steps:

  1. Verify Network Connectivity: Ensure that your Docker environment has proper network access. Check if the proxy server (http://192.168.31.114:7897) is reachable from within the Docker container. You can test this by executing a simple network command like ping or curl from within the container to the proxy server.

  2. Check Proxy Server Status: Make sure the proxy server is running and accessible. Verify that there are no firewall rules or network policies blocking access to the proxy server or the target domain.

  3. Review Docker Network Settings: Ensure that the Docker network settings are correctly configured. If you're using a custom Docker network, verify that it allows outbound connections.

  4. Inspect Squid Logs: Check the Squid logs for any errors or warnings that might provide more insight into the connection issues. The logs can help identify if the requests are reaching the Squid proxy and if there are any specific errors being logged.

  5. Test Direct Connection: As a troubleshooting step, try accessing the target domain directly from the host machine (outside of Docker) to ensure there are no broader network issues.

If these steps do not resolve the issue, consider reviewing any recent changes to your network or proxy configuration that might have affected connectivity.

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

@dosubot[bot] commented on GitHub (Mar 1, 2025): <!-- Answer --> To address the "Network is unreachable" error, consider the following steps: 1. **Verify Network Connectivity**: Ensure that your Docker environment has proper network access. Check if the proxy server (`http://192.168.31.114:7897`) is reachable from within the Docker container. You can test this by executing a simple network command like `ping` or `curl` from within the container to the proxy server. 2. **Check Proxy Server Status**: Make sure the proxy server is running and accessible. Verify that there are no firewall rules or network policies blocking access to the proxy server or the target domain. 3. **Review Docker Network Settings**: Ensure that the Docker network settings are correctly configured. If you're using a custom Docker network, verify that it allows outbound connections. 4. **Inspect Squid Logs**: Check the Squid logs for any errors or warnings that might provide more insight into the connection issues. The logs can help identify if the requests are reaching the Squid proxy and if there are any specific errors being logged. 5. **Test Direct Connection**: As a troubleshooting step, try accessing the target domain directly from the host machine (outside of Docker) to ensure there are no broader network issues. If these steps do not resolve the issue, consider reviewing any recent changes to your network or proxy configuration that might have affected connectivity. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/81f45ab6-3e3a-47cd-952e-b81434132478?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/81f45ab6-3e3a-47cd-952e-b81434132478?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/81f45ab6-3e3a-47cd-952e-b81434132478?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/81f45ab6-3e3a-47cd-952e-b81434132478?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/81f45ab6-3e3a-47cd-952e-b81434132478?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/81f45ab6-3e3a-47cd-952e-b81434132478?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/81f45ab6-3e3a-47cd-952e-b81434132478?feedback_type=other)</sup>
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#8811
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?