Extract SSL certificate PFX file for Serv-U

4/29/2019 8:01 PM

1/6/2025 4:57 PM

Serv-U supports HTTPS and FTPS protocols which needs an SSL certificate for encryption. There are instances where an existing certificate is already available in a PFX format. Serv-U does not support a PFX format SSL certificate. The private key and certificate must be extracted from the PFX file so they can be imported in Serv-U.
 

Serv-U Managed File Transfer & Serv-U FTP Server

Using OpenSSL is one way to extract the private key and certificate file from the PFX format SSL certificate.
See the instructions below to use OpenSSL.

 

• Download and install OpenSSL in the server (or the administrator's PC) from here. Use the light version if possible.

Note: Choose Win64 OpenSSL v1.1.1m Light EXE file when downloading the OpenSSL 

• Copy the PFX file inside the C:\Program Files\OpenSSL-Win64\bin folder.
• In the Windows command-line, navigate to the OpenSSL bin directory: C:\Program Files\OpenSSL-Win64\bin

 
Run the following commands below. Make sure to change the 'yourpfxname.pfx' to the actual file name of the PFX file.
 

• To extract the certificate file: Note that the PFX password needs to be entered here one time.

REM - Scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any - implied warranties of merchantability or of fitness for a particular purpose.
REM - The risk arising out of the use or performance of the scripts and documentation stays with you. 
REM - In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation. 

openssl pkcs12 -in yourpfxname.pfx -clcerts -nokeys -out yourpfxname.crt

 

• To extract the private key file: Note that the PFX password needs to be entered here three times.

REM - Scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any - implied warranties of merchantability or of fitness for a particular purpose.
REM - The risk arising out of the use or performance of the scripts and documentation stays with you. 
REM - In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation. 

openssl pkcs12 -in yourpfxname.pfx -nocerts -out yourpfxname.key

 

• Using File Explorer, navigate to the OpenSSL bin folder (C:\Program Files\OpenSSL-Win64\bin) and copy the .crt and .key files into the Serv-U server.
• Import the .key and .cert files into Serv-U.
• Launch the Management Console
• Go to Global or Domain > Limits & Settings > Encryption tab
• The .crt file goes into the Certificate Path field
• The .key file goes into the Private Key Path field
• Enter the same PFX password in the Password field
• Click the SAVE button

Note:
 

• If GoDaddy is the SSL provider, they will provide a gd-bundle cert with the download. Use that bundled certificate in the CA (Certificate Authority) Certificate Path in Serv-U.
• If the SSL certificate is used in the Global level Encryption, make sure you have the same information in the Domain level Encryption.
• If the SSL certificate information is defined in the Domain level, leave the Global level Encryption blank.
• The CA (Certificate Authority) field does not accept a .p7b, or .pfx format. It should always be in .cer or .crt file extension.

Disclaimer: 

Scripts are not supported under any SolarWinds support program or service. Scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.