If you generate your own private key and certificate without putting a path in front of the file name, FZS only puts the bare filename in the certificate field without an error notice, but later you will get 'Could not load certificate file' errors in the FZS log when someone tries to connect via FTPS/FTPES (Implicit/Explicit).

Please note that FZS needs the paths to the certificate files: If you have a slower connection, let's say around 1.5Mbps up you may not have to worry about CPU utilization as much.

When you apply encryption to your FileZilla server the CPU will have to do many calculations to encrypt the data being sent and decrypt the data being received.īandwidth will also play a factor in how much the CPU is being utilized. There is however one thing that needs to be taken into account, CPU utilization during the connection handshake. The bigger the key size the more secure the certificate and the initial session key exchange on every connection will be. The key size for the certificate is chosen at the top of the generator: 1280 bit, 2048 bit, 4096 bit. The Generator will want the country code, state, city, etc.īe as truthful as possible, you only undermine your own credibility if you enter wrong information into the certificate. First, you'll want to create a certificate, this can be used in the Certificate Generator in FileZilla Server.

Setting up filezilla server