This is a proven workaround on fixing Cyberpanel not working after a server reboot. This error happens commonly on any OpenVZ 6 or OpenVZ 7 VPS.
Symptoms: VPS becomes inaccessible. Website(s) is not accessible / down. Cannot log in to the server through SSH connection. The VPS status in SolusVM is Online but you cannot reach it. You can only have access through built-in Serial Console (in the SolusVM). Networking is not working. Pinging to the server returns RTO.
Objective: To fix Cyberpanel not working issue after a VPS reboot event.
Requirements:
- A Cyberpanel server.
- Access to SolusVM or any other VPS management panel.
- Access to built-in Serial Console.
Fix Cyberpanel Not Working Error on OpenVZ VPS
Step 1. Login to SolusVM > Virtual Serves > choose your Cyberpanel server > Manage
Step 2. Click the “Serial Console” icon
Step 3. Create a session (1 hour should be more than enough).
Step 4. Launch the console (either Java or HTML5). You can also use Putty with predefined connection settings (as displayed in SolusVM).
Step 5. Issue this command:
service network restart
You’ll see:
Restarting network (via systemctl): Job for network.service canceled.
Step 6. See why the error occurred:
systemctl --failed
Expect this output:
UNIT LOAD ACTIVE SUB DESCRIPTION
* tmp.mount loaded failed failed /tmp
* systemd-sysctl.service loaded failed failed Apply Kernel Variables
* systemd-vconsole-setup.service loaded failed failed Setup Virtual Console
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
3 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Step 7. Edit the fstab file using Nano editor:
nano /etc/fstab
Step 8. Delete these two lines:
/usr/.tempdisk /tmp ext4 loop,rw,noexec,nosuid,nodev,nofail 0 0
/tmp /var/tmp none bind 0 0
Step 9. Press Control+O to save, then Control+X to exit the editor.
Step 10. Go back to SolusVM. Click “Reboot” then “Yes”.
Try to log in to your VPS again, as usual, using Putty or try accessing your website(s).
VERDICT
This error is an issue occurs in Cyberpanel installation on an OpenVZ VPS (either OVZ6 or OVZ7). Clearing the two mentioned lines in the fstab file will fix the issue.