ragflow icon indicating copy to clipboard operation
ragflow copied to clipboard

[Question]: Fail to access model(deepseek-r1:8b).**ERROR**: [Errno 111] Connection refused

Open qiufeihong2018 opened this issue 10 months ago • 2 comments

Describe your problem

Click the OK button and a question is reported: 'Fail to access model (deepseek-r1:8b). ERROR: [Errno 111] Connection refused' Image

qiufeihong2018 avatar Feb 18 '25 11:02 qiufeihong2018

same issue

departurechen avatar Feb 18 '25 23:02 departurechen

Please refer to #2050

KevinHuSh avatar Feb 19 '25 04:02 KevinHuSh

The problem is solved.

For Windows environment, refer to the following steps:

  1. Locate the config.json file. Generally speaking, if you installed Ollama through the regular installer, this file might be in the installation directory, such as C:\Program Files\Ollama. It could also be in the user data directory, for example, C:\Users\YourUsername\AppData\Local\Ollama.
  2. Edit the config.json file to set the listening address:
{
    "host": "0.0.0.0",
    "port": 11434,  // Assume the default port is 11434, adjust it according to the actual situation.
    // Other possible configuration items...
}
  1. Restart the Ollama service.

For Linux environment, refer to the following steps:

  1. You can check your Ollama configuration file (/etc/systemd/system/ollama.service).
  2. Add Environment="OLLAMA_HOST=0.0.0.0" in the service section. Then reload the configuration with the following commands:
systemctl daemon-reload
systemctl restart ollama

qiufeihong2018 avatar Feb 20 '25 02:02 qiufeihong2018

you cansolve this issue via the following instructions:

sudo nano /etc/systemd/system/ollama.service Environment="OLLAMA_HOST=0.0.0.0"

sudo systemctl daemon-reload sudo systemctl status ollama sudo netstat -tuln | grep 11434

test: curl http://:<YOUR_IP>11434

Remember12344 avatar Feb 21 '25 14:02 Remember12344

many thanks

---Original--- From: @.> Date: Fri, Feb 21, 2025 22:37 PM To: @.>; Cc: @.@.>; Subject: Re: [infiniflow/ragflow] [Question]: Fail to accessmodel(deepseek-r1:8b).ERROR: [Errno 111] Connection refused (Issue #5090)

you cansolve this issue via the following instructions:

sudo nano /etc/systemd/system/ollama.service Environment="OLLAMA_HOST=0.0.0.0"

sudo systemctl daemon-reload sudo systemctl status ollama sudo netstat -tuln | grep 11434

test: curl http://:<YOUR_IP>11434

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***> Remember12344 left a comment (infiniflow/ragflow#5090)

you cansolve this issue via the following instructions:

sudo nano /etc/systemd/system/ollama.service Environment="OLLAMA_HOST=0.0.0.0"

sudo systemctl daemon-reload sudo systemctl status ollama sudo netstat -tuln | grep 11434

test: curl http://:<YOUR_IP>11434

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

departurechen avatar Feb 22 '25 03:02 departurechen

http://host.docker.internal:11434

jinzhonglin avatar Feb 26 '25 09:02 jinzhonglin

I met the same error and already solved it. Just use http://host.docker.internal:11434 instead. The cause is that your ragflow request the docker's 11434 port,which is not bound to the host's port,or you input wrong ip,which is not in the same subnet of your host. The ragflow in docker will request the host's 11434 port.

Ventery avatar Feb 28 '25 08:02 Ventery

thanks a lot buddy

---Original--- From: @.> Date: Fri, Feb 28, 2025 16:41 PM To: @.>; Cc: @.@.>; Subject: Re: [infiniflow/ragflow] [Question]: Fail to accessmodel(deepseek-r1:8b).ERROR: [Errno 111] Connection refused (Issue #5090)

I met the same error and already solved it. Just use http://host.docker.internal:11434 instead. The reason is that your ragflow request the docker's 11434 port,which is not bound to the host's port,or you input wrong ip,which is not in the same subnet of your host. The ragflow in docker will request the host's 11434 port.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***> Ventery left a comment (infiniflow/ragflow#5090)

I met the same error and already solved it. Just use http://host.docker.internal:11434 instead. The reason is that your ragflow request the docker's 11434 port,which is not bound to the host's port,or you input wrong ip,which is not in the same subnet of your host. The ragflow in docker will request the host's 11434 port.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

departurechen avatar Mar 01 '25 00:03 departurechen