google backup and sync for mac cannot connect localhost didn’t send any data. err_empty_response

Sometimes bits and pieces of bundles get left behind on deletion.

Folks suggested rsyncX, psync, and Unison, but I was most convinced by the arguments in favor of Chronosync.

Chronosync costs money, but it does exactly what I need it to: it gives me all the power and flexibility of rsync, but with a nice, polished GUI.

All the Chronosync documentation (which is quite thorough, by the way) presumes that you have two locally-mounted volumes, either over a LAN or through FireWire, etc.

But, youll recall I didnt want to haul the PowerBook into the office.

This all seems simple enough, and is a breeze to use now that its set up.

But I was rather surprised that no one had mapped out any sort of simple instructions to sync two machines not on a LAN without using the command line.

My next step would be to automate this process with an AppleScript, but as you can likely tell from above, Im not much of a programmer.

I set up a synchronizer document where one target is on the remote volume (which has to be mounted to set up the document, of course).

So, the next time ChronoSync will run that document, the volume will mount automatically, provided the server is available.

With Chronoscript you have the option of launching this Applescript prior to the sync to mount the volume (or you can run Chronosync from within this script itself if you can figure out the syntax).

Id really like the SSH Tunnel manager syntax if anyone knows it.

However, this is used to mount an AFP volume (not FTP or other), which means that you need to be able to access this volume through AFP, and that means over your LAN.

LAN, the server is never available from Chronosyns perspective).

Thus, if both machines are on the same local network, this hint isnt necessary at all (Chronosync is all you need).

Also, if you want to use a firewire drive as an intermediary, then you also dont need this hint.

However, I wanted to skip the step of carrying a drive back and forth, AND my machines arent on the same LAN.

For this application, the extra step of the SSH tunnel is necessary.

You just need to know either the DNS fully qualified name or the IP address.

I tried Chronosync, but found it to be more cumbersome, and slower, although Ill admit that I didnt time them.

The advantage of running through the tunnel, as in this hint, is security as well.

Going through all these contortions because one is afraid of opening the Terminal is like taking a bus and transferring multiple times instead of just driving there using ones own vehicle.

You could even save this as a shell script and forget the syntax if you wanted to.

Google Backup And Sync For Mac Cannot Connect Localhost Didn’T Send Any Data. Err_Empty_Response