If you’re talking about network attached storage, you won’t see much benefit from SSDs since the network transfer speeds are the bottleneck. Example: SSD transfer rate of 3000MB/s, but your wifi may only go 500MB/s, or Ethernet 1000MB/s.

You’re better off just going HDD on a NAS, at least for the $/Tb. Just start with two disks in RAID1. More than good enough for what you’re trying to do.

Sorry, I missed something. SSDs setup for what?

Certainly don’t need the Synology, just an option if you want things in a clean and tidy package with a UI to manage some things.

You’re describing a number of different things here, but you’re thinking about it in an overly complex manner.

You need a centralized file store like a NAS, and a mountable workspace from said NAS that will mount to each machine, then you need some sort of Domain Directory service to join it all together. If you want the different desktops settings and stuff synced, you can achieve this with that setup, or you can go a step deeper and use an immutable distro of some sort, and commit and keep the same revision from one machine checked out on all your other machines (works kinda like a fit repo). This will likely present issues if it’s not all the same hardware though, so I would go with probably just keeping it simple if you go that route.

User experience example would like this:

• setup all your files on your centralized storage
• join one machine to your domain (you can use LDAP, Samba+LDAP, NFSv4 domains…whatever)
• login and have it pull your userinfo from the domain
• your network mounts and user preferences will be pulled down and out in place

Obviously this is simplified for the purposes of this post, but it should give you a direction to start investigating. Simplest path you can test this with is probably Samba, but it will be fairly limited and just serve as a starting point.

Edit: if these concepts are a bit much for you, maybe consider getting a NAS with a good UI to make managing it much simpler. Synology has this baked in already, and I think Qnap does as well: https://www.synology.com/en-global/dsm/feature/active_directory

Exactly

NAS: little box of disks that sits on a shelf or rack Media Server: just something that makes media files available for whatever. Could be a network drive you attach to from your desktop, or a streaming server for music or video RAID: mirrored drives. If you have two drives in a NAS, you can mirror them with RAID1 so if one fails, you can replace it with the data on the second drive UPS: just a battery backup device you plug things into

So these are just various things you can combine to make a larger system. You don’t NEED a NAS for instance, you can just have a machine that serves files to your network. You don’t NEED a media server unless you want those features.

You pick and choose what you want to do, then piece all these things together to make a larger functional system that does what you want.

Maybe a better approtis asking here what you actually want, and then people can suggest solutions for that.

Yeah, and people ask about suicide on the Internet as well, but I would never help them.

Big nope. It’s not a technical hurdle, it’s a viability problem. Just search on why you should never host your own SMTP service.

Networking isn’t specific to Linux. It’s just networking. Nginx configs work the same on every OS.

No special knowledge needed except the very basic ability to understand and run commands from documentation.

Sure…so I’m confused why you’re bringing XFS to the conversation.

They literally said it was a btrfs array.

If it mounts, and you can read it, then it’s fine and you just need Proxmox to pay attention to it. Works like any Linux install and you need to add the disk into fstab BEFORE Proxmox starts up. Here’s a thread: https://forum.proxmox.com/threads/how-to-mount-existing-disk-to-storage.66559/

…why? He has a functioning array already. It mounts and is readable.

Your ISP doesn’t allow port or 443. Change those to something else, or reverse proxy 80 to 8080 or whatever.

Then you need to go looking in your logs. You mentioned nginx, so go check those logs, or the WordPress logs and see if you can get any info. Wouldn’t hurt to also check your browser console output and see if there are any errors there when attempting to load the page.

I’m missing something in your post then.

Are you asking exactly what the mechanism for getting a direct video stream from a camera is? Depends on your camera, but it’s almost always RTSP.

Are you sure your camera even supports streaming off camera? You can try opening an RTSP stream from the camera with VLC as a quick and simple test to find out.

You can either connect whatever the WordPress host is on to your VPN and access the camera that way, or create a reverse proxy off of something connecting to the VPN. There’s no other way to transport a live video stream like this between points except by direct connection though.

As fast as it gets to the CPU. That should be pretty obvious.

AMD APU uses whatever system RAM is as VRAM, so…yeah. NPU as well.