"Failed to Establish communication between the cloudendure agent and the replication"

[Hugues Henrion]

Hello Everyone,

I have an issue with the cloudendure replication agent that I have been trying to resolve in every way possible for the last 3 days and I am running out of options.

Here is the setup :

Local computers:

-Guest VM (virtualbox) --> Ubuntu 16.04  local IP : 192.168.1.71 (connection is set to bridge mode)

  Host --> Ubuntu 16.04 local IP: 192.168.1.70

-Another computer for Test on windows --> Windows 7 local IP : 192.168.1.15

Local Network:

All computers are  connected to internet via our ISP box which has no firewall rules set on any port

GCE :

Two weeks ago we followed the installation procedure (on gcp.cloudendure.com) to replicate our VM and all went well, a gce instance was created and the replication process was doing well. 

About one week later, the replication started to lag and was finally interrupted. When we tried to restart the replication via the cloudendure console we got the following error : 

"Failed to Establish communication between the cloudendure agent and the replication"

We followed the general procedures to troubleshoot this problem 

- we opened ingress/egress port 1500 on the GCE replicator instance (although thoses rules were already created automatically during the installation procedure)

- we opened port 1500 for INPUT and OUTPUT via iptables on the VM (ufw is disabled in this machine)

- we tried nc -l 1500 on the VM and call it via telnet 192.168.1.71 1500 vi the local network --> all working good

- We tried to reinstall the agent and create a new instance with a new token but to no avail and we got the same error.

To be sure the problem was not coming from a hidden firewall rule on Ubuntu or from and issue with the bridge mode on virtualbox we first try to replicate the host computer directly. The installatin went well but we got the same problem.

To be sure it was not coming from a Ubuntu mysterious setting issue we tried the replication of a windows computer on the local network (running win7 64). The installation went well, the replication instance was created in GCE (with rule automatically created for port 1500). But we got the same error. so :
 - we open port to incoming and outgoing traffic in windows firewall
 - On our router we routed external traffic  on port 1500 directly to the 192.168.1.15 port 1500.

But it still would not work and we got the same error on the cloudendure console.

We are suspecting there might be an issue on the GCE side but after many trial with the firewall rule on GCE we are running out of option.

The VM we are actually replication is running odoo-server and we had the exact same problem with port 8069 on GCE. The first week when the replication went well; we opened port 8069 on GCE for an instance running a cutover of the replication. Then suddenly we lost acces to port 8069 and had to route port 80 to 8069 in Ubuntu to get acces to odoo.

After 3days of searching and fiddling around we are pretty much lost on this one,

We will appreciate any input you guys could give us,

Thanks to all.

[Leonid Feinberg]

Hi,

Could you please send an email to sup...@cloudendure.com with this description? The CloudEndure support team will be happy to help you!