1 Answer
- Newest
- Most votes
- Most comments
0
The auth method (PPK, password, Kerberos) doesn't come in to play until after a connection is made -- the server has no idea what you are going to use until then, and except for more exotic Kerberos configurations the client doesn't do anything different either. I suggest rechecking your security groups / NACLs to see if you are blocking connectivity at that layer; perhaps your client ip has changed.
answered a year ago
Relevant content
- asked 8 months ago
- asked 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
Oh!.. Right, I have noticed that my publish IP has changed. Now I created elastic IP and allocated my instance.. and the website started.....
but still my PPK not connecting using Filezila and this time I am getting an error
Error: FATAL ERROR: Remote side sent disconnect message Error: type 2 (protocol error): Error: "Too many authentication failures" Error: Could not connect to server Status: Waiting to retry...