🇨🇦

  • 3 Posts
  • 65 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle







  • BorgBackup creates compressed and de-duplicated backups, splitting data into chunks then only keeping unique chunks + a list of files those chunks belong too.

    I’ve currently got around 470gb being backed up; compression brings that down to 320gb, then after de-duplication that’s down closer to 70gb. (there’s a lot of media metadata in there, results will vary)

    17 backups going back 6 months: 8.10 TB original > 5.62 TB compressed > 326.55 GB final backup data stored on disk

    /edit this thread is a week old… It showed up at the top of my ‘new’ feed…? Odd.



  • Plus Foldersync is way harder on battery, I’ve experimented a lot.

    This is very configuration dependant. With an aggressive schedule checking a large number of files, it certainly can use a lot of battery; but I’ve had it setup to sync my entire device to my server a couple times a day, while also monitoring/syncing images immediately on creation/change. It doesn’t even register on androids battery usage monitor as it uses so little power.

    Anyway; just listing an option for people to look at



  • More than any other piece of self-hosted software: backups are important if you’re going to host a password manager.

    I have Borg automatically backing up most of the data on my server, but around once every 3 months or so, I take a backup of Vaultwardens data and put it on an external drive.

    As long as you can keep up with that, or a similar process; there’s little concern to me about screwing things up. I’m constantly making tweaks and changes to my server setup, but, should I royally fuck up and say, corrupt all my data somehow: I’ve got a separate backup of the absolutely critical stuff and can easily rebuild.

    But, even with the server destroyed and all backups lost, as long as you still have a device that’s previously logged into your password manager; you can unlock it and export the passwords to manually recover.





  • Thanks. That seems to be a similar, but slightly different error. I think the below may apply though.

    I believe I’ve tracked down more of my issue, but fixing it is going to be a hassle:

    When cloudflare proxying is enabled, there are 3 DNS records involved; A record with cloudflares ipv4, AAAA record with cloudflares IPV6, and the key to this puzzle: an HTTPS record with cloudflares ech/https config.

    With pihole I can set DNS records for A/AAAA, but I have no way of blocking/setting the HTTPS record so it gets through from cloudflare.

    The LAN A/AAAA records don’t match the HTTPS record from cloudflare, so browsers freak out.

    Once I disabled cloudflares proxying, I no longer get HTTPS records returned and all works as intended.

    I’ll either have to keep cloudflare proxying disabled, or switch pihole out for a more comprehensive DNS solution so I can set/block HTTPS records :(

    Thank you @bobslaede@feddit.dk for pointing me in the right direction.


  • That unfortunately did not work. I am only getting the ipv4 address now, but I still get the same ECH error in chrome 1/5 tries.

    Firefox now changed errors from ‘invalid certificate’ to ‘connection is insecure but this site has HSTS’ (true). Still wont show the cert or provide any further info. (forgot to grab a screenshot before the below ‘solution’)

    I’m really annoyed at this point and have just disabled cloudflare proxying for this service. That seems to have sorted it for all browsers. I may look further later, I may just say fuck it and leave it like this. Gotta walk away for a bit.