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

Cannot connect to redis://:**@redis:6379/1: Error -3 #4297

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

Originally created by @HakunamatataLeo on GitHub (Jun 27, 2024).

Self Checks

  • 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).
  • 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

image

2. Additional context or comments

Cannot connect to redis

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @HakunamatataLeo on GitHub (Jun 27, 2024). ### Self Checks - [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] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. <img width="978" alt="image" src="https://github.com/langgenius/dify/assets/4550421/aa6dea59-a003-4693-8d2f-6f3b25f23b8a"> ### 2. Additional context or comments Cannot connect to redis ### 3. Can you help us with this feature? - [X] I am interested in contributing to this feature.
yindo added the 🤔 cant-reproduce label 2026-02-21 18:05:37 -05:00
yindo closed this issue 2026-02-21 18:05:38 -05:00
yindo commented 2026-02-21 18:05:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 27, 2024):

Hello @HakunamatataLeo! 👋 I'm here to assist you with bug solving, answering questions, and even becoming a contributor. Let's work together to resolve your issue.

To resolve the issue where your Docker container "docker-worker-1" running the "langgenius/dify-api:0.6.11" image cannot connect to a Redis instance at "redis:6379" due to a "Temporary failure in name resolution," you can try the following steps:

  1. Check Docker Network Configuration: Ensure that both the docker-worker-1 container and the redis container are on the same Docker network. You can inspect the network configuration using the following command:

    docker network inspect <network_name>

    Replace <network_name> with the name of your Docker network.

  2. Add Network Alias: If the containers are on the same network, you can add a network alias for the Redis container. This can be done by modifying your docker-compose.yml file (if you are using Docker Compose) to include an alias for the Redis service:

    services:
  redis:
    image: redis:6-alpine
    networks:
      default:
        aliases:
          - redis
  worker:
    image: langgenius/dify-api:0.6.11
    depends_on:
      - redis
    networks:
      default:
networks:
  default:
    driver: bridge

  3. Update /etc/hosts: As a temporary workaround, you can manually update the /etc/hosts file inside the docker-worker-1 container to map the Redis hostname to its IP address. First, find the IP address of the Redis container:

    docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' docker-redis-1

    Then, update the /etc/hosts file inside the docker-worker-1 container:

    docker exec -it docker-worker-1 /bin/bash
echo "<redis_ip> redis" >> /etc/hosts

    Replace <redis_ip> with the IP address of the Redis container.

  4. Restart Docker Containers: Sometimes, simply restarting the Docker containers can resolve temporary network issues:

    docker-compose restart

Additionally, ensure that the Redis configuration in your docker-compose.yml file is correct. Based on the provided configuration, it should look something like this:

services:
  redis:
    image: redis:6-alpine
    restart: always
    volumes:
      - ./volumes/redis/data:/data
    command: redis-server --requirepass difyai123456
    ports:
      - "6379:6379"

  worker:
    image: langgenius/dify-api:0.6.11
    restart: always
    environment:
      REDIS_HOST: redis
      REDIS_PORT: 6379
      REDIS_PASSWORD: difyai123456
    depends_on:
      - redis
    networks:
      default:

By ensuring that the containers are on the same network and properly configured, you should be able to resolve the "Temporary failure in name resolution" error [1][2][3].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jun 27, 2024): <!-- Greeting --> Hello @HakunamatataLeo! 👋 I'm here to assist you with bug solving, answering questions, and even becoming a contributor. Let's work together to resolve your issue. <!-- Answer --> To resolve the issue where your Docker container "docker-worker-1" running the "langgenius/dify-api:0.6.11" image cannot connect to a Redis instance at "redis:6379" due to a "Temporary failure in name resolution," you can try the following steps: 1. **Check Docker Network Configuration**: Ensure that both the `docker-worker-1` container and the `redis` container are on the same Docker network. You can inspect the network configuration using the following command: ```bash docker network inspect <network_name> ``` Replace `<network_name>` with the name of your Docker network. 2. **Add Network Alias**: If the containers are on the same network, you can add a network alias for the Redis container. This can be done by modifying your `docker-compose.yml` file (if you are using Docker Compose) to include an alias for the Redis service: ```yaml services: redis: image: redis:6-alpine networks: default: aliases: - redis worker: image: langgenius/dify-api:0.6.11 depends_on: - redis networks: default: networks: default: driver: bridge ``` 3. **Update `/etc/hosts`**: As a temporary workaround, you can manually update the `/etc/hosts` file inside the `docker-worker-1` container to map the Redis hostname to its IP address. First, find the IP address of the Redis container: ```bash docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' docker-redis-1 ``` Then, update the `/etc/hosts` file inside the `docker-worker-1` container: ```bash docker exec -it docker-worker-1 /bin/bash echo "<redis_ip> redis" >> /etc/hosts ``` Replace `<redis_ip>` with the IP address of the Redis container. 4. **Restart Docker Containers**: Sometimes, simply restarting the Docker containers can resolve temporary network issues: ```bash docker-compose restart ``` Additionally, ensure that the Redis configuration in your `docker-compose.yml` file is correct. Based on the provided configuration, it should look something like this: ```yaml services: redis: image: redis:6-alpine restart: always volumes: - ./volumes/redis/data:/data command: redis-server --requirepass difyai123456 ports: - "6379:6379" worker: image: langgenius/dify-api:0.6.11 restart: always environment: REDIS_HOST: redis REDIS_PORT: 6379 REDIS_PASSWORD: difyai123456 depends_on: - redis networks: default: ``` By ensuring that the containers are on the same network and properly configured, you should be able to resolve the "Temporary failure in name resolution" error <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/learn-more/use-cases/practical-implementation-of-building-llm-applications-using-a-full-set-of-open-source-tools.md)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup><sup>[[3]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.middleware.yaml)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:05:38 -05:00
Author
Owner
Copy Link
Copy Source

@HakunamatataLeo commented on GitHub (Jun 28, 2024):

image is doesn't work ,i'm config this @dosubot
@HakunamatataLeo commented on GitHub (Jun 28, 2024): <img width="372" alt="image" src="https://github.com/langgenius/dify/assets/4550421/091d3f3f-df08-4771-9e99-33ed293fbc45"> is doesn't work ,i'm config this @dosubot
yindo commented 2026-02-21 18:05:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 28, 2024):

If the provided configuration doesn't resolve the issue, here are additional steps you can take:

  1. Ensure DNS Configuration in Docker: Modify Docker's DNS settings to use reliable DNS servers. Edit the Docker daemon configuration file (/etc/docker/daemon.json) to specify DNS servers:

    {
  "dns": ["8.8.8.8", "8.8.4.4"]
}

    Restart the Docker daemon afterward:

    sudo systemctl restart docker

  2. Specify DNS in Docker Compose: Add a dns section under your services in the docker-compose.yml file to use specific DNS servers:

    services:
  worker:
    image: langgenius/dify-api:0.6.11
    dns:
      - 8.8.8.8
      - 8.8.4.4
    networks:
      - ssrf_proxy_network
      - default

  3. Check Network Configuration: Ensure Docker containers are not in a network mode that isolates them from external access. Verify the network settings and ensure they are correctly configured.

  4. Restart Containers: Apply changes by restarting your Docker containers:

    docker-compose down
docker-compose up -d

  5. Test DNS Resolution: Verify DNS settings by executing ping google.com or nslookup google.com within a container:

    docker exec -it docker-worker-1 /bin/bash
ping google.com

These steps should help resolve the "Temporary failure in name resolution" error [1][2].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jun 28, 2024): <!-- Answer --> If the provided configuration doesn't resolve the issue, here are additional steps you can take: 1. **Ensure DNS Configuration in Docker**: Modify Docker's DNS settings to use reliable DNS servers. Edit the Docker daemon configuration file (`/etc/docker/daemon.json`) to specify DNS servers: ```json { "dns": ["8.8.8.8", "8.8.4.4"] } ``` Restart the Docker daemon afterward: ```bash sudo systemctl restart docker ``` 2. **Specify DNS in Docker Compose**: Add a `dns` section under your services in the `docker-compose.yml` file to use specific DNS servers: ```yaml services: worker: image: langgenius/dify-api:0.6.11 dns: - 8.8.8.8 - 8.8.4.4 networks: - ssrf_proxy_network - default ``` 3. **Check Network Configuration**: Ensure Docker containers are not in a network mode that isolates them from external access. Verify the network settings and ensure they are correctly configured. 4. **Restart Containers**: Apply changes by restarting your Docker containers: ```bash docker-compose down docker-compose up -d ``` 5. **Test DNS Resolution**: Verify DNS settings by executing `ping google.com` or `nslookup google.com` within a container: ```bash docker exec -it docker-worker-1 /bin/bash ping google.com ``` These steps should help resolve the "Temporary failure in name resolution" error <sup>[[1]](https://github.com/langgenius/dify/issues/4773)</sup><sup>[[2]](https://github.com/langgenius/dify/issues/4423)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:05:38 -05:00
Author
Owner
Copy Link
Copy Source

@HakunamatataLeo commented on GitHub (Jun 29, 2024):

An error occurred during credentials validation: HTTPConnectionPool(host='host.docker.internal', port=11434): Max retries exceeded with url: /api/chat (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0xffff37e92740>: Failed to resolve 'host.docker.internal' ([Errno -2] Name or service not known)"))

@HakunamatataLeo commented on GitHub (Jun 29, 2024): An error occurred during credentials validation: HTTPConnectionPool(host='host.docker.internal', port=11434): Max retries exceeded with url: /api/chat (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0xffff37e92740>: Failed to resolve 'host.docker.internal' ([Errno -2] Name or service not known)"))
yindo commented 2026-02-21 18:05:38 -05:00
Author
Owner
Copy Link
Copy Source

@HakunamatataLeo commented on GitHub (Jun 29, 2024):

@dosubot

@HakunamatataLeo commented on GitHub (Jun 29, 2024): @dosubot
yindo commented 2026-02-21 18:05:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 29, 2024):

To address the NameResolutionError for host.docker.internal, follow these steps:

  1. Ensure Docker Network Configuration: Verify that the host.docker.internal hostname is correctly resolved within your Docker containers. This hostname is typically used to refer to the host machine from within Docker containers.

  2. Add host.docker.internal to /etc/hosts: Manually add the host.docker.internal entry to the /etc/hosts file inside the container. First, find the IP address of the host machine:

    ip addr show docker0

    Then, update the /etc/hosts file inside the container:

    docker exec -it docker-worker-1 /bin/bash
echo "<host_ip> host.docker.internal" >> /etc/hosts

    Replace <host_ip> with the IP address of the host machine.

  3. Use Docker's Built-in DNS: Ensure that Docker's built-in DNS is enabled and correctly configured. You can specify DNS servers in your docker-compose.yml file:

    services:
  worker:
    image: langgenius/dify-api:0.6.11
    dns:
      - 8.8.8.8
      - 8.8.4.4
    networks:
      - ssrf_proxy_network
      - default

  4. Restart Docker Daemon: Sometimes, restarting the Docker daemon can help resolve DNS issues:

    sudo systemctl restart docker

  5. Verify DNS Resolution: Test DNS resolution within the container:

    docker exec -it docker-worker-1 /bin/bash
ping host.docker.internal

These steps should help resolve the NameResolutionError for host.docker.internal [1].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jun 29, 2024): <!-- Answer --> To address the `NameResolutionError` for `host.docker.internal`, follow these steps: 1. **Ensure Docker Network Configuration**: Verify that the `host.docker.internal` hostname is correctly resolved within your Docker containers. This hostname is typically used to refer to the host machine from within Docker containers. 2. **Add `host.docker.internal` to `/etc/hosts`**: Manually add the `host.docker.internal` entry to the `/etc/hosts` file inside the container. First, find the IP address of the host machine: ```bash ip addr show docker0 ``` Then, update the `/etc/hosts` file inside the container: ```bash docker exec -it docker-worker-1 /bin/bash echo "<host_ip> host.docker.internal" >> /etc/hosts ``` Replace `<host_ip>` with the IP address of the host machine. 3. **Use Docker's Built-in DNS**: Ensure that Docker's built-in DNS is enabled and correctly configured. You can specify DNS servers in your `docker-compose.yml` file: ```yaml services: worker: image: langgenius/dify-api:0.6.11 dns: - 8.8.8.8 - 8.8.4.4 networks: - ssrf_proxy_network - default ``` 4. **Restart Docker Daemon**: Sometimes, restarting the Docker daemon can help resolve DNS issues: ```bash sudo systemctl restart docker ``` 5. **Verify DNS Resolution**: Test DNS resolution within the container: ```bash docker exec -it docker-worker-1 /bin/bash ping host.docker.internal ``` These steps should help resolve the `NameResolutionError` for `host.docker.internal` <sup>[[1]](https://github.com/langgenius/dify/issues/4423)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:05:38 -05:00
Author
Owner
Copy Link
Copy Source

@HakunamatataLeo commented on GitHub (Jun 29, 2024):

docker server how to config the ’dns‘ @dosubot

@HakunamatataLeo commented on GitHub (Jun 29, 2024): docker server how to config the ’dns‘ @dosubot
yindo commented 2026-02-21 18:05:38 -05:00
Author
Owner
Copy Link
Copy Source

@HakunamatataLeo commented on GitHub (Jun 29, 2024):

Run failed: Node LLM run failed: [ollama] Server Unavailable Error, HTTPConnectionPool(host='host.docker.internal', port=11434): Max retries exceeded with url: /api/chat (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0xffff3d9cc5e0>: Failed to resolve 'host.docker.internal' ([Errno -2] Name or service not known)"))

@HakunamatataLeo commented on GitHub (Jun 29, 2024): Run failed: Node LLM run failed: [ollama] Server Unavailable Error, HTTPConnectionPool(host='host.docker.internal', port=11434): Max retries exceeded with url: /api/chat (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0xffff3d9cc5e0>: Failed to resolve 'host.docker.internal' ([Errno -2] Name or service not known)"))
yindo commented 2026-02-21 18:05:38 -05:00
Author
Owner
Copy Link
Copy Source

@HakunamatataLeo commented on GitHub (Jun 29, 2024):

@dosubot

@HakunamatataLeo commented on GitHub (Jun 29, 2024): @dosubot
yindo commented 2026-02-21 18:05:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 29, 2024):

To configure the DNS settings for your Docker server and resolve the NameResolutionError for host.docker.internal, follow these steps:

  1. Configure DNS in Docker Daemon:
    Edit the Docker daemon configuration file (/etc/docker/daemon.json) to specify reliable DNS servers:

    {
  "dns": ["8.8.8.8", "8.8.4.4"]
}

    After making this change, restart the Docker daemon:

    sudo systemctl restart docker

  2. Add DNS Configuration in Docker Compose:
    Add a dns section under your services in the docker-compose.yml file to use specific DNS servers:

    services:
  worker:
    image: langgenius/dify-api:0.6.11
    dns:
      - 8.8.8.8
      - 8.8.4.4
    networks:
      - ssrf_proxy_network
      - default

  3. Manually Add host.docker.internal to /etc/hosts:
    If the above steps do not resolve the issue, you can manually add the host.docker.internal entry to the /etc/hosts file inside the container. First, find the IP address of the host machine:

    ip addr show docker0

    Then, update the /etc/hosts file inside the container:

    docker exec -it docker-worker-1 /bin/bash
echo "<host_ip> host.docker.internal" >> /etc/hosts

    Replace <host_ip> with the IP address of the host machine.

  4. Verify DNS Resolution:
    Test DNS resolution within the container to ensure it can resolve host.docker.internal:

    docker exec -it docker-worker-1 /bin/bash
ping host.docker.internal

These steps should help resolve the NameResolutionError for host.docker.internal and ensure proper DNS configuration for your Docker server [1][2].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jun 29, 2024): <!-- Answer --> To configure the DNS settings for your Docker server and resolve the `NameResolutionError` for `host.docker.internal`, follow these steps: 1. **Configure DNS in Docker Daemon**: Edit the Docker daemon configuration file (`/etc/docker/daemon.json`) to specify reliable DNS servers: ```json { "dns": ["8.8.8.8", "8.8.4.4"] } ``` After making this change, restart the Docker daemon: ```bash sudo systemctl restart docker ``` 2. **Add DNS Configuration in Docker Compose**: Add a `dns` section under your services in the `docker-compose.yml` file to use specific DNS servers: ```yaml services: worker: image: langgenius/dify-api:0.6.11 dns: - 8.8.8.8 - 8.8.4.4 networks: - ssrf_proxy_network - default ``` 3. **Manually Add `host.docker.internal` to `/etc/hosts`**: If the above steps do not resolve the issue, you can manually add the `host.docker.internal` entry to the `/etc/hosts` file inside the container. First, find the IP address of the host machine: ```bash ip addr show docker0 ``` Then, update the `/etc/hosts` file inside the container: ```bash docker exec -it docker-worker-1 /bin/bash echo "<host_ip> host.docker.internal" >> /etc/hosts ``` Replace `<host_ip>` with the IP address of the host machine. 4. **Verify DNS Resolution**: Test DNS resolution within the container to ensure it can resolve `host.docker.internal`: ```bash docker exec -it docker-worker-1 /bin/bash ping host.docker.internal ``` These steps should help resolve the `NameResolutionError` for `host.docker.internal` and ensure proper DNS configuration for your Docker server <sup>[[1]](https://github.com/langgenius/dify/issues/1602)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:05:39 -05:00
Author
Owner
Copy Link
Copy Source

@HakunamatataLeo commented on GitHub (Jun 29, 2024):

how to connect local ollama
@dosubot

@HakunamatataLeo commented on GitHub (Jun 29, 2024): how to connect local ollama @dosubot
yindo commented 2026-02-21 18:05:39 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 29, 2024):

To connect to your local Ollama instance from within a Docker container, follow these steps:

  1. Expose Ollama Service to the Network:
    Ensure that the Ollama service is accessible from outside the host machine by binding it to 0.0.0.0 instead of 127.0.0.1.

    For macOS:

    launchctl setenv OLLAMA_HOST "0.0.0.0"

    For Linux:

    [Service]
Environment="OLLAMA_HOST=0.0.0.0"

    For Windows:
    Set the OLLAMA_HOST environment variable to 0.0.0.0 in the system environment variables.

  2. Restart Ollama:
    After setting the environment variable, restart the Ollama service to apply the changes.

  3. Use host.docker.internal:
    Inside your Docker container, use http://host.docker.internal:11434 to connect to the Ollama service.

    Example:

    curl http://host.docker.internal:11434

By following these steps, you should be able to connect to your local Ollama instance from within a Docker container [1][2][3].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jun 29, 2024): <!-- Answer --> To connect to your local Ollama instance from within a Docker container, follow these steps: 1. **Expose Ollama Service to the Network**: Ensure that the Ollama service is accessible from outside the host machine by binding it to `0.0.0.0` instead of `127.0.0.1`. For macOS: ```bash launchctl setenv OLLAMA_HOST "0.0.0.0" ``` For Linux: ```ini [Service] Environment="OLLAMA_HOST=0.0.0.0" ``` For Windows: Set the `OLLAMA_HOST` environment variable to `0.0.0.0` in the system environment variables. 2. **Restart Ollama**: After setting the environment variable, restart the Ollama service to apply the changes. 3. **Use `host.docker.internal`**: Inside your Docker container, use `http://host.docker.internal:11434` to connect to the Ollama service. Example: ```bash curl http://host.docker.internal:11434 ``` By following these steps, you should be able to connect to your local Ollama instance from within a Docker container <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/model-configuration/ollama.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/guides/model-configuration/ollama.md)</sup><sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/jp/guides/model-configuration/ollama.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:05:39 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jun 29, 2024):

@HakunamatataLeo Please check your env variables in docker-compose.yaml. And make sure there is no other redis server running in this machine. redis://:**@redis:6379/1 this suggests there is no host information provided to redis client.

Please not not modify network bridge, if you want to disable the proxy, please see this link https://github.com/langgenius/dify/issues/5686#issuecomment-2198395207

Run failed: Node LLM run failed: [ollama] Server Unavailable Error, HTTPConnectionPool(host='host.docker.internal', port=11434): Max retries exceeded with url: /api/chat (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0xffff3d9cc5e0>: Failed to resolve 'host.docker.internal' ([Errno -2] Name or service not known)"))

For bug report, please use bug template to report an issue. This is a feature request template. Thanks :)

@crazywoola commented on GitHub (Jun 29, 2024): @HakunamatataLeo Please check your env variables in `docker-compose.yaml`. And make sure there is no other redis server running in this machine. `redis://:**@redis:6379/1` this suggests there is no host information provided to redis client. Please not not modify network bridge, if you want to disable the proxy, please see this link https://github.com/langgenius/dify/issues/5686#issuecomment-2198395207 > Run failed: Node LLM run failed: [ollama] Server Unavailable Error, HTTPConnectionPool(host='host.docker.internal', port=11434): Max retries exceeded with url: /api/chat (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0xffff3d9cc5e0>: Failed to resolve 'host.docker.internal' ([Errno -2] Name or service not known)")) For bug report, please use bug template to report an issue. This is a feature request template. Thanks :)
yindo commented 2026-02-21 18:05:39 -05:00
Author
Owner
Copy Link
Copy Source

@Eugene-Zh commented on GitHub (Jul 31, 2024):

@crazywoola Hello, if there is a need to open other redis server on the server or I want to deploy two dify on one machine, how should I set or modify the redis port and other conflicting containers because they are the same? Thank you！

@Eugene-Zh commented on GitHub (Jul 31, 2024): @crazywoola Hello, if there is a need to open other redis server on the server or I want to deploy two dify on one machine, how should I set or modify the redis port and other conflicting containers because they are the same? Thank you！
yindo commented 2026-02-21 18:05:39 -05:00
Author
Owner
Copy Link
Copy Source

@lichengyang666 commented on GitHub (Nov 6, 2024):

I also encountered the problem of connecting to Redis, "Cannot connect to redis://:**@localhost:6379/1: invalid password." I started a flask service locally and then started Celery, but I got the error, and the password configuration has not changed and is difyai123456. I am very confused by this issue. Looking forward to your answer.

@lichengyang666 commented on GitHub (Nov 6, 2024): I also encountered the problem of connecting to Redis, "Cannot connect to redis://:**@localhost:6379/1: invalid password." I started a flask service locally and then started Celery, but I got the error, and the password configuration has not changed and is difyai123456. I am very confused by this issue. Looking forward to your answer.
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 🤔 cant-reproduce
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#4297
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?