...
- incorrect URL or network connectivity issue, that prevents node from connecting to the target hypervisor or hypervisor manager
- incorrect credentials
- if SSH connectivity is being used
- incorrect host fingerprint (should be in RSA format) - older versions required fingerprint to be collected first using the following command on the Node:
sudo -u vprotect ssh -o HostKeyAlgorithms=ssh-rsa root@HYPERVISOR - incorrect certificate (or ownership not set to
vprotectuser with 400 permissions
- incorrect host fingerprint (should be in RSA format) - older versions required fingerprint to be collected first using the following command on the Node:
- firewall blocking requests
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...