I remote logged in and saw I had a flatline… Restored files and restarted WD.
My webpage (deputydawgwx.com) is not updating yet weatherunderound is
I manually launched cronftpreal from terminal. It starts doing its count 1,2,3 etc. When gets to 10 where it should upload, it just sits there (see screen shot).
I thought maybe my hosting site was down, yet I can FTP into that.
Don’t know if this issue is the one causing your problem, DeputyDawg, however as of 2:35 PST 1/8/17 one large ISP (AABACO, used to be Yahoo.com) that is my web hosting service disallowed TLS 1.1 and requires TLS 1.2 as ftp protocol. There have always been problems for me because both this web hosting service required FTPS (aka FTP via TLS/SSH) and my university requires SFTP.
But this latest issue affected my website porting www.oak1e.com. Also, even using an ftp client with the built in TLS had to bechanged (in Transmit preferences) to TLS 1.2 from 1.1.
There was no notification to me of this change. I had to figure it out. The Help people at yahoo.com also thought TLS is TLS, and told me they couldn’t figure out why Transmit, let alone WD, stopped ftp transfers without any error messages.
Ah, OK. That was a different situation. I resolved my problem (which has been ongoing for about four years now) by turning off WD’s built in ftp and just saving the files locally. Then I set up a script through Automator (built into the Apple operating system) to synchronize the files between /webfiles locally and on my remote server once per hour each day. The Automator script uses the wonderful Transmit ftp program’s Synchronize command. However, my problem is not unique. I notice on the Forum for WeatherCat (which only supports ftp and not SFTP and FTPS) people are asking for some solution. I realize that other services such as GoDaddy don’t require secure web hosting, but unfortunately, in the university world and in the business world it is pretty much de facto.
The version of WD that I am using had FTPS (FTP with TLS/SSH). It’s just that the TLS version WD was using was 1.1, which I think was the version as of 2008 or 2009. A lot of web hosting services that require secure connections stopped using that a few years ago, and AABACO (yahoo small business solutions) stopped supporting it and required TLS 1.2 last week. All of a sudden WD stopped communicating with AABACO (and so did my settings on Transmit). I could change the protocol on Transmit in its preferences, but there was no way for me to change the version of TLS WD was using.
I read your post, Brian. And I interpreted it that you will be including that curl script into WD future releases.
I was just clarifying why some WD users might be getting connection errors when older versions of WD are attempting to upload .html pages to web hosts. I look forward to your changes to WD to accommodate this. The graphic below is what I finally got from AABACO about the problem I was having.
I did not say actually say I will be including into WD future releases
I just said that it could be a way to to be able to support FTPS or SFTP
by using curl
it was just an idea
if you want to work with me on that idea, let me know
I just spent the better part of two days sleuthing out why WD stopped ftping. At least I got my website updating again. Got to get back to other things that must take priority for the next several days. It may be a week or so before I have loose time to work on this. It looks like I am the only one affected anyway, so no big deal.
curl works
with your ftp settings
but I had to update curl on my mac and change the path variable so that new version is used
so I have curl version 7.48
and so I can get WD mac version to call this curl command direct to upload the needed files
see what version of curl you have:
in a terminal window go
curl -V
I have added option to use secure FTP now (uses curl (you will need the latest version of that)
to the latest WD Mac version update (see in the connections setup)