To monitor a Linux VPS with Munin, install the munin package on a master server, install munin-node on every VPS that should expose metrics, restrict TCP port 4949 to the master, register each node in /etc/munin/munin.conf, enable suitable plugins, and serve the generated reports through a web server such as Apache2. A single VPS can run both the master and node roles for self-monitoring.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
What Munin does on a VPS
Munin is split into two cooperating roles:
- Munin master: collects metrics from nodes, stores the results, and generates graphs and reports.
- Munin node: runs on a monitored machine and exposes metrics through plugins when the master requests them.
The roles are separate in the upstream documentation. Debian and Ubuntu package the master role conveniently as munin and the monitored role as munin-node. For a small setup, one VPS can run both: install both packages locally, allow the node to accept requests from the master address, and add the VPS as a node in the master’s configuration.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Choose the deployment layout
| Layout | Install on the VPS | When it fits |
|---|---|---|
| One VPS, self-monitoring | munin and munin-node |
You need graphs for one server and do not have a separate monitoring host. |
| Dedicated monitoring VPS | munin on the monitoring VPS; munin-node on every monitored VPS |
You want monitoring to remain available if an application VPS fails. |
| Several application VPSs | munin on one master; munin-node on each monitored machine |
You want one report interface for a fleet of servers. |
The master must be able to reach each node on TCP 4949. Each node should accept connections only from the master’s private or public address, not from the whole internet.
Prerequisites and network plan
Before installing packages, decide which VPS will collect data and which addresses it will use. Record the master’s address as seen by each node. If your provider offers a private network, use the master’s private address for Munin traffic; otherwise use its public address and restrict the firewall to that single source.
#1 Best Overall
- 12th Intel Alder Lake N95 Processor – The GMKtec G3 S Mini PC is powered by the 12th Gen Intel N95 processor with 4 cores, 4 threads, 6MB cache and a burst frequency up to 3.4GHz. Compared with N100/N5105/N5100/N5095, the N95 delivers up to 36% overall performance improvement. Perfect for routine tasks, office work, and home entertainment, this compact mini desktop is more convenient than traditional bulky PCs.
- 8GB RAM & 256GB SSD Storage – Pre-installed with 8GB DDR4 memory and a fast 256GB M.2 2242 SSD, the G3 S mini desktop offers quicker startup, smoother multitasking, and faster file transfers. Enjoy seamless performance whether you’re working on multiple applications, browsing, or streaming content.
- Rich Interfaces & Connectivity – The G3 S mini computer comes equipped with USB 3.2 (up to 10Gbps), dual HDMI 2.0 (4K@60Hz), and a 3.5mm audio jack. With support for WiFi 5, Bluetooth 5.0, and Gigabit Ethernet (RJ45 1000MbE), it connects easily with monitors, projectors, printers, office equipment, and other peripherals, making it versatile for both home and business use.
- Dual 4K Display Support – Featuring upgraded Intel UHD Graphics (up to 1000MHz), the G3 S supports 4K video playback and AV1 decoding for a smooth viewing experience. With dual HDMI outputs, you can connect two 4K@60Hz displays simultaneously, enabling efficient multitasking for work and entertainment.
- GMKTEC WARRANTY - GMKtec offers a 3-year limited warranty (1 year replacement + 2 years parts replacement) for each mini PC, starting from the date of the purchase effective on all sales starting Oct. 2026. All defects due to design and workmanship are covered. With a professional after sales team always ready to attend to your needs, you can simply relax and enjoy your mini PC
- Debian or Ubuntu on the master and monitored VPSs.
- Root access or a sudo-enabled account.
- A reachable address for the master and every node.
- Permission to change the VPS firewall or cloud security group.
- A web server on the master for viewing generated reports. Apache2 is the documented Ubuntu example.
For one IPv4 master host, the node’s CIDR rule uses a /32 suffix. Replace the example addresses below with your real values; 203.0.113.10 and 203.0.113.20 are documentation-only addresses.
Install Munin on the master
Run these commands on the VPS that will collect data and host reports:
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorssudo apt updatesudo apt install munin
The Debian/Ubuntu munin package supplies the master-side configuration and report-generation components. If this same VPS is also being monitored, install the node package on it as described in the next section and apply the node access restriction to the local address.
Install Munin Node on every monitored VPS
On each VPS whose operating-system and service metrics you want to collect, run:
sudo apt updatesudo apt install munin-node
Install the node package on the master too when the master is expected to graph its own CPU, memory, disk, network, or service data. The package normally creates a service that starts at boot, but verify the status on the distribution image you use.
Restrict the node to the master
Munin-node listens on TCP 4949 by default. Its access list is independent of the network firewall, so configure both layers.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallUse a regular-expression allow rule
Edit /etc/munin/munin-node.conf on the monitored VPS and add an allow rule for the master’s address:
allow ^203.0.113.10$The escaped dots make the rule match that IPv4 address rather than any character in those positions. Keep the rule anchored with ^ and $ so a longer or different address is not accidentally accepted.
Use a CIDR rule
You can express the same single-host permission with:
cidr_allow 203.0.113.10/32For one IPv4 host, /32 is required. If the master reaches the node through IPv6, use the master’s IPv6 address and the appropriate IPv6 prefix instead of copying the IPv4 example.
Allow the port in the VPS firewall
In the host firewall or cloud security group, create an inbound rule for TCP 4949 whose source is only the master’s address. Do not publish 4949 to 0.0.0.0/0 or an unrestricted internet-facing security group. The node protocol is intended for the Munin master, not for public browser access.
Rank #2
- 【AMD Ryzen 3 5300U CPU: Outperforms N150 & 3500U】 BOSGAME E5 mini PC is powered by the TSMC 7nm FinFET architecture AMD Ryzen 3 5300U processor (4 Cores, 8 Threads, up to 3.8GHz boost, 6MB total cache). Compared to low-end Intel N150 or 3500U chips which only have 4 single threads and throttle under load, the 5300U delivers over 30% faster multi-core speed. Run 30+ browser tabs, large Excel sheets, and Zoom meetings simultaneously without system lag.
- 【8GB DDR4 RAM & 256GB NVMe SSD Storage】 Installed with high-speed 8GB DDR4 dual-channel memory and a fast 256GB M.2 2280 SSD, eliminating slow boot times and application loading delays. To accommodate growing data requirements, the upgradeable hardware design features dual SODIMM slots that allow you to expand memory up to 64GB RAM, ensuring smooth operation during heavy multitasking.
- 【High-Capacity Dual M.2 SSD Storage Expansion】 Never worry about running out of space for your business files. In addition to the pre-installed 256GB system drive, the motherboard houses an extra empty internal M.2 2280 NVMe PCIe 3.0 slot. This allows you to easily add a second solid-state drive for up to an additional 2TB of storage capacity (upgrades not included) without needing to remove or reinstall the original operating system.
- 【Radeon 6-Core Graphics & Triple 4K Displays】 Integrated with official AMD Radeon Graphics (6 Graphics Cores, 1500 MHz frequency) for casual gaming, photo editing, and crisp 4K media decoding. Featuring 1x HDMI 2.0 port, 1x DisplayPort, and 1x Full-Function Type-C port, the E5 outputs true 4K@60Hz resolution to three monitors at once. This multi-screen setup eliminates constant window-switching for traders, programmers, and office workers.
- 【Dual 2.5GbE LAN Ports for Advanced Networking】 Experience fast wired network transmission speeds up to 2500Mbps without lagging or buffering. The integration of dual 2.5 Gigabit Ethernet ports (powered by Realtek RTL8125 controller) makes this compact computer an exceptional hardware choice for tech enthusiasts. Easily configure it into software routers, hardware firewalls (pfSense, OpnSense), home NAS servers, or local homelabs.
Register the node on the master
On the master, edit /etc/munin/munin.conf. Add one node block for each monitored VPS:
[web-01.example]
address 203.0.113.20The text in square brackets is the hostname displayed in Munin reports. It does not have to resolve in public DNS, but use a stable, recognizable name. The indented address value must be the address that the master can actually reach on TCP 4949.
For a second node, add another block with a different display name and address:
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →[db-01.example]
address 203.0.113.30Do not reuse one node name for multiple machines: Munin uses the name to identify collected time-series data and generated reports.
Discover and enable plugins
Munin gathers most metrics through plugins. On a node, inspect what the installed package can use:
sudo munin-node-configure --suggestThe command reports plugins that appear compatible with the machine and identifies requirements that may be missing. Suggestions are not a guarantee that every plugin is appropriate: review them for the services actually running on the VPS and for any credentials or permissions they require.
The official automatic-install form is:
sudo munin-node-configure --shell --families=contrib,auto | sudo sh -xUse that pipeline only after reviewing the suggested output. A plugin is enabled when a symlink for it exists in /etc/munin/plugins. The symlink points to a plugin supplied by the package, while the name in that directory determines what the node advertises.
Free tools Windows power users keep installed
One-click scans. No signup required.
After adding or removing plugin links, restart the node. Munin-node discovers its plugin set when it starts, so a configuration change alone may not take effect.
Restart the node and check its service
After changing munin-node.conf or the plugin links, run:
sudo systemctl restart munin-node.serviceThen inspect the service:
sudo systemctl status munin-node.serviceIf the service fails, examine the status output and the logs provided by your distribution package. Syntax errors, an invalid allow rule, a plugin with missing permissions, or a plugin that exits with an error can all prevent useful collection. Log locations and exact unit packaging vary between Debian and Ubuntu releases, so use the unit’s reported journal and package documentation rather than assuming one fixed file path.
Recommended Free Tools
Serve Munin reports with Apache2
The Ubuntu installation example uses Apache2 to publish the master’s generated Munin reports. Install Apache2 on the master if it is not already present, then use the Munin package’s Apache configuration. A typical package installation is:
Rank #3
- 【1-Year Worry-Free Warranty】Your satisfaction is our priority. Glorlin provides a 1-year warranty covering any hardware malfunctions. We support returns or exchanges to ensure a 100% worry-free shopping experience. Have a question? Reach out to us through our official after-sales email for a prompt solution.
- 【Reliable Performance with Ryzen 7 Processor】Powered by AMD Ryzen 7 8745HS (8 cores, 16 threads, up to 4.9GHz), this mini pc delivers stable performance for daily workloads. Suitable for office tasks, programming, and multitasking, it works well as a ryzen mini pc for both home and business use.
- 【Radeon 780M Graphics for Media and Light Gaming】Equipped with integrated Radeon 780M graphics, this mini gaming pc supports smooth 4K video playback and handles many popular games at adjusted settings. A practical mini computer for media, editing, and casual gaming.
- 【Mini PC 16GB RAM and Fast Storage】This mini pc 16gb ram configuration includes single 16GB DDR5 memory (4800MHz，3GB is assigned to VRAM by default) and a 1TB NVMe SSD, offering quick boot times and responsive system performance. Dual M.2 slots allow storage expansion up to 4TB for growing files and projects.
- 【Quad 4K Display Support for Productivity】The mini desktop computer supports up to four 4K displays via HDMI, DisplayPort, and dual USB-C ports. Ideal for multi-screen workflows such as coding, trading, or content creation with improved efficiency.
sudo apt update
sudo apt install apache2The reports are intended to be viewed through the web server on the master, not through the node’s port 4949. If you can view reports only from the master itself, Apache may still be using a Require local rule. To view the reports from an administration workstation or another approved network, edit the Munin Apache access configuration and replace that local-only restriction with the specific viewer IP or network you intend to permit.
Keep the browser-facing report directory protected. Grant access to named administration addresses or a controlled internal network rather than opening the reports to every internet client. This is separate from the node firewall rule: TCP 4949 controls master-to-node collection, while Apache access rules control human access to graphs.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Verify collection from end to end
Check the setup in this order so that a failure is isolated to one layer:
- Node service: confirm
munin-node.serviceis running after the restart. - Plugin links: confirm the expected names appear as symlinks in
/etc/munin/plugins. - Node access: verify the firewall allows TCP 4949 from the master’s actual address and that
alloworcidr_allowmatches that same address. - Master registration: check the node name and
addressblock in/etc/munin/munin.conffor indentation, spelling, and the reachable address. - Report access: open the master’s Munin report through Apache from an address permitted by its access rules.
Do not expect a complete historical graph immediately after installation. Munin must collect samples over time before the daily, weekly, monthly, and yearly views contain meaningful history.
Troubleshoot common Munin VPS problems
No data for a node
- Confirm the master configuration uses the node’s reachable address, not an address valid only from another network.
- Test the firewall or cloud security group for inbound TCP 4949 on the node, with the master as the source.
- Compare the master’s source address with the node’s
alloworcidr_allowrule. A private-network connection may arrive from a private address even when you expected the public one. - Restart
munin-node.serviceafter editing its configuration. - Review node and master service logs for connection refusals, access-denied messages, or configuration syntax errors.
Graphs are empty or only partly populated
- Allow collection time. Newly installed reports have no earlier data to display.
- Check whether the relevant plugin symlink exists in
/etc/munin/plugins. - Run
sudo munin-node-configure --suggestto identify plugins that were not enabled or that require additional software. - Restart the node after changing plugin links, because the running node does not automatically rediscover them.
- Look for plugin permission or execution errors in the service output and logs.
The plugin you need is missing
Plugin availability depends on the package and services installed on that VPS. Start with munin-node-configure --suggest; it can identify compatible plugins and their prerequisites. Enable only plugins that correspond to services you operate, then restart the node. If a suggestion reports a missing dependency, install that dependency according to the service’s own Debian or Ubuntu package instructions before enabling the plugin.
The browser says access is denied
This is usually an Apache authorization issue rather than a Munin-node issue. Review the Munin Apache configuration for Require local. Add only the viewer’s intended IP address or network, reload or restart Apache using your distribution’s normal procedure, and try again. A browser does not need access to TCP 4949 to view reports; it needs access to the Apache endpoint on the master.
The node service will not start after an edit
Undo the most recent change or correct its syntax, then run the service status command again. Check for malformed regular expressions, an invalid CIDR value, duplicate or conflicting settings, and plugin links that point to unavailable executables. The package’s journal output is the authoritative place to identify the failing line or plugin on the VPS image in use.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Security and operational practices
- Minimize exposure: allow TCP 4949 only from the master and keep Apache reports limited to approved viewers.
- Use stable addresses: if a node’s public address changes, update both the master’s
addressentry and the node’s allow rule, or use a stable private network address. - Separate monitoring when possible: a dedicated master continues to hold and display historical data when an application VPS is unavailable.
- Keep plugin scope intentional: enabling every suggestion can create unnecessary load or expose metrics you do not need. Review the list and retain only useful plugins.
- Recheck after upgrades: package updates can change plugin availability, service behavior, or web-server configuration. Confirm the node service, report generation, and Apache access after major system maintenance.
- Protect the reports: Munin graphs can reveal traffic, storage, process, and service behavior. Treat the report site as operational data, not a public status page.
Package installation versus building from source
For Debian and Ubuntu VPSs, the documented path is the distribution packages: munin for the master and munin-node for monitored machines. Packages integrate with the operating system’s service manager, configuration directories, plugin layout, and update mechanism. A source build is a separate deployment choice that requires you to manage those integration details yourself; the commands and paths in this guide assume the Debian/Ubuntu packages and should not be copied unchanged to a source installation.
Master, node, and web access: keep the boundaries clear
| Traffic or component | Purpose | Access to permit |
|---|---|---|
| Master to node, TCP 4949 | Requests metrics from Munin plugins | Only the master’s address to each node |
| Apache on the master | Serves generated graphs and reports to people | Only approved viewer addresses or networks |
| Node plugins | Collect local operating-system and service metrics | Local execution under the package’s service account and permissions |
Understanding these boundaries prevents two common mistakes: opening the node protocol to the internet because a graph page is inaccessible, and changing Apache rules when the actual problem is that the master cannot reach port 4949.
Adding another VPS later
- Install
munin-nodeon the new VPS. - Permit the existing master’s address in
/etc/munin/munin-node.confwith an anchoredallowrule or a correctly sizedcidr_allowentry. - Allow TCP 4949 from the master in the new VPS firewall or cloud security group.
- Run
munin-node-configure --suggest, enable the plugins appropriate for that VPS, and restartmunin-node.service. - Add a unique node block and reachable
addressto the master’s/etc/munin/munin.conf. - Wait for collection, then verify the new node’s reports through the master’s Apache site.
Repeat the same sequence for each machine. The node name in the master configuration is the label readers will see, so choose names that identify the server’s purpose without changing them casually after data collection begins.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
