Custom Query (8171 matches)


Show under each result:

Results (319 - 321 of 8171)

Ticket Resolution Summary Owner Reporter
#12336 duplicate Lenghty wait to get to site after logging in CBSneyd

I created a new username and password on my Plesk FTP page. In FileZilla, I created a new site profile “Internic” using the new username and password, as shown on the attached FTP setup.png screen shot. I then attempted to connect and got stuck at the "Initializing TLS..." line on the message log for about 8 minutes before being asked to verify the certificate and getting to the site files. If I disconnect (CTRL+D) without exiting the program and then reconnect, I get to the site right away. If I exit the program and start the program again and try to connect, I get stuck on the same "Initializing TLS..." line and it can take anywhere from 3 to 9 minutes before getting in. On the same computer and using the same program, a different site on a different server has exactly the same problems. This does not happen on a different computer on the same home network connecting to the two sites on different servers, running the same version of FileZilla. Connection time is almost instantaneous. This can happen at any time of the day or day of the week. I am attaching a text file of a verbose timestamped message log from another session, and a text file showing system and program information from the FileZilla “About…” panel. According to “Your server is working and assorted routers/firewalls have been correctly configured for explicit FTP over TLS as performed by this test. However there have been warnings about compatibility issues, not all users will be able to use your server. For maximum compatibility, consider resolving these warnings.” The only warning in the log was “Warning: The entered address does not resolve to an IPv6 address.” I am attaching a text file of a verbose timestamped message log from another session, and a text file showing system and program information from the FileZilla “About…” panel

#12328 rejected Connection failed to Fedora 33 SSH/SFTP server Vitaly Zaitsev

Description of problem: Cannot connect to the OpenSSH server on Fedora 33 due to recent crypto-policy changes with using standard RSA-4096 keys (curve25519 works).

I can also reproduce this issue with FileZilla on Windows 10 and even in PuTTY client.

Version-Release number of selected component (if applicable): filezilla-3.51.0-1.fc33 libfilezilla-0.25.0-2.fc33

How reproducible: Always.

Steps to Reproduce:

  1. Install Fedora 33.
  2. Install OpenSSH server: sudo dnf install openssh-server
  3. Enable it: sudo systemctl enable --now sshd.service
  4. Disable password authentication:

echo "PasswordAuthentication no" | sudo tee /etc/ssh/sshd_config.d/00-disablepass.conf sudo chmod 0600 /etc/ssh/sshd_config.d/00-disablepass.conf

  1. Restart OpenSSH server: sudo systemctl restart sshd.service
  2. Create SFTP connection in FileZilla to
  3. Try to connection with RSA key authentication (id_rsa should be added to the SSH agent).

Actual results: Connection failure: FATAL ERROR: No supported authentication methods available (server sent: publickey)

Expected results: Successful connection.

Additional info: Logs attached:

  • filezilla.log - internal FileZilla log file with full debug enabled;
  • sshd-filezilla.log - OpenSSH Server log with debug for the FileZilla connection;
  • sshd-console-client.log - OpenSSH Server log with debug for the default console SSH client.
#12327 rejected Persistent Dialog After Quitting Doc Z

I am using version 3.51.0 of FileZilla Client on a Windows 7 PC. After quitting the Site Manager Ctrl-S dialog label persist in the upper left section of the desktop on top of all other windows. The only way to get rid of this is to restart the PC

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.