FTP issue followup

Regarding issues related to ftp to ftpupload.net and blocking by TPLInk HomeShield powered by Avira.

I submitted a ‘false positive’ to Avira several times. After a week of waiting it appears Avira has eliminated the [TPLink HomeShield] rule that was previously blocking ftpupload.net. I’m now able to get a somewhat reliable connection with FileZilla and review/interact with the website files while HomeShield web protection is enabled.

However, there are some apparent non-fatal errors that are intermittently thrown during the connection process. I pasted them below if anyone has feedback. They happen within 4 to 6 seconds of starting the connection and before a directory is displayed for user interaction. I’m not sure what the ‘need to type a little faster’ means as there is no typing involved with the connection process, just connect and get a directory to work with. All the credentials and home directory are auto-populated.

Status: Directory listing of /youdontknow.ct.ws/htdocs successful
Response: 421 Timeout - try typing a little faster next time
Error: GnuTLS-fel -110 i gnutls_record_recv: The TLS connection was non-properly terminated.
Status: Servern stängde inte ner TLS-anslutningen korrekt
Error: Could not read from socket: ECONNABORTED - Anslutningen avbröts
Error: Disconnected from server
Status: Resolving address of ftpupload.net

This is expected behavior. Our FTP server is quite aggressive in killing inactive FTP connections. The line at the top shows that Filezilla was able to connect successfully, send and receive commands, and to access your files. The line after that is the result of the FTP server killing the connection after 20 seconds of inactivity.

This is completely normal, and shouldn’t prevent you from using our FTP server to manage your website. If you see this error, just disconnect and reconnect to resume file management.

4 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.