Bobcares

R1soft Error Failed to connect to (hostname) after 120000 milliseconds – How to fix

by | Jul 17, 2021

Wondering how to fix R1soft Error Failed to connect to (hostname) after 120000 milliseconds? We can help you!

Often our customers using R1soft report to us that they end up with this error while trying to connect to the Agent server.

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

Today let’s see how our Support Engineers fix this for our customers.

How to fix R1soft Error Failed to connect to (hostname) after 120000 milliseconds

Before going into the steps for fixing this error we will see what causes this error.

A typical error message looks like the following one:

R1soft Error Failed to connect to (hostname) after 120000 milliseconds

Cause:

One of the common causes is that the R1soft backup server IP has been blocked at the Agent server firewall. If we have a CSF firewall installed, then it can also be blocked by CSF.

Steps to fix R1soft Error “Failed to connect to (hostname) after 120000 milliseconds”

We must remove the R1soft server IP from the blocked/deny IP list. It may be temporarily blocked or listed in csf.deny. Furthermore, we have to add R1soft server IP in csf.allow as trusted IP.

Following are the two methods with which we can fix this error:

1. Unblocking an IP Address using WHM

1. Firstly from the WHM homepage go to CSF, take the Search for IP section.

2. Then enter the IP that we suspect is being blocked and click Search for IP.

3. If the IP is blocked, it will show and the reason why it is blocked will be given.

4. We can click on the green Unblock button to unblock the IP.

A confirmation that the IP has been unblocked can be seen.

2. Unblock using Command Line for Linux

1. Firstly we have to log in to the server via command line (SSH).

2. Then to find out if the IP address is permanently blocked or only temporarily blocked we can run the following command:

csf -g XXX.0.XX.0

3. The output for a permanent block may look like the following one:

csf.deny: xxx.0.xx.0 # Manually denied: xxx.0.xx.0 (-/-/-) - Mon Feb 20 10:25:05 2017

4. The output for a temporary block may look like the following one:

Temporary Blocks: IP:xxx.0.xx.0 Port: Dir:in TTL:30 (Manually added: xxx.0.xx.0 (-/-/-))

5. For removing a permanent IP block, we can use the following command:

csf -dr xxx.0.xx.0

We may get an output similar to the one given below once the IP is successfully unblocked:

Removing rule...
DROP  all opt -- in !lo out *  xxx.0.xx.0  -> 0.0.0.0/0  
LOGDROPOUT  all opt -- in * out !lo  0.0.0.0/0  -> xxx.0.xx.0

6. For removing a temporary IP block, we can either wait until the time is up or run the following command:

csf -tr xxx.0.xx.0

We may get an output similar to the one given below once the temporary block has been removed:

csf: xxx.0.xx.0 temporary block removed
csf: There are no temporary IP allows

[Need assistance? We can help you]

Conclusion

To conclude, we saw the steps that our Support Techs follow to fix this error for our customers.

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.