Closed mrdjohnson closed 1 month ago
Hi @mrdjohnson, are there any specific errors in the browser console logs? That could help with debugging, we had some CORS changes recently so this could have effected this.
Thanks for the update @mrdjohnson, I was able to reproduce this. I have a change up (#4086) that will fix the issue.
Looking forward to the change!!
are those config options modifiable by the user? or do i need to wait for this PR to be merged?
@mrdjohnson this change is going to need the PR to be merged
@BruceMacD Congrats on the merge!
Will this be fixed automatically when the next version of ollama comes out?
It should be, just needs an ollama version update when the next release it out.
Okay! I'm still a little lost on how calling the api manually works, but calling it through ollamajs did not work, but looking forward to the change!
When using ollama/browser and trying to pull models or show information my users get CORS issues. I have replicated this issue on firefox browsers. I am able to load models initially because I am calling it manually, but when getting the same list of models through ollamajs they run into CORS issues.
I am not sure what is going on but it is strange that a manual fetch works (in my case) but a fetch through the library does not
any advisement would be helpful!