Fusion13combined Publicnet Install [updated]

This guide is written for system administrators, DevOps engineers, and advanced homelab users dealing with modular software deployments or complex network-attached storage (NAS)/virtualization environments.

Review — Fusion13Combined PublicNet Install

Summary

Part 6: Security Hardening for Production Use

If you intend to keep your combined installation running 24/7 with public access, apply these hardening steps immediately: fusion13combined publicnet install

# Check service status
systemctl status fusion13-core
systemctl status fusion13-web

You will see a list of available repositories. Select the "Fusion 13 public repository" option and press Enter.


Updates: OTA updates via signed packages; supports staging channels for testing.
Authentication: Local accounts, LDAP/Radius integration, and optional 2FA for UI.
Auditing: System logs, configurable syslog forwarding, and audit trail for config changes.
Known issues: Past CVEs addressed; keep up to date and enable automatic security updates.

3. Network Topology: Combined PublicNet
In a "Combined" scenario, the cabling is simplified but the logical configuration becomes more complex. This guide is written for system administrators, DevOps
Step 10: Login to Fusion 13