dave/site
1
0
Fork 0
mirror of https://github.com/davegallant/davegallant.github.io.git synced 2025-08-09 10:02:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: e3bdcacacb702e92cdcbfdb8bd63a991c8df7b27

Browse Source
This commit is contained in:
davegallant
2025-04-18 03:27:17 +00:00
parent e02dc11c43
commit 4ba34a84cb
82 changed files with 82 additions and 82 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
js/flexsearch.7a0c7464ebee46a304acc1bfc848311b7ee05e6ceb517883d37c0a7c1fd2b5a772b474dc4582d44d88946b0044fc9903f5ca63b7a4d97701958db416989b2624.js → js/flexsearch.a07d618c9a634fc44af47d760ab314f159d1443da94f0fdac72198ba25fb62e4e21e3bac91070a6023e1f164fb446a6135280c54758d92f36d2eeaacbc626ede.js
View File

@@ -3,7 +3,7 @@
The only app I’ve needed to install has been the Tailscale app which has enabled me to access the TrueNAS Web UI from anywhere. I’ve setup a few datasets and NFS shares to store various backups and the rest of the periodic backups have routinely been working without a hitch. Since my homelab is becoming more of a vital piece of infrastructure for my daily needs, I wanted to ensure that these datasets had Cloud Sync Tasks setup for offsite backups. These encrypted backups are mostly being stored in places such as Google Drive and other blob storage providers.
More recently, to reduce cloud costs, I’ve setup some a small node at another physical location and installed both tailscale and sftpgo on it to facilitate these offsite backups. After setting up the infrastructure and adding a Cloud Sync Task in TrueNAS Scale to replicate these backups offsite to sftpgo, I noticed that Tailscale’s Magic DNS was not working, nor was the tailscale IPv4 address.
After reading the Tailscale docs , it became clear that the Userspace box had to be unchecked in the Tailscale app settings. This is because the Tailscale app is running within a docker container on the TrueNAS SCALE VM. After unchecking the Userspace box, I was able to verify that the Backup Credentials created for sftpgo worked when specifying the host as a tailscale IPv4 address. This was probably good enough since tailscale IPs won’t change unless the node is re-registered, but I figured setting up MagicDNS would be a bit more portable.
To get MagicDNS working, I went to Network > Global Configuration and set Nameserver 1 to 100.100.100.100. After this, I was able to specify the FQDN in the Backup Credentials and the Cloud Sync Tasks started.
To get MagicDNS working, I went to Network > Global Configuration and set “Nameserver 1” to 100.100.100.100. After this, I was able to specify the FQDN in the Backup Credentials and the Cloud Sync Tasks started.
`}).add({id:1,href:"/blog/opting-out-of-haveibeenpwned/",title:"Opting out of haveibeenpwned",description:`Data breaches are a concern for anyone trying to live a life of relative privacy. Last month, PowerSchool informed its customers that hackers stole data of 62 million students. This may not have impacted you, but unless you have been practicing Extreme Privacy techniques for decades, you likely have been impacted by a data breach in the past.
`,content:`Data breaches are a concern for anyone trying to live a life of relative privacy. Last month, PowerSchool informed its customers that hackers stole data of 62 million students. This may not have impacted you, but unless you have been practicing Extreme Privacy techniques for decades, you likely have been impacted by a data breach in the past.
Understanding Data Breaches# Data breaches occur when unauthorized individuals gain access to sensitive information (names, addresses, emails, phone numbers among other details). If the breach is substantial enough, the raw data is likely to make it into the hands of data brokers that will collect, aggregate, and sell the information on the dark web.