You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Docker deployment runs on the server side with no browser CORS restrictions
368
-
- Supports internal network environments, data stays within your network
369
-
- Request flow: Docker container → Model service provider
370
-
371
-
3. **Use Self-deployed API Proxy Service** (Professional solution)
374
+
2. **Use Self-deployed API Proxy Service** (Professional solution)
372
375
- Deploy open-source API aggregation/proxy tools like OneAPI, NewAPI
373
376
- Configure as custom API endpoint in settings
374
377
- Request flow: Browser → Proxy service → Model service provider
375
378
- Full control over security policies and access permissions
376
379
380
+
**Note**: All web versions (including online version, Vercel deployment, Docker deployment) are pure frontend applications and subject to browser CORS restrictions. Only the desktop version or using an API proxy service can solve CORS issues.
381
+
377
382
#### Q4: I have correctly configured CORS policies for my local model (like Ollama), why can't I still connect using the online version?
378
383
**A**: This is caused by the browser's **Mixed Content security policy**. For security reasons, browsers block secure HTTPS pages (like the online version) from sending requests to insecure HTTP addresses (like your local Ollama service).
379
384
380
385
**Solutions**:
381
386
To bypass this limitation, you need to have the application and API under the same protocol (e.g., both HTTP). We recommend the following approaches:
382
-
1. **Use the desktop version**: Desktop applications have no browser restrictions and are the most stable and reliable way to connect to local models.
383
-
2. **Docker deployment**: Docker deployment also uses HTTP
384
-
3. **Use Chrome extension**: Extensions can bypass some security restrictions in certain situations.
387
+
1. **Use the desktop version**: Desktop applications have no browser restrictions and are the most stable and reliable way to connect to local models
388
+
2. **Use Docker deployment (HTTP)**: Access via `http://localhost:8081`, both the app and local Ollama use HTTP
389
+
3. **Use Chrome extension**: Extensions can bypass some security restrictions in certain situations
0 commit comments