tvcvt

@tvcvt@lemmy.ml

This is a remote user, information on this page may be incomplete. View at Source ↗

⁨Comment⁩ on ⁨Proxmox Backup Server: Bare Metal vs. Privileged LXC vs. VM?⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:
Sure thing—autofs is a pretty cool utility and it works with SMB as well.

If the storage isn’t present for PBS, the backup would fail. There are files inside the directory that PBS will notice are missing.

Mounting the NFS export in the PVE host is the simplest way to get shared storage into an LXC container. You have to fight apparmor to mount NFS or SMB inside the container directly.
⁨Comment⁩ on ⁨Proxmox Backup Server: Bare Metal vs. Privileged LXC vs. VM?⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:
No, I used an unprivileged container and I set the permissions on the NFS server to accommodate that.
⁨Comment⁩ on ⁨Technitium DNS v14 is released with support for clustering⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:
I use it like I might use unbound or dnsmasq, but I’d think of it more like bind. It’s can be used as a recursive or authoritative resolver. It supports all kinds of protocols (DOT, DOH, DNSSEC, etc). Handles zone transfers easily. It’s pretty slick. Definitely worth a look
⁨Comment⁩ on ⁨Proxmox Backup Server: Bare Metal vs. Privileged LXC vs. VM?⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:
If you’d like some separation, one option is to create a VM on TrueNAS for PBS that connects to an NFS export where all the data would be stored.

What I did in this scenario is an LXC container running PBS, which uses a bindmount for storage. That bindmount is populated via an NFS export from my NAS, mounted on the PVE host using autofs so that if it disconnects, it will reconnect as soon as it can.
⁨Comment⁩ on ⁨Technitium DNS v14 is released with support for clustering⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:
Technetium is a recursive DNS resolver with a nice web UI. If you’re familiar with PiHole or AdGuard Home, you can think of it in that genre, but much more full-featured.
⁨Comment⁩ on ⁨self hosted calendar + events management and booking platform which has embaddable widgets for websites?⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:
If you haven’t already, check out the Awesome Open Source page’s Booking and Scheduling section.
⁨Comment⁩ on ⁨Immich camera lens info⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:
That metadata is written into the photo by the camera, so Immich may not be able to accommodate this easily. Not sure about Canon specifically, but my Nikon cameras have a memory bank for manual focus lenses. Might be worth checking through your menus.
⁨Comment⁩ on ⁨Why do I need a domain to access my Funkwhale library but not SyncThing?⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:
The two pieces of software have very different topologies.

In very broad strokes: Something like FunkWhale uses a server-client model. To get to it, you connect to it remotely and you need some way to get there. By contrast Syncthing behaves as a mesh of nodes. Each node connects directly to the other nodes and the syncthing project folks host relays that help introduce the nodes to one another and penetrate NAT.

No, you may not need a paid domain to use your self-hosted FunkWhale server (I haven’t dabbled with that service in particular). There are a few options.
1. You could probably use the direct public IP address or alternatively
2. Use a dynamic DNS provider (like afraid.org) to resolve your IP address
3. Use a VPN on all of your clients and use local DNS to resolve your FunkWhale server’s local IP address.
These all assume that you have a public IP address on your router and not one that’s being NAT-ed by your ISP.

Again, these are very broad strokes, but hopefully it helps point your in a direction for some research.
⁨Comment⁩ on ⁨What's the real danger of opening ports?⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:
There’s definitely nothing magic about ports 443 and 80. The risk is always that the underlying service will provide a vulnerability through which attackers could find a way. Any port presents an opportunity for attack; the security of the service is the is what makes it safe or not.

I’d argue that long tested services like ssh, absent misconfiguration, are at least as safe as most reverse proxies. That doesn’t mean to say that people won’t try to break in via port 22. They sure will—they try on web ports too.
⁨Comment⁩ on ⁨[Question] Visual feedback of my Linux homelab setup/system?⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:
I’m not sure if this what you’re after, but it sounded to me that you were describing monitoring. Might be worth your checking out librenms or zabbix or checkmk. Those would give you a good overview of the health of your stuff and keep track of what’s where.
⁨Comment⁩ on ⁨Proxmox Rclone Mounts in LXC⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:
I’m not familiar with Zurg, but the WebDAV connection makes me recall: doesn’t LXC require that the FUSE kernel module be loaded in order to use WebDAV?

I’ve also seen it recommended that WebDAV be setup on the host and then the mount points bind mounted into the container. Not sure if any of that helps, but maybe it’ll lead you somewhere.
⁨Comment⁩ on ⁨What I host myself⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:
That’s a great tip. I’d completely forgot you can use telnet for that. Thanks!
⁨Comment⁩ on ⁨What I host myself⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:
Thanks for the response. I really should just dive in, but I’ve got this nagging fear that I’m going to forget about some DNS record that will bork my entire mail service. It good to hear about some working instances that people are happy with.
⁨Comment⁩ on ⁨Getting Started with Proxmox⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:
Tainted in that the kernel and ZFS have different licenses. Not a functional impairment. I have no way to check to check a system not using ZFS. For my use case, Debian plus ZFS are PVE’s principal features.
⁨Comment⁩ on ⁨What is the current state of Matrix?⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:
I have synapse server running in docker on a VPS and it’s been pretty reliable. At my office I use it as sort of a self-hosted Slack replacement. For our use case, I don’t have federation enabled, so no experience on that front. It’s a small office and everyone here uses either Element or FuzzyChat on desktop and mobile. I’ve got SSO set up with Authentik and that’s worked very well. Happy to share some configs if that would be useful.
⁨Comment⁩ on ⁨What I host myself⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:
Have you by any chance documented your PMG set up? I’m also a very happy Mailcow user and spinning up PMG is something I’ve been meaning to tackle for years so I can implement archiving with mailpiler, but I’ve never really wrapped my head around how everything fits together.
⁨Comment⁩ on ⁨Getting Started with Proxmox⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:
Ceph isn’t installed by default (at least it hasn’t been any time I’ve set up PVE) and there’s no need to use ZFS if you don’t want to. It’s available, but you can go right ahead and install the system on LVM instead.
⁨Comment⁩ on ⁨Fresh Proxmox install w/ full disk encryption—so install Debian first, then Proxmox on top?⁩ ⁨⁨5⁩ ⁨months⁩ ago⁩:
I think you can do the same with LUKS (cyberciti.biz/…/cryptsetup-add-enable-luks-disk-e…) if that’s your preferred route.
⁨Comment⁩ on ⁨Fresh Proxmox install w/ full disk encryption—so install Debian first, then Proxmox on top?⁩ ⁨⁨5⁩ ⁨months⁩ ago⁩:
Another idea for you: if you use ZFS for the install, check Debian directions on OpenZFS or zfsbootmenu and you’ll get directions for an encrypted installation. You’ll be able to specify the path to a key file, which you can keep on a thumb drive. When the machine boots up, it’ll see the thumb drive and decrypt the zpool automatically; yank the thumb drive and it won’t (backup the key of course).
⁨Comment⁩ on ⁨First file server⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:
The answers for this will vary widely, but the thing I think many people overlook when planning out expenses is a plan to back up the data. Having the file server is great, but start planning now for what to do when it breaks. Where will backup copies of your data live and how will you restore it?

As to the server itself, the hardware completely depends on your desires. Some like second hand enterprise gear; others prefer purpose-made home NAS devices or a DIY rig. On the software side my thought is keep it simple if you’re starting up. There are good readymade options (TrueNAS, XigmaNAS, openmediavault, unraid, etc). They’re all great and they help get up and running quickly. They also have a lot of tempting knobs to turn that can cause unexpected problems if you don’t fully understand them.

To my mind file servers have to be reliable above all else, so I’d avoid running anything besides file sharing on your server until it’s running like a top and then only add more layers one at a time.

Sorry for all the philosophy, but I really do think this is a common stumbling block for people getting started.
⁨Comment⁩ on ⁨If Nothing is Exposed, Am I Safe?⁩ ⁨⁨7⁩ ⁨months⁩ ago⁩:
You ever see those Wired videos where they talk about a concept on five different levels ranging from beginner to expert?

The first level answer is likely that, yes, you’re reasonably secure in your current setup. That’s true, but it’s also really simplified and it skips a lot of important considerations. (For example, “secure against what?”) One of the first big realizations that hit me after I’d been running servers for a little while and trying to chase security is the idea of a threat model. What protects me from a script kiddie trying to break into one of my web servers won’t do much for me against a phishing attack.

The more you do this, though, the more I think you’ll realize that security is more of a process than an actual state you can attain.

I think it sounds like you’re doing a good job moving cautiously and picking up things at each step. If the next step is remote access, you’ve got a pretty good situation for a mesh VPN like Tailscale or Netbird or ZeroTier. They’ll help you deal with the CGNAT and each one gives you a decent growth path where you can start out with a free tier and if you need it in the future, either buy into the product or self host it.
⁨Comment⁩ on ⁨Best Back Up Solution For Multiple Servers⁩ ⁨⁨7⁩ ⁨months⁩ ago⁩:
It sure will handle a remote VPS, it’s just not as automatic to set up as it is with PVE.

I put this off for a long time, but I finally did it this weekend.

Basically, you install the proxmox-backup-client utility and then run it via cron or a systemd timerto do the backup however often you want.

You’re responsible for getting the VPS to communicate with your backup server (like pretty much any self-hosted service), so some sort of VPN between them would be good. I used NetBird for that part and I have a policy that allows access from the client to PBS only on TCP port 8007.
⁨Comment⁩ on ⁨Best Back Up Solution For Multiple Servers⁩ ⁨⁨7⁩ ⁨months⁩ ago⁩:
I’ve been quite happy with Proxmox Backup Server. I’ve had it running for years and it’s been pretty solid for all my VMs/containers. There’s also a bare metal client, which I’m adding to a couple cloud VPS machines this weekend. We’ll see how that goes.

Also, since it’s just Debian under the hood, I also use the PBS host as a replication target for my ZFS datasets via sanoid/syncoid.
⁨Comment⁩ on ⁨How to update Immich now that I am way behind?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:
I just had to do this. Don’t skip the release notes. They’re really good at highlighting potential pitfalls, just scroll back through and look for the heading “Breaking Changes.”

In my case there were a few, but they were only for API calls I’m not using, so I just did the update in one go and it worked out great. (Of course, I made sure to take a backup first.)
⁨Comment⁩ on ⁨What do people use for a shelf-stable backup⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:
This was a recent point of discussion on the 2.5 Admins podcast (2.5admins.com/2-5-admins-228/). Some good discussion on there.

My own thought is the best way to handle your family-member-finding-your-old-photos problem is the analog way: make some prints. It’s absolutely idiot proof, the methodology of keeping paper goods is well understood, and the technology is platform independent.