Skip to content

V9.0.0

Latest
Latest

Choose a tag to compare

View all tags
@ParisNeo ParisNeo released this 31 Oct 02:29
· 169 commits to main since this release
v9.0.0
328e543

Release Notes: Ollama Proxy Fortress v9.0.0

This is a stability and security-focused release that addresses a critical startup bug and hardens the application based on a comprehensive security audit.

🌟 Highlights

  • 🚀 Hyper-Detailed Live Dashboard: Go beyond ollama ps. Get a real-time, auto-updating view of your proxy's health (CPU, Memory, Disk), see all active models across all servers, monitor the live health of your load balancer, and watch API rate-limit queues fill and reset in real-time.

  • 🎨 Radical Theming Engine: Why should your tools be boring? Choose from over a dozen stunning UI themes to match your personal aesthetic. Whether you prefer a sleek Material Design, a futuristic Cyberpunk neon glow, a retro CRT Terminal, or a stark Brutalist look, you can make the interface truly yours.

  • 📈 Comprehensive Analytics Suite: Don't just guess your usage—know it. Dive into beautiful, interactive charts for daily and hourly requests, model popularity, and server load. Plus, with a single click, drill down into per-user analytics to understand individual usage patterns. All data is exportable.

  • 👤 Granular User & API Key Management: Effortlessly create and manage users. The sortable user table gives you at-a-glance stats on key counts, total requests, and last activity. From there, manage individual API keys with per-key rate limits, and temporarily disable or re-enable keys on the fly.

  • 🌐 Multi-Server Management & Federation: Centrally manage all your Ollama backend servers. The proxy load-balances requests and provides a unified, federated view of all available models from all your instances combined.

  • ✨ Polished User Experience: From a streamlined logo upload process to a rich, navigable Help page with a scroll-spying table of contents, every detail has been crafted to be intuitive and enjoyable to use.

  • 🚀 Effortless 1-Click Setup: No Docker, no pip install, no command-line wizardry required. Just download and run a single script.

  • 🛡️ Comprehensive Security Audit: The entire codebase was audited for common security vulnerabilities. The application was found to be well-protected against major threats like SQL Injection, XSS, and CSRF.

  • 🐛 Critical Startup Bug Fix: Resolves a 500 Internal Server Error that occurred for some users immediately after starting the server, making the dashboard inaccessible.

  • 🔒 Minor Information Leak Patched: An error-handling vulnerability on the Settings page has been fixed to prevent leaking potentially sensitive server information.

Detailed Changes

🛡️ Security Enhancements

As part of our commitment to security, a full code audit was performed.

  • Conclusion: The application shows no signs of malware and correctly implements modern security practices. It is not vulnerable to common critical attacks.
  • Vulnerability Patched: A minor information leak was identified and resolved.
    • Previous Behavior: If saving the application settings failed due to an unexpected server error, the raw exception message could be displayed to the admin user.
    • New Behavior: A generic, user-friendly error message is now displayed, while the full technical details are logged to the server console for debugging. This prevents leaking internal server state or configuration details.

🐛 Bug Fixes

  • Fixed NoMatchFound on Startup:
    • Symptom: The application would start successfully but immediately throw a 500 Internal Server Error when navigating to /admin/dashboard. The logs showed a starlette.routing.NoMatchFound: No route exists for name "admin_settings".
    • Resolution: This was caused by an internal route naming conflict. The route for the settings page has been renamed, which completely resolves the issue and ensures the dashboard loads correctly after a fresh installation.

How to Upgrade

If you are running the application from the source code, please follow these steps:

  1. Stop the currently running server (press Ctrl+C in the terminal).
  2. Update the files with the changes provided in the previous step. If you are using Git, you can pull the latest changes.
  3. Restart the application using your run.sh or run_windows.bat script.

No database migrations are necessary for this update.

We are confident that this version provides a more stable and secure experience for all users. Thank you for your support, and please report any further issues on our GitHub page.

Assets 2
Loading