11/16/2023 0 Comments Filezilla server refused our keySet up new SFTP "Ask for Password" and "Normal" connections to the server without specifying port or passwordĮverything I've tried results in the same error: Status: Connecting to. Setting an Inbound and Outbound Port 22 Connection to "Open": Getting desperate, I've been trying to open any form of port 22 on my local machine - inbound and outbound - just to try to get any kind of connection established other than KeyFile connections.Ĭompletely shut off Windows Firewall, Defender, etc.: I've disabled everything I could think of and tried to clear the way for any port 22 connections.Ĭlearing the trustedcerts.xml file: This was located at %APPDATA%\FileZilla per the following thread I cleared out everything and started fresh: Ĭhecked and re-checked my passwords, usernames, etc. Setting FileZilla to Active Mode: I've set FileZilla to Active, back to Passive, and nothing here has seemed to work. I suspect from searching that has something to do with the keyfile, either the format, or where I've stored it, or the permissions granted to it. I get 'server refused our key' in Filezilla. This was immediately changed back to only my IP. That keyfile was created on the Windows machine using NotePad and given the Key Name shown in AWS instance with an extension of. Temporarily setting the allowed connection on port 22 (on the server) to ALL ips: This was to see if it was somehow blocking my IP. User:, but like the host, the same one I've always used.Host:, but the very same one I've used for years connecting from a Linux environment.ppk (as putty demands private key in ppk format) I had to. I solved them in the following way: 1) username should be 'bitnami' (ec2-user is not working) 2) Using puttykey to convert the public SSH-key from.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |