• 0 Posts
  • 63 Comments
Joined 2Y ago
cake
Cake day: Jun 09, 2023

help-circle
rss

You might consider asking this in the !homeassistant@lemmy.world community, too.


Getting feedback about this post being spam. The article details a legitimate integration for HomeAssistant. But, it seems contrary to what this community would value. Going to leave this post up, but suggest that OP consider moving it to one of the HomeAssistant communities. Everyone else: use the downvote arrow to judge the worthiness of the posting.



TL;DR: Op needs to sort out reverse proxy with SSL/TLS.


For troubleshooting, I would recommend you visit the Plex Discord/Matrix channels for real-time help. Additionally, !plex@lemmy.ca may prove helpful.


I’ll leave this for others to chime in. But you may find useful information in one of the homelab communities as well.


OP says the question has been answered. Locking the discussion so they don’t have to suffer through any more repeat information.


Not from iCloud, just from the phone’s local storage. So, to backup all of iCloud from the phone, those photos would have to be downloaded to the phone first.

Alternatively, you can download all the photos from iCloud to a computer, then upload those photos manually to the Immich web interface.


I have implemented what you’re looking for using Immich on my wife’s iPhone.

Immich backs up the “Recents” album - which means it backs up everything. What’s important to remember is that it backs it up, not syncs it. This allows me to delete photos from the iPhone and they stay in the Immich library. This is how I keep my wife’s phone from running out of storage.

Works well for us so far, even if I have to manually delete the photos off the phone from time to time.


In fairness, the lack of Enterprise OS connectivity is spelled out in the Pricing breakdown on their website.


While this post is in support of a self-hosting platform, the request itself is storage-related. I would recommend that you reach out to https://lemmy.world/c/zfs or https://discourse.practicalzfs.com.


The problem with managing replication outside of PVE is ‘what do you do when you have to move the VM/CT to another node?’ Are you going to move the conf file manually? It’s too much manual work.

Let PVE manage all of the replication. Use Sanoid for stuff that isn’t managed by Proxmox.


Home assistant integration could accomplish this for you. Not sure if it’s less work than regular mobile clients, though.


I think fans of Nix and NixOS would agree.


This is really more of a home networking issue than anything having to do with self-hosting. Please consider posting this in one of the many Lemmy home networking communities.


This is a question probably better-suited for one of the Proxmox communities. But, I’ll give it a try.

Regarding your concerns about new SSDs and old VM configs: why not upgrade to PVE8 on the existing hardware? This would seem to mitigate your concerns about PVE8 restoring VMs from a PVE7 system. Still, I wouldn’t expect it to be a problem either way.

Not sure about your TrueNAS question. I wouldn’t expect any issues unless a PVE8 installs brings with it a kernel driver change that is relevant to hardware.

Finally, there are several config files that would be good to capture for backup. Proxmox itself doesn’t have a quick list, but this link has one that looks about right: https://www.hungred.com/how-to/list-of-proxmox-important-configuration-files-directory/



Nextcloud Photos performs okay, but the interface is very ‘meh’. Plus, the mobile client’s sync is a little unstable. On iOS, there’s no background sync at all.


This seems the correct advice. If the container is on the same host as the data, there’s no need to access the data via Samba. In fact, it’s likely the container doesn’t contain the samba client needed for such connectivity.

Assuming TrueNAS allows the containers to see local data, a bind mount is the way to go.


This is good stuff. Has it been posted to the project’s GitHub (issue, discussion, etc.)?


Have you considered searching the GitHub issues?


IMO, this is a discussion that should be taking place on the project’s GitHub. I’m going to lock the comments so I don’t get any more reports about commenters’ behavior.


I imagine this would be up to the application. What you’re describing would been seen by the OS as the device becoming unavailable. That won’t really affect the OS. But, it could cause problems with the drivers and/or applications that are expecting the device to be available. The effect could range from “hm, the GPU isn’t responding, oh well” to a kernel panic.


I still use the label ‘homelab’ for everything in my house, including the production services. It’s just a convenient term and not something I’ve seen anyone split hairs about until now.

if nothing on it is permanent. You can have a home lab where the things you’re testing are self hosted apps. But if the server in question is meant to be permanent, like if you’re backing up the data on it, or you’ve got it on a UPS you make sure it stays available, or you would be upset if somebody came by and accidentally unplugged it during the day, it’s not a home lab.

A home lab is an unimportant, transient environment me


Tailscale is an overlay network. It will use whatever networking is available. If only one of those NICs is a gateway, then that’s what will be used to reach remote Tailnet resources.


Leaving this post here since it’s an interesting project to keep an eye on, but the conversation isn’t constructive. So, locking the comments.


Would they have to be VLAN aware if the switch port was already tagged AND if OP doesn’t care to consider untagged traffic ?


With the disclaimer that Proxmox has nothing to do with this question, I’m forced to assume this is just a networking issue that happens to use OPNsense as the router. Because of that, I must advise that you seek help from a networking-focused community. There’s no clear link to self-hosting in this post, which is required per Rule 3.


If the connections are already tagged as you come into the Proxmox server, then you need only to create interfaces for them in Proxmox (vmbr1, vmbr2, etc). EDIT: if you’re doing PCI passthrough of the physical NICs, ignore this step.

Then, in OPNsense, you just adding the individual interfaces. No need to assign a VLAN inside OPnsense because the traffic is already tagged on the network (per your earlier statement).

Whether or not the managed switch that has tagged each port is also providing VLAN isolation, you’ll simply use the OPNsense firewall to provide isolation, which it does by default. You’ll use it to allow the connections access to the fiber WAN gateway.


You’ll need to be far more descriptive than “I can’t get it to work.” I can almost guarantee you that Fedora is not the problem.



I’m a little lost on how a container would mess with your boot loader (GRUB). That aside, most of what you’re explaining to do with the containers. These are OS-agnostic. What do the container logs tell you?


This is really more of a home networking issue than anything having to do with self-hosting, especially since it centers on a consumer router. Please consider posting this in one of the many Lemmy home networking communities.


I’m going to allow this post, despite its age and likely obsolescence. I encourage community members to use up and down votes to judge its value to the community.


I am with you on the advantages of running it in a VM. The isolation a VM provides is really nice. Snapshots FTW.


That’s not a definitive support statement about Docker being unsupported. In fact, even in the Admin Guide, it only provides recommendations. The comment I replied said Docker is unsupported by Proxmox. I maintain that there is no such statement from Proxmox.


Proxmox is Debian at its core, which is supported by Docker. There’s no good reason to not run Docker on the bare metal in a homelab. I’d be curious to know what statement Proxmox has made about supporting Docker. I’ve found nothing.


This community is not unmoderated, nor is it micromanaged. As has been shared in these comments, some members of this community appreciate these new release postings. If you don’t, ignore/hide it and/or downvote it and move on.


Check the ZFS pool status. You could lots of errors that ZFS is correcting.


Quick and easy fix attempt would be to replace the HDD with an SSD. As others have said, the drive may just be failing. Replacing with an SSD would not only get rid of the suspect hardware, but would be an upgrade to boot. You can clone the drive, or just start fresh with the backups you have.