1
0
-1
1 answer
- 10-1
Thanks for reply.
When the Local side (Private Server) has internet, sometimes this error message shows but the sync is established.
Regards
Add your comment...
Thanks for reply.
When the Local side (Private Server) has internet, sometimes this error message shows but the sync is established.
Regards
Hi,
I see the following error in the Exalate. The Local side is on the internal network and the Remote side is on the Internet. Without the Internet, there is no communication, while previously there was a connection between the two sides without the Internet. what is the problem?
Exaltate had trouble communicating with the remote side when polling for changes, the communication will be retired automatically.
Sync is not blocked
Regards
GG
Hi GG,
More information on Private / Public issue synchronization can be found here: https://docs.idalko.com/exalate/x/doYrAQ
In the private-public connection, all communication over TCP/IP is initiated from the private side. In this case, the public side never sends HTTP requests. It only answers requests sent from the instance, located behind the firewall.
The private instance (one behind the firewall) requests for any changes either every 20 seconds, or whenever there are changes to sync towards the public instance. This explains the delay in sync in case that there are no changes in the private to push to the public.
If there is no internet, at least you would need to whitelist the Exalate cloud gateway. More information on this can be found here:
https://docs.idalko.com/exalate/x/1wJ1Aw
Kind regards,
Ariel