Bobcares

wesupport

CLIENT AREACall Us 1-800-383-5193
Bobcares

wesupport

Call Us 1-800-383-5193
Bobcares

wesupport

Call Us 1-800-383-5193

Need help?

Our experts have had an average response time of 13.52 minutes in October 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

R1soft failed to get key from the server – How to resolve

by | Jun 21, 2021

Wondering how to resolve R1soft failed to get key from the server error? We can help you.

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

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

 

R1soft failed to get key from the server

Usually, while trying to get the key from the server using r1soft-setup –get-key, users at times sees errors like “connection refused” or “Unable to get key from remote CDP Server” error.

Today, let us discuss about the steps followed by our Support Engineers resolving these errors.

Connection refused

Typical error will look as shown below:

# r1soft-setup --get-key http://192.168.1.103
Get http://192.168.1.103//public_info: dial tcp 192.168.1.103:80: connection refused

Please note when configuring the R1Soft Manager – http and https ports are set using the below command:

# serverbackup-setup --http-port 26080 --https-port 26443

Thus, the following command should work when setting up the key on the agent server to the Manager server:

r1soft-setup --get-key http://192.168.1.103:26080

In order to manually configure the key follow below steps:

  • Firstly, login on to CDP server front end panel
  • Then, click on “Advanced Options” on the left-bottom menu
  • Next, copy the Public Key from the page.
  • On the CDP agent(the server you are trying to configure to r1soft), edit the config files at:
# cd /usr/sbin/r1soft/conf/server.allow
#ls -la
--w----r-- 1 root root 271 Mar 3 11:13 192.168.1.103ifconfig

# nano 192.168.1.103ifconfig
  • Paste the Public Key of CDP server into this file without any white spaces.
  • Also white list the CDP server IP in the agent firewall.
# nano /etc/sysconfig/iptables

Then add the following.

-A INPUT -p tcp -s 192.168.1.103 -j ACCEPT

Restart iptables on Agent server

# service iptables restart
  •  Finally, go to Protected Machines, Click arrow on the right for Test Agent Connection.

 

Unable to get key from remote CDP Server

In this case, error will look as shown below:

[email protected] [~]# r1soft-setup –get-key http://37.x.x.x
Couldnt connect to remote host
Unable to get key from remote CDP Server

Our Support Techs followed below steps to manually configure the key.

  • Firstly, login on to CDP server front end panel
  • Then, click on “Configuration” on the left-bottom menu
  • Copy the Public Key from the page.
  • On the CDP agent(the server you are trying to configure to r1soft), touch a new file naming the IP of CDP server, like as follows:
#touch /usr/sbin/r1soft/conf/server.allow/37.x.x.x (37.x.x.x is the IP of CDP server)
  • Then, paste the Public Key of CDP server into this file without any white spaces.
  • Also white list the CDP server IP in the agent firewall.
  • Test the connection to CDP agent from r1soft panel while trying to add a new server to it.
  • Go to Servers >> Add Server. If everything successfull, then you should get the following message status on the screen.
Successfully communicated with Agent!
Resolving Internet Address

Resolved hostname to: 82.x.x.x
Connecting to Agent

Successfully connected to Agent
Authenticating with Agent

Authenticated with Agent

 

[Need further assistance with R1soft error? We can help you]

 

Conclusion

In short, today we discussed about two different errors and their solutions provided by our Support Techs.

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 *

Categories

Tags