Bobcares

SolusVM connection refused migration error – How to resolve

by | Jul 7, 2021

Stuck with SolusVM connection refused migration error? We can help you.

Here at Bobcares, we handle requests from our customers to fix similar errors as a part of our Server Management Services.

Today we will see how our Support Engineers fix this for our customers.

 

How to Migrate via SolusVM interface?

Today, let us see the steps followed by our Support Techs to migrate via SolusVM interface.

  • Firstly, open SolusVM > Virtual Servers > VPS for migration > Migrate.
  • Then, select the necessary configuration:

Where:

Destination node – the node where VPS should migrate

Migrate Data – If you select “Yes” – VPS will migrate to another node. and location of the VPS will change to the new node in SolusVM interface.

If you select “No”– VPS will not migrate – its location will change to the new node in SolusVM interface only.

Compression – enable compression for transferring VPS data.

Transfer Speed – limits network speed use for migration.

Transfer over Internal Network – enables transfer between nodes using an internal network. Both nodes have to have an internal IP address configured in node settings.

Automate on Success – if set to Yes – VPS on the source node will automatically delete.

  • Then, click on Start.
  • Wait until the migration is finished.
  • Then, select what should be done at the end of the migration.

It is recommended to verify that migration is successful and select corresponding option before finishing migration.

  • Finally, click Confirm.

 

How to resolve SolusVM connection refused migration error?

Typical error might appear as shown below:

OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 192.3.168.10 [192.3.168.10] port 22.
debug1: connect to address 192.3.168.10 port 22: Connection refused
ssh: connect to host 192.3.168.10 port 22: Connection refused

Cause for the error us wrong SSH port is specified for the source node in SolusVM.

 

How to resolve SolusVM connection refused migration error?

Let us see the simple steps followed by our Support Techs to resolve it.

  • Firstly, login to SolusVM admin panel.
  • Then, go to SolusVM > Nodes > Edit page of source node.
  • Finally, set the correct SSH port.

 

[Need assistance with SolusVM error?We can help you]

Conclusion

In short, today we saw how our Support Techs resolved Solusvm connection refused migration error.

 

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF