In this post, I will be configuring it with Signal. To deploy Mailrise with Signal, I will be using an LXC container on a Proxmox server running Debian (I am using a template I created that has docker preinstalled. Instructions to install it can be found here).

A brief overview of what we need to do is found below.

• Deploy the Signal REST-API docker image found here. You can find the setup instructions on the apprise documentation page found here.
• Link your Signal account to the Signal REST- API docker image.
• Generate a mailrise.conf file.
• Deploy Mailrise with docker-compose

Signal

First, make a directory that will hold the docker-compose files. I will be using the /opt/docker directory. You will need elevated privileges to create the directory if you are not running as root.

sudo mkdir -p /opt/docker/signal-rest-api/

• If you are not running as root, you will need to change the ownership of the /opt/docker/ folder. You can do this by using sudo chown -R <user>:<user> /opt/docker/. Change the <user> to your username.

You can run this with docker as shown in the Getting Started page of the project's README here. I prefer to use docker-compose as I can see the configuration that I used to deploy the container.

Next, create the docker-compose.yml file for the Signal REST-API docker image.

nano /opt/docker/signal-rest-api/docker-compose.yml

version: '3'

services:
  signal-api:
    image: bbernhard/signal-cli-rest-api
    container_name: signal-api
    restart: always
    environment:
      MODE: native
    ports:
      - 8080:8080
    volumes:
      - ./signal-cli:/home/.local/share/signal-cli

Bring up the container by running the docker-compose -f /opt/docker/signal-rest-api/docker-compose.yml up -d (Or docker-compose up -d if you're in the directory where the docker-compose.yml file is located).

Register your Signal number by going to http://10.0.69.1:8080/v1/qrcodelink?device_name=signal-api. Replace 10.0.69.1 with the IP address of your machine. You can link your number by going to the Signal app > Settings > Linked Devices.

Mailrise

To deploy Mailrise, make a directory in the /opt/docker directory.

mkdir /opt/docker/mailrise

Then create the docker-compose.yml file in the /opt/docker/mailrise directory using nano.

version: '3'

services:
  mailrise:
    container_name: mailrise
    image: yoryan/mailrise
    restart: unless-stopped
    ports:
      - 8025:8025
    volumes:
      - ./mailrise.conf:/etc/mailrise.conf

Before deploying the container, you will need to create the mailrise.conf file. The docker-compose.yml file sets the location of the mailrise.conf file in the same directory as indicated by the ./ in the last line of the configuration file.

Note: If you don't create the file, a directory will be created when the container is deployed. You'll need to remove the folder and create the file.

nano /opt/docker/mailrise/mailrise.conf

configs:
# The following line will be the email username for the email destination address.
# Because it is set as signal, the email address to be used is signal@mailrise.xyz
  signal:
    urls:
    # The following will send a Signal "Note to Self".
      - signal://10.0.69.1:8080/18001234567
    # The following will send a signal message to the second number in the URL.
      - signal://10.0.69.1:8080/18001234567/18007654321
    # You can leave both lines to receive a "Note to Self" and send the message to the specified number as well.
# In the line below, the email username is set to jamesjonahjameson, so the email recipient will be jamesjonahjameson@mailrise.xyz
  jamesjonahjameson:
    urls:
      - signal://10.0.69.1:8080/18001234567/15557654321

Note: Modify the signal:// lines to reflect your IP address and Signal recipient and destination phone number. You can also choose if you want to send a message to yourself or to another Signal number.

In the mailrise.conf file shown above, there is a section for signal and another section called jamesjonahjameson. These can be used to have different email recipients so that when you send an email to signal@mailrise.xyz, you get a signal Note to Self. When you send an email to jamesjonahjameson@mailrise.xyz, someone else gets notified.

There are several urls you can add to the config file, such as Microsoft Teams, PagerDuty, Home Assistant, Mastodon, PushBullet, Pushover, and so many more. You can find a list of all the supported notification services here.

After you configure the mailrise.conf file, bring up the container with docker-compose -f /opt/docker/mailrise/docker-compose.yml up -d (Or docker-compose up -d if you're in the directory where the docker-compose.yml file is located).

Verifying installation

You can verify the docker containers are running by executing docker ps.

Note: If you have any errors running a container, you can check the logs by running docker logs <container_name> -f. You can also run docker-compose logs -f if you are in the directory where the docker-compose.yml file is at.

An example of the directory structure can be found below (You can run tree /opt/docker/ to check your file structure).

[user@fedora ~]# tree /opt/docker/
.
├── mailrise
│   ├── docker-compose.yml
│   └── mailrise.conf
└── signal-api
    ├── docker-compose.yml
    └── signal-cli

Using Mailrise

There are several ways you can use Mailrise to send notifications.

Linux

In Linux, you can use ssmtp to create an email from the command line.

After installing ssmtp, modify the /etc/ssmtp/ssmtp.conf file to have the following

mailhub=10.0.69.1:8025
UseTLS=NO
UseSTARTTLS=NO
FromLineOverride=YES
FromLineSender=YES

Now that the configuration for ssmtp is done, you can send a message by executing the following:

echo "Current Directory is $(pwd)" | ssmtp signal@mailrise.xyz

A more useful example command can be found below.

{
    echo To: signal@mailrise.xyz
    echo From: from_email@example.com
    echo Subject: Current user is $USER
    echo "Body Message goes here"
    echo "You can add more info here such as the IP address"
    echo "Public IP is :" $(curl ifconfig.co)
    echo "Private IP is $(ip addr show eth0 | grep 'inet\b' | awk '{print $2}' | cut -d '/' -f1)"
} | ssmtp signal@mailrise.xyz

Windows (PowerShell)

In Windows, you can use the Send-MailMessage PowerShell cmdlet (more info found here). You can add variables to receive some information about the system as well.

Send-MailMessage -From "admin@$env:COMPUTERNAME.local" -To "signal@mailrise.xyz" -Subject "subject" -Body  "Machine running $env:PROCESSOR_ARCHITECTURE" -SmtpServer 10.0.69.1 -Port 8025

To get started, we will need a Windows Server 2022 Server VM, as well as a few Windows 11 VMs. The Windows 11 VMs must be running a version that supports joining a domain, which includes Windows 11 Professional, Enterprise, and Education.

I have templates made for Windows Server 2022 and Windows 11 Enterprise in my Proxmox server. These are both running the evaluation editions from Microsoft.

Proxmox Network Setup

To begin, you will need to create a bridge under Proxmox so that the VMs can communicate with each other. The bridge created will only be used for the Windows Active Directory environment. You can see this in the diagram below.

To create the Linux bridge, go to your Proxmox web interface, click on your node name, then go to System > Network.

You will need to create a new Linux Bridge. To do so, click on Create > Linux Bridge. Add a comment to signify that this will be the bridge used for the Active Directory Home Lab. The bridge I will be using is named vmbr3. After the Active Directory lab is configured, we can bridge a port to the vmbr3 bridge. This will let us use a network adapter connected to the Proxmox server to connect physical Windows devices to the Active Directory domain.

The next step is to create a clone of Windows Server 2022. Right click on the template, and select Clone. Change the mode to Full Clone, give it a VM ID (I choose 801), and choose a name for it. I will name mine HL01-WindowsServer2022. Then click Clone.

Do the same for the Windows 11 template. I named my Windows 11 VM HL01-Windows11-Client01 and gave it a VM ID of 802. Make sure you change the mode to Full and click Clone.

The time it takes to fully create the VM under Proxmox can vary depending on your hardware.

The next step is modify the network devices of each VM. The Windows Server 2022 (VM ID 801) will act as the default gateway, so it needs to have two network adapters. I will add a network device and choose the Linux Bridge we created earlier ( vmbr3). Make sure the model of the network device is VirtIO (Paravirtualized). The other network device is attached to a Linux bridge that has internet access (vmbr1 in the following image).

On the Windows 11 VM, we now have to change the bridge of the current network device to be vmbr3 as that is the one we created earlier. The Windows 11 VM will then communicate with the Windows Server via the network device connected with the bridge vmbr3.

Windows Server 2022 Setup

Now we're ready to start up our Windows Server 2022 VM. The initial setup is similar to previous Windows installations. Set the local Administrator password and login. Select Yes when you are asked if you want to allow your PC to be discoverable by other PCs.

The first thing to do is to rename the Windows Server. Go to Settings > System > About. Then choose Rename this PC. I named mine DC01 and choose Restart Later.

The next step to do before rebooting is to rename the ethernet adapters. Go to Control Panel > Network and Internet > Network and Sharing Center. Then choose Change adapter settings.

One of the network adapters should have internet connectivity. You can identify which one by double clicking on them and seeing if they have internet connectivity.

Rename them so that you know which one has an active internet connection. I renamed mine Internet. I then renamed the other ethernet adapter as Internal. I restarted the VM at this point.

We then have to set an IPv4 range for the AD network. You can so this by once again going to Control Panel > Network and Internet > Network and Sharing Center. Then choose Change adapter settings.

Double click the Internal network device, click on Properties, select Internet Protocol Version 4, and click Properties.  

In the Properties tab, you have to select a private IP range that will not interfere with your current network.

The IP range I chose for my home lab is 172.16.0.1/16. You can find more info about the private IP ranges in RFC1918 here.

The IP of the domain controller is set to 172.16.0.1, with a /16 subnet. I did not specify a gateway as the domain controller will act as the default gateway. I specified the localhost address (127.0.0.1) as the DNS server as the domain controller will serve as a DNS server. Select OK and the close the Properties window.

Setup Active Directory Domain Services

The next step is to setup Active Directory Domain Services. To do so, open Server Manager and lick on Add roles and features. Select Next to accept the default settings until you're prompted with the Server Roles section. Choose Active Directory Domain Services, confirm by clicking the Add Features button, then lick on Next to accept the default settings until you can select the Install button. Once it has installed successfully, select Close.

The next step is to promote the server to a domain controller. You will need to have the domain name you want to use in the next step. There are several best practices when choosing a domain name, such as having a FQDN from a top-level registrar. You can find some of Microsoft's best practices here. Because I am deploying this in a home lab environment, I will choose the domain name of mydomain.com.

To promote the server to a domain controller, click on the notification icon on the top section of the Server Manager program. Then select Promote this server to a domain controller. Select Add a new forest as this in a newly created AD environment. Enter the domain name in the Root domain name: area.

You will then need to set a password for the Directory Services Restore Mode. Enter a secure password and click Next. Accept the default settings for the following prompts by selecting Next. You will receive some warnings but these are okay for our home lab environment use case. This process can take a while so be patient. The Windows Server 2022 VM will restart automatically when the process is completed.

Once the Windows Server has rebooted, you will see the login screen show the domain entered in the previous step.

Create a domain administrator account

The next step we want to do is to create a domain administrative account. This is a good practice and it can enable proper monitoring of logs to see who accesses the server and what changes they may make.

First, we have to login with the built in Administrator account. To create a domain administrative account,  we need to open Active Directory Users and Computers. This can be found in the Start menu under Windows Administrative Tools.

Expand the mydomain.com section (or whichever domain name you chose previously). Right click on mydomain.com and select New > Organizational Unit (OU).

I created two OUs called _IT Staff and _Staff.  I unchecked Protect container from accidental deletion as this makes it easier to manage in my home lab environment.

To create an IT Adminstrator, I right clicked the _IT Staff OU, then selected New > User. In the pop up windows, enter the credentials for the domain administrator account you want to create. In most organizations, usernames are created by using the first initial of their first name, followed by their last name. Because I am creating an administrative account, I want to denote this is the User logon name section. I will be denoting administrative accounts by adding the prefix admin- to the User logon name.

Then set a password for the account. I disabled the option User must change password at next logon  and the Password never expires because I am deploying this in my home lab environment. In an organization, this option should be checked so that the end user can set their own password. In an organization, Password never expires may need to be unchecked depending on their password policy requirements.

Now we need to add the newly created account to the Domain Admin group. This can be done right clicking the newly created user and selecting Properties.

Select the Member of tab. You will notice that the user is a member of the Domain Users group. Click on Add. You will get a pop up titled Select Groups. Under the Enter the object names to select section, click on the Advanced button. Then click Find now button on the pop up window. Select Domain Admins and click OK.

NOTE: If you know the name of the object name, you can type it in when the Select Groups pop up windows shows up as shown below.

We can then logout of the Administrator account and login with our newly created domain account.

Installing RAS/ NAT

The next step is to install RAS/NAT. If we take a look at the network diagram, this will allow the AD clients to receive Internet access via the domain controller.

To get NAT installed, we have to once again open Server Manager. Select Add roles and features. Select Next to accept the default settings until you reach the Server Roles section. Select the Remote Access checkbox as this will install NAT. Select Next. Then when you get to the Role Services section, enable the Routing checkbox, and click on the Add Features button. This should auto select the DirectAccess and VPN (RAS) checkbox. Select Next > Next > Next. Then click on the Install button and wait for the features to get installed.

Next, go back to the Server Manager program. Then click on Tools > Routing and Remote Access.

In the Routing and Remote Access window, right click on the domain controller's name (DC01) and select Configure and Enable Routing and Remote Access. Select Next and then choose Network Address Translation (NAT). Select Next.

NOTE: If you don't see any network adapters in this step, close the wizard and close the Routing and Remote Access windows. Reopen it and they should appear.

Because we labeled the devices earlier, we can see which adapter is being used for internet access. Select the one labeled Internet and click Next. Then select Finish. If you don't see any changes, you might need to refresh by right clicking the domain controller's name and selecting Refresh.

Setting up the DHCP Server

The next step is to setup the DHCP server on the Windows Server. This can be done by going to the Server Manager program. Click on Add roles and features. Select Next until you reach the Server Roles section. Select DHCP Server from the list and click on Add Features in the pop put window. Select Next to accept the defaults settings and then select Install.

To complete the DHCP configuration, you have to click on the Notifications flag icon in Server Manager and select Complete DHCP Configuration. Specify the credentials to be used to authorize this DHCP server in AD DS. I chose the domain account I created earlier admin-asanchez.

We then have to configure a DHCP scope. To do so, go to Server Manager once again. Then select Tools > DHCP. Expand the available options and then right click on IPv4 to create an IPv4 scope.

Set a name for the scope and give it a description if you wish to do so. Select Next. Now to select the scope for the IPv4 addresses, we have to refer back to our initial network diagram. We chose to implement a 172.16.0.1/16 network. This gives us the available IP range of 172.16.0.2 to 172.16.255.254 with over 65,000 available IP addresses.

Then you can exclude some IP addresses from being handed out by the DHCP server. I choose to exclude the IP ranges of 172.16.0.2 to 172.16.9.255. The first available IP address the DHCP server should hand out would be 172.16.10.0. I reserved these addresses so I can know that devices with those IP addresses were manually assigned. This lets me organize devices and manage their network access. I use this feature in my own network to easily identify devices such as printers, managed switches, etc.

When you are prompted to choose the lease duration, this depends on how long a typical host will be connected to the network. The default of 8 days is okay for our home lab use case.

When prompted if you want to configure DHCP options for this scope now, choose Yes, I want to configure these options now, then select Next. You will then be prompted to select the IP address for the default gateway. The IP address we gave our default gateway was 172.16.0.1. Enter that and click on Add. Then select Next.

The pre-configured options in the Domain Name and DNS Servers are okay for our use case so select Next.

I am not configuring WINS so I will select Next on the WINS Server section. Then when prompted if you want to activate the scope now, make sure Yes, I want to activate this scope now is selected and hit Next then Finish.

You might need to refresh to see the changes.

Using a script to create multiple users

Next you can create users you want to have in your domain. You can do this manually as shown in the previous step where we created a domain admin account. You can use a script as well to quickly create multiple user accounts.

I will be modifying a script by Josh Madakor. The link for the script can be found below.

https://github.com/joshmadakor1/AD_PS/archive/master.zip

Download the .zip file on the Windows Server 2022 VM. I copied the extracted file to the Desktop. Then open up PowerShell ISE and run it as an administrator.

The first pre-requisite to run the script is to run the following command.

Set-ExecutionPolicy Unrestricted.

This is to allow the script to run on the server. You can restrict the policy after running the script if you would like.

Enter dir to show the contents of the directory. The script is set to use the names.txt file but I created my own called staff.txt so I will  modify the script to use this file instead.

Open up the PowerShell scripts in PowerShell ISE. Then change the file the script will use to generate the user accounts (from names.txt to staff.txt), the defaut password used (the script has it set at Password). Then change the OU the user accounts will be placed at. I changed it so that the new accounts will go to add users to the _Staff OU I created earlier.

After modyfing the script. save it then run the script. I have Active Directory Users and Computers window on the right. Refreshing it after running the script will show the newly created user accounts.

We can now begin configuring the Windows 11 VM.

Windows 11 Setup

Since we have already configured the Windows 11 VM, we are now ready to start it up under Proxmox. Go through the initial setup wizard. When you are prompted to sign in, select Sign-in options. Then enter the username and password for the local administrator of the PC.

I like to disable the telemetry options when prompted.

After Windows 11 finishes the setup process, you will be logged in to the account that you created earlier. When we open up a command prompt and run ipconfig, we see that the Windows 11 VM has a valid IP address.

The next step is to join the Windows 11 VM to the domain. To do so, open the Settings program. Then go to Accounts > Access work or school. Then click on the blue Connect button. In the pop out window, select the option Join this device to a local Active Directory domain. Enter the domain name we used to configure our Active Directory forest (I used mydomain.com). You will then be prompted with a login prompt.

I entered the credentials for a user I created earlier, jjameson. I did not specify the account type as I want to see what default permissions are for the domain.

Windows 11 will restart after entering the credentials. After rebooting, you can now login to the domain by selecting Other User in the lower left corner.

Final thoughts

So now we have a working active directory home lab environment. There is still a lot of work to as we have to manage what permissions each OU has, as well as manage the group policies per OU, we can add storage to the domain controller and share access with only the users that require it. One issue I noticed is that when I added the jjameson account to the domain via the Windows 11 VM and skipped the step to set their permissions, I noticed that the user account would have the default permissions for the domain. After using the jjameson account for a few minutes, I noticed that there were a few access control policies I would like to implement. But this is a great way to get started and learn more about how to manage an Active Directory environment in a non-production environment. Because I am hosting the Windows Server in a VM in proxmox, I can also backup the VM, create snapshots, and easily restore to a previous point if I want to revert any changes that I make.

I have a Proxmox cluster setup and I'm adding Windows Server 2022 and Windows 11 Enterprise virtual machines to it to become more familiar with Active Directory. Having virtual machines can let me mess around with different configurations and if I break something, I can revert back by using the snapshots feature. I also want to get familitar with the process of creating an Active Directory without referencing to my documentation as often as I currently do.

To begin, you will need the evaluation image for Windows Server 2022 which can be found here.

You will also need the VirtIO Drivers. You can find them here. I will be using the newest version available at this time which is the virtio-win-0.1.225-2.iso found here.

Instead of downloading the image to your PC, you can copy the download link and download it directly from your Proxmox server. You can find the ISO images page by heading to the ISO Images tab of the local storage.

You can see the options I chose for my Windows Server 2022 VM below. Because I want to convert this to a template later on, I chose the minimum amount of storage required which is 32 GB.

After creating the Virtual Machine, we have to add the VirtIO ISO so that we can load the drivers during the Windows installation process. You do this by going to the Hardware section, adding a CD/DVD Drive, and choosing the ISO image.

You'll then want to verify that the VM will boot off of the Windows ISO attached to it. You can change the boot order by going to the Options tab.

Now you are ready to start the VM. The installation process is similar to recent previous Windows installations. When choosing which OS to install, I choose the Standard Edition with Desktop Experience. The Desktop Experience will give you a GUI so you don't have to manage it via a CLI.

When you get to the step where you have to select a storage, you won't see any options until we load the appropriate driver. Choose Load Diver (Or type L) and then browse to the VirtIO drive > vioscsi > 2k22 > amd64 folder. Once you load that driver, you should see the drive as an option to install Windows Server 2022.

After the installation process is completed, you will be prompted to create a password. This password will need to be recreated after the template is created so don't worry about the complexity of it, as long as Windows accepts it as an acceptable password.

Once you're at the login screen, send the Control + Alt + Delete key combo via the Proxmox interface.

After logging in, install the VirtIO drivers by selecting the VirtIO image from Windows Explorer and run the virtio-win-guest-tools.exe file. If you run the .msi installer, you wont get all the drivers installed. Reboot the VM after the drivers are installed.

You can also choose to install updates to the VM at this time. This will save you resources as newly created machines will be up to date.

To properly convert the VM to a template, we have to run the sysprep utility to safely clone it so that when a machine is created from the template, it has its own unique identifiers.

To run the sysprep utility, I will run it as a command from the Run dialog screen. Enter the following command:

C:\Windows\System32\Sysprep\sysprep.exe /oobe /generalize /shutdown

Once the VM powers off, all that is left to do is to convert it to a template under Proxmox. I like to remove the mounted ISO images from the VM before doing so. That includes the VirtIO image and the Windows Server ISO.

Then convert it to a template and you're done!

Using a recursive DNS server will also provide some privacy features since instead of querying a public DNS server, the DNS server will request the IP address from the authoritative name server and cache the requests. Initial requests will take a bit longer but load times will decrease as the DNS server will cache request made. This prevents your ISP from building a profile based on your DNS requests (as you won't be using their DNS servers).

Additional benefits include lower response times for DNS queries and filtered DNS queries.

I deployed my DNS server using my Proxmox server with an Alpine Linux LXC container, AdGuard, Unbound, and Nginx Reverse Proxy.

To begin, I deployed an LXC container based on Alpine Linux on my Proxmox server. I choose Alpine Linux because it is a lightweight distribution of Linux. Once the LXC container is deployed, I added a non root user, installed OpenSSH to manage the container remotely, and disabled password based authentication (I am using key-based authentication).

The next step is to install the DNS server. I choose to install a DNS forwarder that are able to block ads from specified domain names. Two popular options are Pi-Hole and AdGuard Home. I used AdGuard Home for my DNS server. You can see the setup instructions to install AdGuard Home on Alpine Linux in a post I made found here.

After the initial setup of AdGuard Home was completed, I installed Unbound and then configured AdGuard Home with it.

Next, I added DNS rewrites to my AdGuard Home instance. You can choose any domain you would like to use here. For a local only domain name, I chose the .local extension. Because the .local extension is not a fully qualified domain name, any attempts to access it from outside my local network would not be resolved. The .local domain name is reserved by the IETF so that it can't be used as a top level domain^[1]. More information about the .local domain name can be found at the IETF RFC 6762 documentation found here.

Then, I added custom DNS entried on my Nginx Proxy Manger instance. I specified the IP address and port the web applications were hosted on, and choose a custom subdomain. The following screenshot shows a few of the proxied hosts added.

The next step is to generate a self-signed certificate so that the traffic is encrypted. Because I am using a .local domain name, getting an SSL certificate from LetsEncrypt is not possible as the internal applications are not publicly accessible.

To generate a self-signed certificate, I used openssl on a fresh LXC container.

First, I ran the following commands to generate the key and the certificate. I ran the following commands as root.

openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout ./nginx.key -out ./nginx.crt

The "Common Name" is the only required information as it is a self-signed certificate. I created a wildcard certificate with the domain name *.sanchez.local.

Then I needed to access these files to upload them to Nginx Proxy Manger. I setup a quick web server by running the following command.

python3 -m http.server 80

The web server can be reached via its IP address. I downloaded the two files and uploaded them to Nginx Proxy Manager. You need to then add the self-signed SSL certificate and certificate key.

You will still receive an error that you have a self-signed certificate when you attempt to access self-hosted web applications via its URL. This can be removed by adding the certificate to the list of trusted certificates on the device accessing the web application.

Once the certificate is added to the list of trusted certificates, you will no longer recive the error and you can access your self-hosted applications securely!

Reference

[1]“.local,” Wikipedia, Jan. 30, 2021. https://en.wikipedia.org/wiki/.local

Manual Installation

1. Head on over to the rmyeleases page for the AdGuard Home over on GitHub.
2. Download the release for your architecture. You can find out which architecture you are on by running the command uname -m. I download it using wget to my home directory.
3. Extract the folder to the /opt/ directory. You can do this by running the following command.

doas tar -xvf AdGuardHome*.tar.gz -C /opt/

4.  Create a file  /etc/init.d/AdGuardHome. Change the file permissions to 755 afterwards by running the following command.

doas chmod 755 /etc/init.d/AdGuardHome

#!/sbin/openrc-run

description="AdGuard Home"

pidfile="/run/$RC_SVCNAME.pid"
command="/opt/AdGuardHome/AdGuardHome"
command_args="-s run"
command_background=true

extra_commands="checkconfig"

depend() {
  need net
  provide dns
  after firewall
}

checkconfig() {
  "$command" --check-config || return 1
}

stop() {
  if [ "${RC_CMD}" = "restart" ] ; then
    checkconfig || return 1
  fi

  ebegin "Stopping $RC_SVCNAME"
  start-stop-daemon --stop --exec "$command" \
    --pidfile "$pidfile" --quiet
  eend $?
}

Tip: The files in the /etc/init.d/ directory have the same file permissions. A quick way to get the octal file permissions is by running the stat command. You can get the file permissions for the files by running the following command.

stat -c '%a' /etc/init.d/*

5. Enable the service by running doas rc-update add AdGuardHome

6. Start the service by running doas rc-service AdGuardHome start

AdGuardHome should be running now and you can configure it by accessing it via its IP address on port 3000.

Install with a script

I created a script and added it to my GitHub repository. The repository and instructions can be found here.

For this demonstration, I installed MegaCMD on the server that I want to backup data from. Afterwards, I setup a Cron Job to automatically backup data to my Mega account.

First, I installed MegaCMD and logged in using the non-interactive command mega-login. I logged in so I do not need to include my credentials in the script.

mega-login email@domain.com password

NOTE: If you have 2 factor authentication on your account, append the --auth-code= to the end of mega-login command.

Then I choose what directory I wanted to backup to my Mega Account and added it to a script that will run at the specified time I set using a Cron Job.

The script is below. I added a curl command to notify me when the script was executed.  curl will attempt to GET response from my n8n instance, which will then execute a workflow that will notify my Discord and Mattermost server.  

1. Create the script with nano, I made a directory called scripts to store all my scripts.

mkdir ~/scripts && cd ~/scripts

nano mega-backup.sh

#!/bin/bash
# Select items to backup
mega-put -c /home/angel/backup2mega/ /linux_backup/
# Optional - Use curl to notify me when the script is executed
curl https://n8n.mydomain.com/webhook-uuid

2. Make the script executable:

chmod +x ~/scripts/mega-backup-script.sh

3. Add it to Cron and choose how often it is executed.

crontab -e

0 0 * * * sh /home/angel/scripts/mega-backup.sh

To know when it was executed, you can view the cron logs located at var/log/cron

sudo cat /var/log/cron | grep -e 'mega-backup' | less