Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Topics about the Beta trials up to Build 3043, the last build by Cumulus's founder Steve Loft. It was by this time way out of Beta but Steve wanted to keep it that way until he made a decision on his and Cumulus's future.
As it's affecting both http and ftp, the issue is apparently at a lower level, so it's unlikely you'll get any useful information out of Cumulus. I think you'll have to look for answers in Ubuntu. Googling suggests there have been a number of internet related issues with 17.04, DNS lookups in particular.
As it's affecting both http and ftp, the issue is apparently at a lower level
I have resolved the DNS lookup problems which were contributing to about 50% of the timeouts. From your quote above, I am assuming that Cumulus doesn't set a connection timeout value? If it doesn't then I am assuming that the value is obtained from the .net framework implementation. If this is the case then I will search for this. Could you please confirm either way whether Cumulus sets a timeout?
As it's affecting both http and ftp, the issue is apparently at a lower level
I have resolved the DNS lookup problems which were contributing to about 50% of the timeouts.
I should say what I did, for completeness. I upgraded Ubuntu linux from 16.04 to 17.04. You do this by first upgrading to 16.10, then upgrading to 17.04. The 16.10 to 17.04 upgrade changed the local DNS resolver from dnsmasq (which I have been using for years) to systemd-resolved (which is relatively new and is a bit quirky still). This was a notified change (I missed the notification - probably buried in all the other changes, and I probably wouldn't have appreciated the implications just from reading that the change was going to occur). All I did was to re-install dnsmasq and disable systemd-resolved. That sorted out the HTTP errors, which were affecting uploads to WOW, PWS, Weather Underground and Twitter - most noticeably with Twitter which saw very few successful uploads, whereas the other services didn't suffer too much.
The FTP errors I was seeing were related to me having passive FTP set in MX. My FTP server didn't really like this, but happened to start complaining for some reason at the same time as the Linux upgrade. I just assumed the two were connected. After much head scratching I finally realised they were unrelated, and resolved the problem by changing Cumulus.ini to use active FTP.