Custom Query (8174 matches)
Results (58 - 60 of 8174)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12910 | rejected | Cannot connect to Filezilla server | ||
| Description |
Since last week, one of my customer cannot connect to FileZilla server. Keep in mind that it was working before. One of her colleague is able to connect to the server on the same network and I can connect with her account on another network. In the window, it says: AUTH TLS 502 - Auth command is not supported. 502 - Please contact your network administrator to enable FTPS service What cause this issue? |
|||
| #12909 | worksforme | Server Trust Certificate | ||
| Description |
My problem is exactly as described in Bug Report 12199, but I could not find an answer to it. When connecting to the server the certificate shows that it is not trusted and the buttons to override that and force trust are greyed out. If I use OK and move on it does connect. I have had my ISP check that the certificate is correct, and it is. Sadly it cost me a lot of money to do that. See attachments. I am using the latest Filezilla (it automatically updates, so that is always the case). This happens on both my machines which are Windows 10 Pro 22H2 and Windows 10 Home 21H2. |
|||
| #12908 | worksforme | Unicode characters in filenames (server side) not shown properly | ||
| Description |
Seems like I'll have to upload the attachments afterwards. I have uploaded a bunch of files to a server, with unicode characters in the file names. I'll attach a screenshot of how such characters look like in fileziulla in the server panel. For comparison, I'll attach a screenshot of a terminal where I'm connected via SSH to the very same server and I've run a "ls" command: you can see the unicode characters properly rendered in the output. |
|||
