• 0 Posts
  • 37 Comments
Joined 11 months ago
cake
Cake day: March 8th, 2025

help-circle





  • You are like hitting a data protection layer. Basically your corpo does not want you to exfiltrate data (accidentally nor maliciously).

    Your options

    • host it on a public endpoint so it looks like a legitimate website that you might need for your work. Chances are this will get blocked eventually.
    • put you corpo laptop in separate vlan and don’t mix work and personal stuff. If you need something from your local, open it in your laptop. Everything on your work laptop is monitored.












  • If my lab goes down, it sucks, but that’s it. I have no critical service running there.

    I have some recoverability, but it requires for the main router to run. If it isn’t running it’s either a HW failure, which I will not fix remotely anyway or power is down. In which case, not much I can do about it neither.

    I have router with OpenWRT with Wireguard and main server (NUC) on a smart plug. If the router runs and server is mishaving to the point where I cannot reboot it, I can power cycle it via the smart plug connected to the router.

    You mentioned your brother lives 30mins away - well put some tiny server in his house. Having everything at your home is not build for redundancy at all. That’s just the risk management, if you absolutely need access to your server, then 1 site is not going to cut it.


  • I have been on the same boat a while ago. Of course it was a deployment that caught on and was serving longer than expected.

    I don’t recall how many versions I skipped exactly (1-2 years worth of updates). Of course no backups set what so ever.

    I looked at change log of I need something specific, there were changes in docker compose file. Did my best effort to make it succeed.

    My worst case scenario was that I will have to import everything again and made sure I have all my labels, tags and settings backed up.

    Nowadays I’ll just snapshot the whole VM in Proxmox.