Root server check
Root server check
Section titled “Root server check”rConfig runs as the web user, so some settings are out of its reach: sshd_config, sudo rules, Apache vhosts, redis.conf, pg_hba.conf and PHP-FPM pools are readable by root only. From V8.5.0, rconfig-server-check.sh reviews them as root and writes its results where Security Center and rconfig:security-check pick them up. Its findings show with a server icon and IDs starting server..
# Report only. Writes /var/lib/rconfig/server-check.jsonsudo bash /var/www/html/rconfig8/resources/scripts/rconfig-server-check.sh
# Also apply the safe fixessudo bash /var/www/html/rconfig8/resources/scripts/rconfig-server-check.sh --fixRun it after installing, after changing the server, and at least weekly. os.server_check_script warns when its results are more than 7 days old.
What it checks
Section titled “What it checks”SSH root sign-in
Section titled “SSH root sign-in”server.os.sshd_root_login. Reads the effective sshd -T settings. PermitRootLogin yes fails; prohibit-password warns. Set PermitRootLogin no and sign in as a named user with sudo.
SSH password sign-in
Section titled “SSH password sign-in”server.os.sshd_password_auth. PasswordAuthentication yes warns, because SSH passwords can be guessed. Use SSH keys, then set PasswordAuthentication no.
sudo and the web user
Section titled “sudo and the web user”server.os.sudoers_web_user. Fails if any sudo rule gives the web user NOPASSWD: ALL. rConfig needs only its own narrow helper rules (/etc/sudoers.d/rconfig-xftp, /etc/sudoers.d/rconfig-vector-hub).
sudo rule files
Section titled “sudo rule files”server.os.sudoers_perms. Every file in /etc/sudoers.d must be owned by root and not readable or writable by others (0440). --fix corrects the mode.
redis.conf
Section titled “redis.conf”server.redis.conf. Fails when Redis binds to every interface, warns when protected-mode is off. Use bind 127.0.0.1 -::1 and protected-mode yes.
pg_hba.conf
Section titled “pg_hba.conf”server.db.pg_hba. Fails on trust lines (no password at all) and warns on md5 or password. Use scram-sha-256.
MariaDB/MySQL anonymous accounts
Section titled “MariaDB/MySQL anonymous accounts”server.db.anonymous_users. Fails if anonymous accounts exist. Run mariadb-secure-installation.
PHP-FPM pools
Section titled “PHP-FPM pools”server.php.fpm_pool. Fails if a pool runs as root or has a world-writable socket.
.env permissions
Section titled “.env permissions”server.app.env_file_perms. Same as the app check, but as root it can also fix a .env the web user does not own.
World-writable files
Section titled “World-writable files”server.os.app_world_writable. Anything under the rConfig folder (except vendor and node_modules) that any local user can write. --fix removes the write bit.
OS security updates
Section titled “OS security updates”server.os.security_updates. Warns when dnf updateinfo or apt reports security fixes waiting to be installed.
Host firewall
Section titled “Host firewall”server.os.firewall. firewalld, ufw or an nftables ruleset must be active.
Apache
Section titled “Apache”The Apache rows (server.web.*, server.os.default_ssl_site, server.db.bind_address) come from rconfig-apache-check.sh, which looks at the default sites on ports 80 and 443, the stock ssl.conf site (the cause of rCFG-SA-2026-15), directory listings, dotfile access and the main DocumentRoot, then requests .env, storage and .git over HTTP and HTTPS to prove they are not served. See Apache hardening.