my hoster informed me, there is only SFTP possible on that server from now.
My question:
Are there further settings in WD have to be done, except ticking “use SFTP” in internet/connections setup?
[link, path adaption, whatever]
Will the link name after that // remain the same as before or will it also change?
[ftp://ftp.xyz.com → sftp://sftp.xyz.com ?] - maybe a stupid question, but not for a bloody IT non-specialist :roll:
I was migrated to a new server by my host today and FTPUPD is not getting through using SFTP (neither is clientraw nor SQL updates).
Getting 10060 timeout messages every time. SFTP connection was ok on the old host server up until 9am this morning when the migration started.
Tech support investigating but no solution as yet.
Filezilla connects fine and I can transfer manually, so not sure why WD can’t. I also tried FTPS and that seems to connect and handshake ok, but files end up all 0 bytes on the webserver then error 301: Timeout)
(Looks like meteofrog’s weather has not updated for some time either so I guess he also has problems)
Seems I may have to find a new webhost that still allows plain old FTP access real soon before I get emails from my fans. A hassle I don’t need due to issues at home
would be an interesting excercise to see if the alternative ftp component i have here would work
(as the SFTP I do have in use is probably out of date now)
Is there any more advice on this, my site has failed to update since 1and1 changed from FTP to SFTP the other day.
I only found out they had done it after slow motion email exchange but checking SFTP and port 22 doesn’t seem to connect either.
Having said that it did briefly work at first but quite abruptly refused to connect any more after a few hours - and usual “restart everything” fixes haven’t helped.
At the moment I’m considering changing the domain to point to wunderground page as 1and1 support seems to consist of suggesting settings that don’t work over and over until you go away.
Got quite excited there but doesn’t seem to work.
What’s this about ‘not recognising sub-folders’
Is it worth testing key pages on the root folder server side?
1and1 now helpfully suggest using filezilla even though I told them I can upload with other clients it’s WD getting stuck!
list of files uploaded*
actual messages from upload session* Start Time/date:2:05:42 PM 6/17/2016
Permanent connection selected
Permanent connection, will do ftp now
Finshed email agenda
Finshed email agenda, and more Internet agenda items to do… Time/date:2:05:44 PM 6/17/2016
Logging onto FTP server…[i.d.removed].1and1-data.host
Connecting to FTP server.
[10060] Connection timed out
Failed to connect: [10060] Connection timed out
FTP error occured
FTP error, looking for next agenda item
Checking for next FTP agenda…
there are 2 more things to do
Doing ftp upload
there are 1 more things to do
ERROR: 143: Busy performing current action. at time/date 2:06:05 PM 6/17/2016 agenda
item: dowapupload
Doing abort procedure/program close…
Logging onto FTP server…[i.d.removed].1and1-data.host
Connecting to FTP server.
[10060] Connection timed out
Failed to connect: [10060] Connection timed out
That’s failing before it even gets to the login. Are you sure you have the correct server info in WD?
Just to clarify I changed it to remove my real username.
It must be otherwise valid as it did run - on SFTP setting - for about 24 hours.
Nowadays it’s no big deal changing your host but I get the feeling they are all going this way for security reasons, and it does suggest they are not using standardised protocols.
Mine ran on normal FTP for six years before this, never touched it.
On my setup with 1and1, I’m still using FTP for the weather software (Weather-Display, GRLevel3 and Fling) successfully. I know they ‘prefer’ SFTP, but are still accepting FTP as long as the number of concurrent connections for FTP/SFTP from a single IP address is 5 or under.
It’s possible that your IP address was ‘blacklisted’ for a while due to some combination of failed logins/excessive concurrent connections/excessive connection attempts. Turn off WD main internet switch and let it ‘cool’ for 30 minutes, then retry. If it was an ‘auto-blacklist’, that will (hopefully) let the block reset and you can connect again. WD uses two concurrent connections (at most) – a persistent one for clientraw*.txt realtime updates, and a periodic one for ftpupd to update the other files in your site.
Interesting thoughts here but trying this did not work.
I asked support if IP address was somehow blocked and they checked and it is not.
I tried setting up a secondary FTP account which uploads direct to weather folder rather than setting that part in WD.
FTP log now says username good but DNS error?
Weather Display FTP Upload 9.35 9:54:26 AM
11004: [11004] Valid name, no data record (check DNS setup)
ERROR: Host not found at time/date 9:54:26 AM 6/18/2016 agenda item:
Doing abort procedure/program close…
Edit: just spotted client raw txt is now getting through, I wonder if it resolve itself yet after all this time.