Frigate NVR Updates: Network Configuration and Bug Fixes
Three pull requests merged yesterday including new networking configuration options for custom port settings, go2rtc source restrictions, and internationalization fixes.
Duration: PT1M23S
Transcript
Good morning. This is your Frigate NVR update for January 29th, 2026.
Yesterday saw three merged pull requests focused on networking improvements and bug fixes.
The most significant change comes from zeroepoch, who merged networking configuration options for custom listening ports. This 189-line addition across 18 files allows users to configure which ports Nginx listens on, addressing scenarios with macvlan networks where all ports are automatically exposed. Users can now bind unauthenticated ports to localhost for enhanced security. The implementation replaces hardcoded port constants throughout the codebase and updates both Docker configurations and documentation.
Blake Blackshear merged a go2rtc source restriction port from the development branch. This 78-line change strengthens security by implementing source validation checks in the go2rtc configuration system, with updated documentation covering the new restrictions.
Marijn0 contributed a small but important fix for missing internationalization keys across three TypeScript files in the web interface, ensuring proper text display in settings wizards and classification views.
What's next: The networking changes provide foundation for more flexible deployment options, while the go2rtc restrictions improve overall security posture.
That's your Frigate update. Back tomorrow with more developer news.