-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
SSL support #701
Comments
Clearly there is always the easy way to have something in front of Ollama, but I was just wondering if this can make sense |
Yeah +1. |
It uses gin so |
Had the same issue and found this thread. I'm not familiar with gin and RunTLS so I used an express server as middleware. Thought I could share the server file since it's so dead simple someone might have use of it :) On the front-end I call the middleware express server on https://yourdomain.com/api/ On the middleware express API I get the response via https, i forward it to ollama as http and return the response as https. No more browser complaints ;) Heres the code for the middleware API const app = express(); // Routes }); // Read SSL certificate and key files // Create HTTPS server server.listen(port, () => { |
Hi super Ollama team!
I received an interest comment on the chatbot-ollama interface here.
It seems that sharing a server and connect from multiple clients works, but it's plain HTTP.
Adding SSL can help in this scenario.
The text was updated successfully, but these errors were encountered: