noVNC not working for migrated KVM VPS

Have more questions? Submit a request

Applicable to:

  • SolusVM

Symptoms 

After transferring of the KVM VPS to a different node noVNC not working:

CONFIG_TEXT: Failed to connect to server (code: 1006)

Cause

The issue caused by the SolusVM bug #SVM-1705

Resolution

Use the following steps as a workaround:

  1. Connect to the Master server via SSH
  2. Move the following file to another location:

    # mv /usr/local/solusvm/data/_vnc.conf /root/_vnc.conf.orig

  3. Log into SolusVM web interface and browse to Dashboard > Configuration > General Settings > Other tab
  4. Switch noVNC Socket Location option from Master Node and click Update
  5. Switch it back to Master Node and click Update

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.