Troubleshooting Cloudbreak

This section includes common errors and steps to resolve them.

Invalid PUBLIC_IP in CBD Profile

The PUBLIC_IP property must be set in the cbd Profile file or else you won’t be able to log in on the Cloudbreak UI.

If you are migrating your instance, make sure that after the start the IP remains valid. If you need to edit the PUBLIC_IP property in Profile, make sure to restart Cloudbreak using cbd restart.

Cbd Cannot Get VM's Public IP

By default the cbd tool tries to get the VM's public IP to bind Cloudbreak UI to it. But if cbd cannot get the IP address during the initialization, you must set it manually. Check your Profile and if PUBLIC_IP is not set, add the PUBLIC_IP variable and set it to the public IP of the VM. For example:

export PUBLIC_IP=192.134.23.10

Permission or Connection Problems

If you face permission or connection issues, disable SELinux:

Set SELINUX=disabled in /etc/selinux/config.
Reboot the machine.
Ensure the SELinux is not turned on afterwards: