WireGuard – Allow Local Network

the logo of a VPN app named WireGuard, depicting a white dragon against a red background

And by Local Network, I mean here on my workstation, not at the peer or VPN docker/server/provider.

I am not very knowledgeable with VPNs but I got to learn something new and when I do, I make a note of it. The problem was that when I have my VPN active to poke things at home, I could not print documents at my workstation at work.

Googled a lot, trid a few things and then realised that adding IP addresses to AllowedIPs in the PEER section, adds an exception for an IP address on the server’s side, NOT my workstation.

“Ooooh, what does this checkmark do?”

Confusingly enough, WireGuard names things differently between the Windows and the iOS app. So here’s what you need to check to gain access to your workstation’s local network:

  1. Open the WireGuard control panel.
  2. Click once on the vpn you want to change
  3. Click the EDIT button on the bottom right
  4. iOS: UN-Tick the box on the bottom left that says: “Exclude private IPs”, then click SAVE
    Windows: UN-Tick the box on the bottom left that says: “Block untunneled traffic (kill-switch)”, then click SAVE

Yes ,this poses a security risc, so I made two VPN profiles. One with and one without so I can easily switch from one to the other.

Loading

Mastodon: Manual backups

This is an updated version (26-08-2024)

This manual is a transcript of the way that I have made a backup of my Mastodon instance. Please make sure you are careful and use your brain while following this manual.

Preparing the backup folder

  1. Log in as root
  2. cd /home/mastodon
  3. mkdir backups
  4. cd backups

Making the backups

  1. Database (three steps)
  2. #NOTE: You might need to elevate to ROOT first before entering the commands in this section below.
    su - mastodon
    cd /home/mastodon/backups
    pg_dump -U mastodon mastodon_production -F t > DATE_FILENAME.tar
    
    

    Example: pg_dump -U mastodon mastodon_production -F t > 2024-02-02-mastodon_production.tar

  3. Settings file (one step)
    cp /home/mastodon/live/.env.production /home/mastodon/backups/DATE_.env.production
    
    

    Example: cp /home/mastodon/live/.env.production /home/mastodon/backups/2024-02-02-.env.production

  4. Redis (two steps, perform as root)
    exit
    cp /var/lib/redis/dump.rdb /home/mastodon/backups/DATE_dump.rdb
    
    

    Example: cp /var/lib/redis/dump.rdb /home/mastodon/backups/2024-02-02-REDIS-dump.rdb

You can now check your backups folder to see if all three files are present. This is also a good moment to copy the backup files to another, safe, location.

If you wish to backup your assets like images and stuff (User-uploaded files), backup the folder named “public/system”. Keep in mind that this folder can be rather large. Actually, it can become rather massive.

Loading