Failed to connect to the server... Seems like you are using the custom OpenAI provider...

[digitalenterprises]

Describe the bug
After install when I go to the url http://localhost:3000/ I get two errors:
"Failed to connect to the server. Please try again later."
and
"Seems like you are using the custom OpenAI provider, please open the settings and configure the API key and base URL"

To Reproduce
Steps to reproduce the behavior: go to the url http://localhost:3000/

1. Go to the url http://localhost:3000/

Expected behavior
I expected perplexica screen to load.

Screenshots

Additional context
Ollama is not installed in docker but is running and working http://127.0.0.1:11434/
Searxng is running in docker and is running and working http://127.0.0.1:32768/
I am running on ubuntu PopOS

[ItzCrazyKns]

Please follow: https://github.com/ItzCrazyKns/Perplexica?tab=readme-ov-file#ollama-connection-errors

[digitalenterprises]

Thank for the response.
I have previously tried your suggestions from reading similar issues here.

Linux: Use http://<private_ip_of_host>:11434
Inside /etc/systemd/system/ollama.service, added Environment="OLLAMA_HOST=0.0.0.0"

I know the port isnt blocked since Im using open-webui in docker and it connects to ollama on http://127.0.0.1:11434

[ItzCrazyKns]

Please remove the / from the end of the URL. If that doesn't work can you show the output of sending a curl request at the same URL.

[digitalenterprises]

Removing the slash didnt work. Here is the result of the curl request:

`$ curl -i http://192.168.111.3:11434
HTTP/1.1 200 OK
Content-Type: text/plain; charset=utf-8
Date: Sun, 17 Nov 2024 14:05:47 GMT
Content-Length: 17

Ollama is running(base)`

[ItzCrazyKns]

Did you pressed the blue save button after removing the / from the URL?

[digitalenterprises]

Did you pressed the blue save button after removing the / from the URL?

Yes, I did save it.

[SCharan24]

Had similar issue, but on windows. After changing the"Chat Model provider" it worked. Hope this helps.

[digitalenterprises]

Had similar issue, but on windows. After changing the"Chat Model provider" it worked. Hope this helps.

Thank you for the response. However, I have no options for chat model provider, only the default.