🛠️Connection Issues After Server Reboot

After rebooting a server, it’s not uncommon to experience connection-related issues such as failed logins, broken FTP access, or unexpected service behavior. This guide will help you address these problems methodically.

Step 1: Restart Login and Network Services

Rebooting sometimes causes systemd-logind and NetworkManager to fail or behave unpredictably. Restart them manually:

systemctl restart systemd-logind
systemctl restart NetworkManager

Tip: If you are using a static IP setup, double-check your /etc/sysconfig/network-scripts/ifcfg-* configuration after reboot.

Step 2: FTP Service Down – Disable Brute Force Protection in Imunify360

If the FTP service is unresponsive or users are being blocked immediately after login attempts, Imunify360’s brute-force protection may be the cause. To troubleshoot:

Disable Brute Force Protection for FTP

Access Imunify360 GUI via WHM:
- WHM > Plugins > Imunify360 > Settings > Proactive Defense > Brute-force protection
Temporarily disable FTP brute-force protection:
- Navigate to Brute-force Protection Settings
- Under the Services section, uncheck FTP to exclude it from protection
Alternatively, disable via CLI:

imunify360-agent config update '{"BRUTE_FORCE": {"FTP": false}}'

Restart the FTP service:

systemctl restart pure-ftpd

Note: Remember to re-enable protection after identifying and whitelisting legitimate IPs.

Step 3: Reinstall WP Toolkit if It’s Broken After Reboot

Sometimes after a system update or unexpected shutdown, WP Toolkit can break. To reinstall it cleanly:

yum reinstall wp-toolkit-cpanel -y

This will ensure all files are restored and reconfigured correctly.

Optional: Check Firewall and CSF Rules

Ensure iptables, firewalld, or CSF (if installed) is not blocking traffic:

csf -g IP_ADDRESS

Temporarily disable CSF to confirm it’s not the culprit:

csf -x

Summary

Task	Command
Restart system login daemon	`systemctl restart systemd-logind`
Restart network manager	`systemctl restart NetworkManager`
Disable FTP brute-force in Imunify360	GUI or CLI
Reinstall WP Toolkit	`yum reinstall wp-toolkit-cpanel -y`
Restart FTP service	`systemctl restart pure-ftpd`