Many enterprise and service provider networks tightly control outbound Internet access. Whether you're deploying FastNetMon in a secure data centre, a regulated environment, or behind a corporate firewall, direct outbound connectivity isn't always an option.
We've recently introduced HTTP and HTTPS proxy support for FastNetMon, making it easier to deploy and operate in environments where outbound traffic must pass through an approved proxy server.
What's New
FastNetMon now supports standard proxy environment variables across:
- FastNetMon (the core daemon)
- fcli
- The FastNetMon installer
Proxy configuration follows established Linux conventions using the standard http_proxy and https_proxy environment variables. Authenticated proxies are also supported, allowing you to include credentials as part of the proxy URL when required.
For compatibility with existing environments and automation, the installer and fcli also recognise the uppercase HTTP_PROXY and HTTPS_PROXY variants.
Built for Enterprise Deployments
Many organisations require all outbound HTTP(S) traffic to traverse a corporate proxy. Until now, this often meant additional workarounds during installation or operation.
With native proxy support, FastNetMon integrates cleanly into existing infrastructure and deployment workflows. Whether you're installing a new instance or running FastNetMon as a long-lived service, proxy configuration uses familiar Linux mechanisms instead of product-specific settings.
For systemd deployments, proxy settings can be configured through standard service overrides. For system-wide configuration, administrators can use /etc/environment, and environments that execute commands through sudo can preserve proxy variables using the standard env_keep configuration.
Simple, Standard Configuration
FastNetMon uses the standard proxy environment variables already familiar to Linux administrators. There are no product-specific proxy settings to learn or maintain.
If you're already managing proxy settings for other Linux applications, you'll find FastNetMon integrates naturally into existing deployment and operational workflows by using the standard http_proxy and https_proxy environment variables supported across the Linux ecosystem.
Learn More
The complete documentation includes configuration examples for:
- HTTP and HTTPS proxy environment variables
- Authenticated proxy configuration
- Configuring the FastNetMon systemd service
- System-wide proxy configuration
- Using proxy settings with
sudo - Verification and troubleshooting
Read the documentation here: FastNetMon Proxy Support Documentation.
