Enabling SSH meant moving my site files to another server at GoDaddy. On another issue, I needed SSH, but the server I was on at GoDaddy did not support user SSH. GoDaddy insisted that FTP was too basic a protocol to work differently on different servers. Verizon said the problem was with goDaddy- if I can FTP into one site I should be able to FTP into any site.
On one, FTP/Filezilla worked fine, on the other, it only worked when the Verizon firewall was disabled. I have two GoDaddy hosting accounts on two different servers. I had exactly the same problem, but it is now fixed.
If you specifically want to use FTPS then you'll need to connect to the port you defined in your vsftp configuration and open up any necessary firewall ports in the security group the EC2 instance uses.I hope this helps someone. the OpenSSH server that's there by default already gives you sftp functionality.
You don't want to use vsftp to use port 22 as then you will have no way to ssh into your instance without changing the port SSH runs on. To clarify for you, port 22 is already open through the EC2 instance so you actually don't need vsftp, but instead just use the private key provided by AWS when you created the instance and you should be good. I think your issue is that the two are being confused as the error logs are looking for ppk files to present to the server for authenticating the user. The public key is stored in the vsftp server for the user while the client you're connecting from presents the server with the private key. With SFTP you're using a public/private keypair you generate yourself and is tied to a specific user to use for authentication. The difference is FTPS uses an SSL public/private key pair to secure the FTP transactions and still requires you to authenticate via username and password. Please tell me if I'm on the wrong track.įor port 22, you're typically using SFTP and not FTPS. I have already confirmed that port 22 is open in the firewall.īTW, my ultimate goal is for clients to connect without getting any sort of "do you trust this certificate" message during their first connection. Response: fzSftp started, protocol_version=8Įrror: Disconnected: No supported authentication methods available (server sent: publickey) Status: Skipping non-existing key file "C:\Users\.ppk" I get no errors from vsftpd, but when I connect using FileZilla I get this response: Status: Connecting to. I can't figure out how to put those three files in a format that vsftpd can understand. crt files that I downloaded from GoDaddy. (the same one I'm using on my AWS Elastic Load Balancer). I want to use my wildcard SSL certificate that was purchased from GoDaddy. I have researched this for hours, but everything I find shows how to configure a self-generated certificate. Plain FTP works just fine, but I need to enable TLS so my clients can use sftp to upload files. I have an Ubuntu 16.04.3 AWS EC2 instance running vsftpd 3.0.3.
0 kommentar(er)
