AnsweredAssumed Answered

Setting up a HUB environment with NAT

Question asked by Baltasar_Infante Employee on Nov 12, 2015
Latest reply on Oct 9, 2018 by

I'm trying to setup the following environment:


- Primary Hub with public IP Address:


- Remote Hub with private address NATed to


I've tried to run this setup as follows:



1) Install the Remote Hub by using the Hub installer and selecting Custom and choosing "robot", "hub" and "libraries". The install was successful.


2) After that, I went to the primary Hub and added a Network Alias of>


3) After that, I added a Static Route pointing to and I got the error message: Could not connect to Hub:! Reason: communication error. The same error is seen if I point to


4) After some research, all I got was that "static routes are not a good option, better go with Tunnels".


5) I've just created a Tunnel, following the Wiki, but still, I just get to see my Primary Hub on my IM.


6) Checking the primary Hub's log, I can see the following errors:


Nov 11 16:11:33:244 [3536] hub: ssl_connect - connect to '' failed (10060)

Nov 11 16:11:33:244 [3536] hub: TSESS could not connect to tunnel (-2)

Nov 11 16:11:33:244 [3536] hub: CTRL could not connect to server

Nov 11 16:11:33:244 [3536] hub: CTRL could not connect to; 1


My first question would be, when you want to connect to Hubs that are in different Networks but there's no firewall in between, shouldn't I go with the "Static Hub Route"?


Also, the way I understand tunnels is that you use them when there's a firewall involved or when you want to add security (VPN). Would we use tunnels "just" to connect two Hubs that are in different networks?


Finally, any idea on why I can't get my Hubs connected with the configurations I've already tried?


Thanks a lot!