JonathanM

Probably not relevant to your specific issue, but those IP's are not meant for internal use, they belong to the DOD. https://www.whois.com/whois/192.100.100.5 You need to use IP's meant for internal networks. https://en.wikipedia.org/wiki/Private_network

Icecast + Mopidy is one option. Kind of a pain to set up, and it hasn't been very reliable with large playlists.

Unraid is designed around using eth0, it's assumed you will assign eth0 to the primary NIC.

What size are you specifying in the vdisk field? Post a screenshot.

It's to share information between containers, like VPN state and such.

Typically that means the vpn wasn't successfully negotiated, it's a safety feature to keep you from thinking everything is working when it's not. Take a look at the log files to see where it's getting hung up.

For THIS specific container, just keep walking the tag versions forward. I don't know how many you can jump, sometimes even point updates are needed for major versions to work. Other containers may handle this differently.

On a managed office365 account, app passwords can be enabled and work fine. I have no clue whether app passwords are available with free accounts.

Another option, probably quicker than going to the array and back, is to create another single device pool with the new drive, and copy directly from drive to drive. After the copy is verified, rename both pools, giving the new pool the correct name after renaming the old pool.

I very successfully use UrBackup. Does both versioned file backups and full images if desired. I've done both image restores and selective folder recoveries over WAN from my remotely located Unraid server hosting the UrBackup container.

Only if you are willing to buy an extra license. The *.key is the license file, and it's bound to one flash drive at a time. Realistically, the time it takes to transfer a key to a new USB is minimal, it's automated so as long as you have internet, it's just a couple clicks. The only caveat is the automated transfer is once a year to prevent abuse. Contacting support to get a key transfer sooner than a year is pretty painless, just need to tell them what happened and they'll get you sorted.

Look in previous apps, if it's in there you can reinstall, set the tag to linuxserver/nextcloud:28.0.10-previous and see what happens. See here for a list of valid tags. https://hub.docker.com/r/linuxserver/nextcloud/tags

Maybe this? I use nextcloud, but that's probably not what you are after.

Not sure what you mean by suggested command, and I'm not saying to run anything in proxmox. Whatever OS you are running as a guest, use the urbackup client inside it, just like you would any other computer. There is a urbackup host container that I run on Unraid to receive those backups.

Talk about counter productive. If it wasn't under warranty I would have recommended experimental surgery, depending on the user's level of hardware tech experience.

That's interesting. I'm seeing replacement batteries for sale, as well as instructions on how to change them.

Try using a standalone VNC viewer, use the server's IP address and port 5900 for the first VM, 5901 for the second one started simultaneously, etc. If that works, then the issue is probably your web browser. As you alluded to, the VNC built in to the server is really only for setting up the VM, or managing things before the guest OS is able to start a nomachine or RDP session. It's not meant to be used as a daily driver interface, just management.

The price penalty for upgrading from a lower version to lifetime is currently less than $10, so I'd recommend buying whichever lower tier license works for you, run it as long as you want while you save for the upgrade. It's kind of like putting it on layaway and still be able to use the product.

That is exactly how I have mine set up. SWAG provides the reverse proxy to the UI, other required ports are forwarded through the firewall. I manage multiple WAN locations with this image. The set inform override is my FQDN.

I don't use NFS (not many do) but I think I remember you need the full path, not just the share. /mnt/user/data

Have you applied all the fixes here?

Yes, just more complicated. You would pretty much be doing a lot of this from scratch on the new array. That's the question I was trying to address.

https://docs.unraid.net/unraid-os/manual/storage-management/#upgrading-parity-disks https://docs.unraid.net/unraid-os/manual/storage-management/#replacing-disks

I'm just talking about the normal process of upgrading drives. Shut down, remove and replace with a larger drive, boot up, select larger drive in the GUI to replace the missing drive. You'd start with Parity1. After that completes, you would remove Parity2, start the array with it set to uninstalled, shut down and replace Disk1, rebuild, and continue until all the new drives are installed.