Opened 20 months ago
Closed 20 months ago
#12915 closed Bug report (rejected)
FileZilla Pro no longer working/updated
| Reported by: | Erin Britt | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Client |
| Keywords: | Not connecting to server | Cc: | |
| Component version: | Operating system type: | Windows | |
| Operating system version: | Windows 10 Pro |
Description
02 May - please see attached file. FileZilla is not working on my machine & IT and cybersecurity have exhausted all options.
I downloaded FileZilla Pro earlier this week and had NO issues with it until yesterday. I kept getting the "421 Proxy is closed" error. I upgraded to the newest version of FileZilla yesterday, checked all my network connections, etc. and roped in IT--they couldn't find any issues and were already allowing the app. I've run every diagnostic and nothing is working. Like I mentioned before, I don't have an IT background & have tried just about everything. Any suggestions? Below is the message log...
Status: Connecting to <server name>...
Response: fzSftp started, protocol_version=11
Command: open "<server name>" 22
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Disconnected from server
Status: Resolving address of <server name>
Status: Connecting to 52.227.72.32:21...
Status: Connection established, waiting for welcome message...
Response: 421 Proxy is closed
Error: Could not connect to server
Status: Waiting to retry...
Status: Resolving address of <server name>
Status: Connecting to 52.227.72.32:21...
Status: Connection established, waiting for welcome message...
Response: 421 Proxy is closed
Error: Could not connect to server
Top
Attachments (2)
Change History (3)
by , 20 months ago
| Attachment: | FileZilla_ZScaler.PNG added |
|---|
by , 20 months ago
| Attachment: | FileZilla_Error_Message.PNG added |
|---|
comment:1 by , 20 months ago
| Resolution: | → rejected |
|---|---|
| Status: | new → closed |
Either the server you are trying to connect to is broken, or there is a broken firewall or NAT router injecting fake replies into the connection.
Considering the certificate error you get when running the update check mechanism, it's guaranteed that there's something injecting fake data into connection.