Sometimes, SolusVM users encounter this error while trying to connect to a node. This generally happens when there is No support for PHP handler on the slave server after upgrading SolusVM. 

Here at Ibmi Media, as part of our Server Management Services, we regularly help our Customers to perform related SolusVm queries.

What triggers SolusVM error "Connection Failed Debug Data: ERROR:4" ?

When this error occurs, the following error is displayed in SolusVM when opening Slave node page:

Connection Failed Debug Data: ERROR:4

AutoFTP restore does not start on the Slave node:

Could not connect to master server. Is the master online with port 5656 SSL open? exiting…

Cause for the SolusVM 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:

1. Log into SolusVM Slave Node via SSH.

2. Run the command to get the required information:

#cat /usr/local/solusvm/data/solusvm.conf

How to resolve SolusVM error "Connection Failed Debug Data: ERROR:4" ?

To fix this error, apply the following steps:

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}

5. 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

6. Then 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 facing SolusVM issue? We can help you. ]