OK scratch that last message.
Got curl upload working.
The issue seems to be that curl is now included with Windows 10 and that version is compiled to leverage WinSSL.
I downloaded the latest version of curl that uses OpenSSL instead and that works ok.
I wonder if that will help with the ftpupd that WD uses, perhaps it is related?
what is the url to the web site so that I can check if I have the files uploading OK with curl?
also one issue that might be re the cant open local file is you have the station name set as
Ilfracombe
i.e capital I and then a small l
but that capital I comes out as a small l in the windows file name
seems to be some confusion
so maybe try setting the station name as something different
e.g just
lfracombe
as a test
in the webfiles/web page setup in WD
The URL to the Saratoga template which is in the root directory of where files get uploaded to is:
Have tried changing the station name.
A few new GIFs got created and uploaded with 0 bytes… same issue
Given that I can replicate the same behaviour via the curl bundled with Win 10 does point to some issue with the SSL implementation (presumably in combination with my hosting server-side setup - otherwise you’d have a chunk of people using Windows 10 complaining!)
Is it worth mentioning it to the FTP author in case he is aware?
the author the component said in testing that there does seem to be a server configuration error
did you day u did get curl to work?
for uploading a file?
email me the command you used
re filezilla
I have tested here…latest version…but it can not retrieve the directory listing…