I have read in the forums that free accounts are not allowed SFTP, kindly re-confirm the same. If so, is there any way that we can make the Normal FTP connection, using user-pwd combination be made more secure?
The server connection is established and the downloads happen, but the connection keeps dropping with the following errors:
Error: GnuTLS error -110: The TLS connection was non-properly terminated.
Error: Transfer connection interrupted: ECONNABORTED - Connection aborted
Any suggestions if this is due to a config mistake at my end?
I have read in the forums that free accounts are not allowed SFTP, kindly re-confirm the same. If so, is there any way that we can make the Normal FTP connection, using user-pwd combination be made more secure?
I think InfinityFree already uses self signed for this.
I’m not sure about this but it looks like you can.
You can use Cloudflare to secure your ftp connection but it will be complicated for you, if you don’t know much about this.
The server connection is established and the downloads happen, but the connection keeps dropping with the following errors:
Error: GnuTLS error -110: The TLS connection was non-properly terminated.
Error: Transfer connection interrupted: ECONNABORTED - Connection aborted
Any suggestions if this is due to a config mistake at my end?
Thanks,
Anand
It looks like this is cause because you were trying to connect to the FTP server through TLS which might not be supported on the server.
@UnknownLolz said:
It looks like this is cause because you were trying to connect to the FTP server through TLS which might not be supported on the server.
SFTP (which is more or less SSH) is not possible here. FTPS is possible, but you’ll want to use the hostname ftpupload.net since that’s the domain the SSL certificate is for.
@Admin said:
SFTP (which is more or less SSH) is not possible here. FTPS is possible, but you’ll want to use the hostname ftpupload.net since that’s the domain the SSL certificate is for.
Things seem to work fine for a while then the connection/current action is constantly breaking due to this error
**Error: GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not read from socket: ECONNABORTED - Connection aborted
**
@Admin said:
SFTP (which is more or less SSH) is not possible here. FTPS is possible, but you’ll want to use the hostname ftpupload.net since that’s the domain the SSL certificate is for.
Our FTP servers use implicit TLS, not explicit TLS.
@ananda said:
Things seem to work fine for a while then the connection/current action is constantly breaking due to this error
**Error: GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not read from socket: ECONNABORTED - Connection aborted
**
That could simply be the inactivity timers kicking in. You should be able to reconnect and continue to navigate your account. It should not interrupt file transfers in progress either.
@ananda said:
Things seem to work fine for a while then the connection/current action is constantly breaking due to this error
**Error: GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not read from socket: ECONNABORTED - Connection aborted
**
That could simply be the inactivity timers kicking in. You should be able to reconnect and continue to navigate your account. It should not interrupt file transfers in progress either.
Seems like inactivity issue to me as well. I am increasing the timeout period in my FileZilla client. Will observe for a while. If the issue still persists will reach back.
After changing the Disconnection on Inactivity to 1 hr, the error has reduced. But it is still occuring. Seems like now the disconnection is happening from the server side.
Is there a way to increment the inactivity time at the server end as well?
After changing the Disconnection on Inactivity to 1 hr, the error has reduced. But it is still occuring. Seems like now the disconnection is happening from the server side.
Is there a way to increment the inactivity time at the server end as well?
I’m sorry, but we set a low inactivity timeout on the server for a reason, and you cannot change the settings of the FTP server. Leaving FTP connections open on the server still uses up a bit of server power. If inactive connections would be left open, that would take server power at the expense of people who are actually trying to make changes to their website’s files.
Please just remember that this issue is caused by the inactivity timers, and disconnecting and reconnecting from your FTP client is enough to keep working.
As much I understand the above mentioned issue, the problem I am facing is downloading a local copy of the theme code. The download once initiated the server constantly keeps disconnecting. Although there is a download is in process which means there is activity happening across the connection.
Infact the same happens even when changing folders with no inactivity at all.
Is there a way to do this better? I am using a regular FTP client tool(FileZilla).
Yes the connection breaks even during basic operations. Yes retrying is the option and it does work after couple of tries. But issue is that if the process is so manual even during basic and simple operations remote working becomes difficult.
Yes the connection breaks even during basic operations. Yes retrying is the option and it does work after couple of tries. But issue is that if the process is so manual even during basic and simple operations remote working becomes difficult.
Hence was looking for a better solution, if any?
Thanks
I’m sorry, but I wanted to know if file transfer are interrupted. So you’ve already added some files to be queued, but the transfers are not completed successfully.
FileZilla opens multiple connections to the FTP server: one for the basic operations (listing files, etc.) and additional connections for file transfers. The server can disconnect the main control connection but leave the file transfer connections intact.
FileZilla does not have any way to automatically detect a closed connection and reconnect on it’s own. FileZilla would only work if we would disable the inactivity timers, but that would cause way more trouble. All FTP servers have timeouts, even though premium services usually have a slightly longer times.
Unfortunately even that gives the same error. See below
**
Command: MLSD
Error: GnuTLS error -110: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Transfer connection interrupted: ECONNABORTED - Connection aborted**
Seems like the problem is persistence in every way.