Cannot connect to slave node in SolusVM: Connection Failed Debug Data: ERROR:4

Have more questions? Submit a request

Applicable to:

  • SolusVM

Symptoms 

  • The following error is shown in SolusVM when opening  Slave node page:

    SVM_ERROR: Connection Failed
    Debug Data: ERROR:4

  • AutoFTP restore does not start on the Slave node:

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

Cause

The ID Key in /usr/local/solusvm/data/solusvm.conf on Slave node does not match the ID Key at SolusVM > Nodes > List Nodes > Edit Node Password

Resolution

  1. Login to SolusVM admin panel
  2. Copy ID Key from SolusVM at List Nodes > Edit Node Password
    mceclip0.png
  3. Connect to the affected slave node via SSH
  4. Create a backup of original /usr/local/solusvm/data/solusvm.conf file on the affected slave node:

    # cp -a /usr/local/solusvm/data/solusvm.conf{,.bkp}

  5. 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. 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:
    mceclip0.png

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share

Comments

0 comments

Please sign in to leave a comment.