Wondering how to fix SolusVM error “Connection Failed Debug Data: ERROR:4”? We can help you.
Often SolusVM users come across this error while trying to connect to a node.
Here at Bobcares, we often handle requests from our customers to fix similar SolusVm errors as a part of our Server Management Services.
Today we will see how our support engineers fix this for our customers.
What causes SolusVM error “Connection Failed Debug Data: ERROR:4”
The following error is shown in SolusVM when opening Slave node page:
AutoFTP restore does not start on the Slave node:
Now we will see what causes this error.
Cause for the error
The main cause can be the ID Key in /usr/local/solusvm/data/solusvm.conf on Slave node does not match to the ID Key at SolusVM > Nodes > List Nodes > Edit Node Password
SolusVM creates the KEY:PASSWORD in the file after the SolusVM slave installation.
In order to get the KEY:PASSWORD pair we can do the following:
- Log into SolusVM Slave Node via SSH.
- Run the command to get the required information:
#cat /usr/local/solusvm/data/solusvm.conf
How to Fix SolusVM error “Connection Failed Debug Data: ERROR:4”
Following are the steps to fix this error:
1. First, we have to log in to SolusVM admin panel
2. Then copy ID Key from SolusVM at List Nodes > Edit Node Password
3. After that connect to the affected slave node via SSH
4. And create a backup of original /usr/local/solusvm/data/solusvm.conf file on the affected slave node.
We can use the following command for this:
# cp -a /usr/local/solusvm/data/solusvm.conf{,.bkp}
3. Next, we have to paste this ID Key to /usr/local/solusvm/data/solusvm.conf replacing the original one:
# cat /usr/local/solusvm/data/solusvm.conf
3BfBmcKgBcGiliVbY4LtY0udlmbxFD62SqOoCR61gMjeTqMxST:wXEonrxjek7fTbVTxOHVTPqY7wUjgZyLKRb37XkhhFNTaSybGP
4. Now we can copy the PASSWORD (second part of /usr/local/solusvm/data/solusvm.conf file) and Paste PASSWORD to ID Password field at List Nodes > Edit Node Password.
[Still, stuck with the error? We can help you]
Conclusion
In short, we saw how our Support Techs fix this SolusVM error for our customers.
0 Comments