Selinux policy is causing the server to not boot completely. It is caused by an upgrade within CentOS. You’ll need to follow the steps below to fix the issue and restore connectivity to your instance. If you are able to log into the system using the console at my.vultr.com start at step 6. If you are not able to log into the system using the console at my.vultr.com you will need to start at step 1.
1. Click [View Console] to access the console and click the send CTRL+ALT+DEL button on the top right. Alternatively, you can also click [RESTART] to restart the server.
As soon as the boot process starts, press ESC to bring up the GRUB boot prompt. You may need to turn the system off from the control panel and then back on to reach the GRUB boot prompt.
2. You will see a GRUB boot prompt – press E to edit the first boot option. (If you do not see the GRUB prompt, you may need to press any key to bring it up before the machine boots)
3. Find the kernel line (it starts with “linux16”), change ro to rw init=/sysroot/bin/sh.
4. Press CTRL+X or F10 to boot single user mode.
5. Access the system with the command: chroot /sysroot
6. Edit /etc/selinux/config and change “enforcing” to “disabled”
7. reboot -f