If you SSH server is not accessible because of a broken configuration or anything else and is not restarting properly through Home »Restart Services »SSH Server (OpenSSH) in WHM you can try starting safesshrestart script which will kill any running instance of sshd and start a new process on port 22, or if that port is taken on first available port after that, like port 23.
Script can be started by adding “scripts2/doautofixer?autofix=safesshrestart” to the end of your WHM url and should look something like this:
Pay attention to the output in WHM when script runs, it will say on which port was SSH started.
Find out your SSH port
If you are not sure on which port is your SSH server running you can find that out on two ways.
You can use the Restart Services part of WHM and restart SSH by going to Home »Restart Services »SSH Server (OpenSSH) in WHM and watching the output in WHM after you restart SSH, it will say on which port is SSH listening.
Other option is to use an API call to show the port.
You can do that by adding “xml-api/cpanel?user=cpanel&cpanel_xmlapi_apiversion=1&cpanel_xmlapi_module=SSH&cpanel_xmlapi_func=getport” to the end of your WHM url which should look something like this:
When doing a fresh install of Ubuntu 16.04, or any other version of Ubuntu or Linux, after the install you might get your laptop or desktop machine not booting the installed OS, but instead returning “No Bootable Device” message, if laptop is set to UEFI mode.
You might be presented with this image after rebooting your laptop, after a successful OS install.
To resolve this issue reboot your laptop and enter BIOS.
There go to “Select and UEFI file as trusted for executing:” and press Enter key.
Once there choose HDD1.
Then choose <EFI>.
Then you should be able to see <ubuntu> or possibly some other name of your Linux installation.
Then choose shimx64.efi
And then choose Yes when asked if you want to add this file to allowable database.
Reboot your laptop and you should now be able to boot your OS normally.
When trying to run VirtualBox on Ubuntu 16.04, or some other version of Linux, you might get a following type an error message, when trying to start a virtual machine, you just created on a fresh installation of VirtualBox.
VirtualBox might return error saying that it failed to open a session for the virtual machine.
Details of error message will say that virtual machine has terminated unexpectedly during startup with exit code 1 (0x1).
You will also get a “Kernel driver not installed (rc=-1908” message.
Error will say “The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv.”
Error message will ask you to try to reinstall the kernel module by executing /sbin/vboxconfig as root, to reinstall the module, which could fail to complete successfully when you try to run the command in terminal.
One of the possible causes of this type of behavior is that you have Secure Boot enabled in your BIOS on the host machine, which is preventing the install of third-party drivers, and causing issues with VirtualBox installation, which fails to install all kernel modules.
To resolve this error, disable Secure Boot in your BIOS, and then try to run /sbin/vboxconfig command as root, or reinstall VirtualBox, with Secure Boot disabled, to install all the necessary modules.