-
-
Notifications
You must be signed in to change notification settings - Fork 162
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
Unable to connect to Ollama #45
Comments
Hey, sorry about that. Is your Ollama server running locally? If not, you need to run it. You can download Ollama from here: https://ollama.com/download |
I'm jumping in to ask about using a remote installation of ollama. When trying something like |
Just to say that the project is really impressive (I've tried with a local server as well). thanks! |
Usually, page assist works with the remote server. I will try to debug it. Maybe it's because of this issue: ollama/ollama#2335
thanks :) |
Great! |
🤔 can you try this command
|
It did. |
Hey guys, a new fix has been released for this issue. All you need to do is go to Settings > Ollama setting and enable custom origin URL, which will resolve the issue. for more information: https://github.com/n4ze3m/page-assist/blob/main/docs/connection-issue.md |
Hey @MicPec I just tested it on the Vivaldi browser (windows) , and it seems to be working fine. Can you try turning on this setting from the web UI settings > Ollama setting? It may resolve the issue. for more details: https://www.youtube.com/watch?v=fydtRnxjfJU or https://github.com/n4ze3m/page-assist/blob/main/docs/connection-issue.md#solutions |
Thanks for quick response. I did try this before, no luck. BTW this is the Linux machine. |
Hey @MicPec , I will test on my Linux machine with Vivaldi. For OpenWebUI and LobreChat, they have a server, but for PageAssist, everything happens in the browser, which is why this issue exists Another fix is by changing Custom origin url in advance settings to
source: ollama/ollama#2335 (comment) |
I've managed to run it, the problem was completely different. The connection was blocked by uBlock 🤦🏻♂️, so I had to add |
Talking of which, and it's not specific to page-assist, I had to change |
Hey @oatmealm In the latest version of Page Assist, there is an advanced URL configuration. All you need to do is enable |
Is it needed when OLLAMA_ORIGINS is set correctly? |
Not needed :) An alternative method only |
Firefox uses My settings that work (the last lines is just so i use a HDD with lots of space for all the models):
|
Hey, sorry about the issue, @uygur55 . Is Ollama and the extension you're trying to connect on the same computer, or are they on two different ones? |
on the same computer. |
Hey @uygur55, that's weird. It usually connects automatically. If possible, can you add this to your environment variable: |
Hi, |
Hey @uygur55, that’s unfortunate. Since you added the env, could you enable the advanced URL option? Please add Also, if you use uBlock, make sure to add the extension ID 'jfgfiigpkhlkbnfnbobbkinehhfdhndo,' as MicPec pointed out in the comment above |
Hey @uygur55, You don't need to add |
After i changed to "chrome-extension://*" Now it is WORKING. |
I had page assist working previously with my remote server which is on a subdomain: https://ollamasubdomain.somedomain.com. I've now tried it on both Arc and Brave and still getting Unable to connect. I have it in custom origin in Advanced settings and not working. Any help appreciated. |
Hello!
I'm experiencing an issue connecting to the local Ollama server while using your page-assist extension. The application displays "Unable to connect to Ollama 🦙" message and a red icon.
I've tried various recommendations from the documentation and discussions, but the problem persists.
Could you provide instructions for running the local Ollama server or suggest other solutions to this issue?
Thank you for your assistance!
The text was updated successfully, but these errors were encountered: