For the last day and a half I have been having problems updating the files on my website using WD Ver10.37 S56. I haven’t changed any WD FTP settings recently and suspect that it’s probably not WD at fault.
The problem is after starting Realtime FTP after a few minutes it stops working and gives the following error:
ftpupd gives the same error part way through uploading files as can be seen in the ftpupdlog.txt below. I have attached the log of ftpupd and a screenshot of realtimeftp below to show the errors.
I have spoken to my host and they are saying there are no problems their end. Ive also restarted my PC and router but the problem continues.
I’m wondering if anyone could help me work out what is going wrong and how to fix it.
I have tried passive mode but the same thing happened.
I have spoken to my FTP host and they remotely accessed my computer to look at WDs settings and setup a new FTP account on the server but in the end their answer was to use Filezilla instead.
I don’t know if you or any others have any more suggestions on what I could try or what they may try at their end.
I’m not sure about secure FTP, but they did get me to try port 22 but it failed to connect.
They setup a new account because they couldn’t get my old account to connect however the problem continues.
I’ve just tried filezilla as I am adding a twitter box to my index page whilst I get this sorted and it gave the following error:
Status: Resolving address of ftp.gosportweather.co.uk
Status: Connecting to 91.222.9.10:21…
Status: Connection established, waiting for welcome message…
Status: Initializing TLS…
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Disconnected from server
Status: Delaying connection for 5 seconds due to previously failed connection attempt…
Hmm thats funny as it seems strangely similar to WDs behaviour:
150 Connecting to port 51021
301: Interrupted.
Real Time Clientraw FTP freezes for about 60 secs at 150 Connecting to port 51021 before giving the 301: Interrupted error.
It seems Real Time Clientraw FTP tries with all it’s might to connect but the server times out the connection.
Also they said that I was trying to connect to port ‘51021’ instead of 21 is this correct or is 51021 just a random number created by Real Time Clientraw FTP.
I’ve noticed that the website seems slower than usual and I can’t find any problems my end so I’m tempted to send off my WD FTP logs and Filezilla log to show them that their server clearly has a problem as three FTP clients are having problems connecting and are all displaying the same errors.
its clearly a problem on their end, if they deny it
the port number is an assigned port number, initiated by the server
normally that only happens with passive mode (i.e a dynamic port is used)
hence I was suggest to have passive mode in use
the fact they do not know about this sort of thing is troublesome
However in passive mode it seems to show more clearly that the problem is at their end by the fact that the server appears to accept the connection but then times out as shown by the following lines:
150 Accepted data connection
301: Interrupted.
I’ve also tried SFTP using port 22 but it just says ‘connection refused’ so I suspect that it’s not enabled on my account.
I’ll get onto them in the morning with the log files as it’s clear that it’s not WD, my computer or broadband at fault.
they could be blocking it at their end without even realising
or it could be at your end, e.g your firewall blocking the transfer (or antivirus program or similar)
It appears to be working again now. I suspect it was something to do with the TLS software as shortly after I sent them details of the error in Filezilla (which appeared to show TLS problems) it started working again.
TLS stands for Transport Layer Security (TLS) which is a cryptographic protocol that provides communications security over a computer network. It’s similar to SSL.
Looking at the error log of Filezilla it appeared to get stuck at Initializing TLS and then when it tried to disconnect it gave the following error:
Error:GnuTLS error -110: The TLS connection was non-properly terminated.
Status:Server did not properly shut down TLS connection.
GnuTLS is a free software implementation of the TLS, SSL and DTLS protocols.
So it appears that the GnuTLS software wasn’t starting or stopping properly hence why my connection to the server was timing out.
I’ll have a word with them about FTPS as when I selected it in WD Real time Clientraw FTP gives the follwoing error:
actual messages from upload session*
Real time Clientraw FTP, vers 9.8 Time/date:16:04:03 24/08/2017
Logging onto FTP server…ftp.gosportweather.co.uk
Connecting to FTP server.
OK
Connected.
220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
220-You are user number 1 of 50 allowed.
220-Local time is now 16:04. Server port: 21.
220-This is a private system - No anonymous login
220-IPv6 connections are also welcome on this server.
220 You will be disconnected after 15 minutes of inactivity.
AUTH TLS
234 AUTH TLS OK.
Starting secure channel handshake.
Enabling TLS versions: TLS1.2 TLS1.1 TLS1.0
Cipher Suites:
TLS_RSA_PSK_WITH_NULL_SHA (0x002e);
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c);
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b);
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030);
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f);
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f);
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e);
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024);
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023);
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028);
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027);
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a);
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009);
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014);
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013);
TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d);
TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c);
TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d);
TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c);
TLS_RSA_WITH_AES_256_CBC_SHA (0x0035);
TLS_RSA_WITH_AES_128_CBC_SHA (0x002f);
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a);
TLS_RSA_WITH_RC4_128_SHA (0x0005)
Sending 184 bytes of handshake data.
Receiving 1452 bytes of handshake data.
Receiving 1518 bytes of handshake data.
Sending 126 handshake bytes.
Receiving 258 bytes of handshake data.
error verifying server certificate: 0x800b010f
FTP error occured
Negotiated SSL parameters: Protocol: TLS1.2 Cipher: AES Cipher strength: 256 Hash: SHA384
Hash strength: 0 Key exchange: ECDH Ephemeral RSA Key exchange strength: 256
OK
Connected.
USER=****
331 User [email protected] OK. Password required
PASSWORD=****
230 OK. Current restricted directory is /
PBSZ 0
200 PBSZ=0
PROT P
200 Data protection level set to “private”
PBSZ 0
200 PBSZ=0
PROT P
200 Data protection level set to “private”
Changing to remote directory public_html
CWD public_html
250 OK. Current directory is /public_html
Error error verifying server certificate: 0x800b010f with FTP transfer
Error occured at:16:04:04 24/08/2017
Error error verifying server certificate: 0x800b010f with FTP transfer
Error occured at:16:04:04 24/08/2017
Error error verifying server certificate: 0x800b010f with FTP transfer
Error occured at:16:04:05 24/08/2017
Filezilla gives the follwing error:
‘The servers certificate is unknown.’
So there appears to be a problem with their certificate.