The good news is that I chose AWS, which while it is more expensive that a local Australian option, it will deliver (magnitudes) better performance to iFamily users in North America and Europe.
One thing that AWS does not do easily is FTP Servers, they are an older technology which was popular in the nineties and noughties but have become less than popular in the tech world and most businesses have permanently decommissioned their FTP due to their insecurities. (The servers not the people).
The update checks from within iFamily, (the ones that occur every 30 days), are checking for a file on the old FTP server we used to host. The error shown that your "internet may not be working", is akin to having knocked on the front door of a house which has been demolished, there's simply nothing to connect with in the background.
I will be using a more modern method within the the next release, building an API which will include a basic version checking portal. This will replace the current method and I will do my best to communicate this to all users of iFamily in advance. (Although, I would hate to run afoul of the new privacy laws in Europe, I will tread carefully on that one. I may also consider briefly resurrecting the old update server to capture as many current users as possible.).
Thanks for reading,
Warwick.
- iFamily_updates_ErrSite.png (46.06 KiB) Viewed 38510 times
- iFamily_updates_cnxnErr.png (58.85 KiB) Viewed 38510 times