How to install SNMP service on Proxmox

In this guide I just install configure SNMP daemon on Proxmox. SNMP is used to read out the state of the machine, this includes CPU, network (-traffic, -settings,…), memory, … I can suggest LibreNMS, for the monitor. Back to setting SNMP daemon up !

Install the service

  • apt-get install snmpd

Config the service

I like to backup the original configuration (for documentation) :

  • mv /etc/snmp/snmpd.conf /etc/snmp/snmpd.conf.ori

Then I create the config file : /etc/snmp/snmpd.conf

  • # this create a SNMPv1/SNMPv2c community named “my_servers”
  • # and restricts access to LAN adresses (last two 0’s are ranges)
  • rocommunity my_servers
  • # setup info
  • syslocation “rack 1, room 3, serverrroom”
  • syscontact “Svenn”
  • # open up
  • agentAddress udp:161
  • # run as
  • agentuser root
  • # dont log connection from UDP:
  • dontLogTCPWrappersConnects yes
  • # fix for disks larger then 2TB
  • realStorageUnits 0

If needed add an exception to the firewall :

  • iptables -A INPUT -s -p udp –dport 161 -j ACCEPT

And start the service :

  • # debian starts services on install
  • service snmpd restart

And enable by default :

  • update-rc.d snmpd enable


after that its time to test if the connection works from the server that is going to listen to the snmpd :

  • snmpwalk -c my_server -v1 servername SNMPv2-MIB::sysDescr.0

This should return something like :

  • SNMPv2-MIB::sysDescr.0 = STRING: Linux …

That’s it, happy tracking !

Configuring DNS-Over-HTTPS on Pi-hole

Why use DNS-Over-HTTPS?

DNS-Over-HTTPS is a protocol for performing DNS lookups via the same protocol you use to browse the web securely: HTTPS.

With standard DNS, requests are sent in plain-text, with no method to detect tampering or misbehaviour. This means that not only can a malicous actor look at all the DNS requests you are making (and therefore what websites you are visiting), they can also tamper with the response and redirect your device to resources in their control (such as a fake login page for internet banking).

DNS-Over-HTTPS prevents this by using standard HTTPS requests to retrieve DNS information. This means that the connection from the device to the DNS server is secure and can not easily be snooped, monitored, tampered with or blocked. It is worth noting however, that the upstream DNS-Over-HTTPS provider will still have this ability.

Configuring DNS-Over-HTTPS

Along with releasing their DNS service, Cloudflare implemented DNS-Over-HTTPS proxy functionality in to one of their tools: cloudflared.

In the following sections we will be covering how to install and configure this tool on Pi-hole.

Installing cloudflared

The installation is fairly straightforward, however be aware of what architecture you are installing on (amd64 or arm).

AMD64 architecture (most devices)

Download the installer package, then use apt-get to install the package along with any dependencies. Proceed to run the binary with the -v flag to check it is all working.

sudo apt-get install ./cloudflared-stable-linux-amd64.deb
cloudflared -v

ARM architecture (Raspberry Pi)

Here we are downloading the precompiled binary and copying it to the /usr/local/bin/ directory to allow execution by the cloudflared user. Proceed to run the binary with the -v flag to check it is all working.

tar -xvzf cloudflared-stable-linux-arm.tgz
cp ./cloudflared /usr/local/bin
chmod +x /usr/local/bin/cloudflared
cloudflared -v

Configuring cloudflared to run on startup

Create a cloudflared user to run the daemon.

sudo useradd -s /usr/sbin/nologin -r -M cloudflared

Proceed to create a configuration file for cloudflared by copying the following in to /etc/default/cloudflared. This file contains the command-line options that get passed to cloudflared on startup.Copied to clipboard

# Commandline args for cloudflared
CLOUDFLARED_OPTS=--port 5053 --upstream --upstream

Update the permissions for the configuration file and cloudflared binary to allow access for the cloudflared userCopied to clipboard

sudo chown cloudflared:cloudflared /etc/default/cloudflared
sudo chown cloudflared:cloudflared /usr/local/bin/cloudflared

Then create the systemd script by copying the following in to /lib/systemd/system/cloudflared.service. This will control the running of the service and allow it to run on startup.Copied to clipboard

Description=cloudflared DNS over HTTPS proxy

ExecStart=/usr/local/bin/cloudflared proxy-dns $CLOUDFLARED_OPTS


Enable the systemd service to run on startup, then start the service and check its status.

sudo systemctl enable cloudflared
sudo systemctl start cloudflared
sudo systemctl status cloudflared

Now test that it is working! Run the following dig command, a response should be returned similar to the one below

dig @ -p 5053

; <<>> DiG 9.10.3-P4-Ubuntu <<>> @ -p 5053
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 65181
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

; EDNS: version: 0, flags:; udp: 1536
;            IN  A

;; ANSWER SECTION:     299 IN  A

;; Query time: 3 msec
;; MSG SIZE  rcvd: 65

Configuring Pi-hole

Finally, configure Pi-hole to use the local cloudflared service as the upstream DNS server:

Screenshot of Pi-hole configuration

(don’t forget to hit Return or click on Save)

How to Redirect HTTP to HTTPS admin page

Edit lighttpd config

nano /etc/lighttpd/lighttpd.conf
compress.cache-dir = "/var/cache/lighttpd/compress/"
compress.filetype = ( "application/javascript", "text/css", "text/html", "text/plain" )
# [add after the syntax above]
# Redirect HTTP to HTTPS
$HTTP["scheme"] == "http" {
 $HTTP["host"] =~ ".*" {
 url.redirect = (".*" => "https://%0$0")

Restart lighttpd Service

1service lighttpd restart