Adrian Lee

My server was recently compromised via the latest vulnerability. Fortunately, the damage wasn’t too severe. Since my server must remain publicly accessible, it can’t be hidden behind a VPN—I can only minimize its exposure as much as possible while ensuring my backup and recovery processes are rock-solid. I’ve configured the firewall to allow only essential ports, restricted SSH access to key-based authentication, enabled automatic installation of security updates, and set up daily backups, one of which is synchronized to an off-site location. Some have suggested treating public-facing machines as if they’ve already been compromised by default. I agree with this approach, and it’s exactly what I plan to do next.

The ability to set up a whitelist of channels and playlists based on user preferences sounds great—it’s perfect for sharing with family or friends. By the way, does the small instance you mentioned with 2 GB RAM include components such as the database, cache, downloads, storage, and media proxy? If I want to use a full instance, what server configuration would you recommend?