-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Failed to connect to the server. Please try again later." #419
Comments
Is Ollama accessible at http://localhost:11434? |
Yes, ollama works just fine, and I tried http://localhost:11434 too, but failed.
----------
该邮件从移动设备发送
…--------------原始邮件--------------
发件人:"ItzCrazyKns ***@***.***>;
发送时间:2024年10月20日(星期天) 晚上10:37
收件人:"ItzCrazyKns/Perplexica" ***@***.***>;
抄送:"coderyiyang ***@***.***>;"Author ***@***.***>;
主题:Re: [ItzCrazyKns/Perplexica] "Failed to connect to the server. Please try again later." (Issue #419)
-----------------------------------
Is Ollama accessible at http://localhost:11434?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Use the |
When I use I‘m not sure if 'the logs from the backend' means those logs generated by Docker, if so, here are the files I retrieved from it: If you mean similar log files generated by Perplexica, tell me where they are. I tried to browse its structure but find no .log files. |
did you press the blue button after you updated the config? |
ya, sure, or there would have no log file to generate. |
i had the same bug as you but i got it to stop. could you try to disable the cache in your network tab of your browser maybe? it is a shot in the dark but just see what happens |
Thanks for the tip, I'll give it a shot later! |
Nope! doesn't work for me, but thank you all the same~ |
Is Ollama even running and is it accessible at http://localhost:11434 |
ya, ollama runs just normal at http://localhost:11434 |
Does it work if you use |
both http://host.docker.internal:11434 and http://localhost:11434/ failed even after my pressing the blue save button. |
Not sure what's causing the issue here, can you join our Discord server here: https://discord.gg/sDUJmVNF so I can help you better. Otherwise share me the logs here. |
where are the log files? will join it later. |
don't know how to register this discord. it keeps telling me that my email address is occupied, but it isn't. |
Hi, The option for ollama is not there and it can not fectch it. here is the log `> perplexica-backend@1.9.1 db:push
drizzle-kit: v0.22.7 No config path provided, using default path [i] No changes detected |
well~ i used this one . https://github.com/ItzCrazyKns/Perplexica/blob/master/docs/installation/NETWORKING.md |
Same issue here. Ollama is running, but Perplexica does not connect. I run another docker container with openwebui and that has no problems with Ollama. Ollama is run without container. One thing i do not understand - but i have 0 Linux knowlage -: Everytime I change something in the settings and hit save, in the config.toml file the port jumps from 3000 to 3_001 as you see in the picture. Maybe that is normal. |
Don't worry about the the port just follow the guide here: https://github.com/ItzCrazyKns/Perplexica?tab=readme-ov-file#ollama-connection-errors |
Describe the bug
When I followed Perplexica's instructions to complete the installation within Docker and set the Ollama API URL to http://host.docker.internal:11434 on the setup page, then saved and returned to the main page, it showed "Failed to connect to the server. Please try again later." As shown in the screenshot below.
I have also tried changing http://host.docker.internal:11434 to http://192.168.x.x:11434, but the problem persists.
I have tried other similar solutions from the issue page, but the problem still exists.
About a month ago in the previous version, this problem did not exist.
env: windows 10 ver22H2
sub env: Docker version 27.2.0, build 3ab4256
ver of perplexica: v1.9.1
Expected behavior
debug and explain why this happened.
step-by-step is expected.
Screenshots
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: