Tools

Allow Non-RFC-compliant option is not available in the Limits & Settings after installing Serv-U 15.3.2 Hotfix 1

This article will provide information on how to resolve why the Allow Non-RFC-compliant option is not available in the Advance option in the Limit Tab under Limits & Settings.

First published date

3/30/2023 2:23 PM

Last published date

5/26/2023 1:50 PM

Overview

In Serv-U 15.3.2.155, there is a HotFix1 available to download for the SolarWinds Customer Portal to address the following:

OpenSSL upgraded to 3.0.8
New Serv-U settings allowing non-RFC compliant SSH protocol version exchange
- Ref: SFTP connection not established for legacy Java clients
Security enhancement in SSH key pair authentication

However, there are instances in which, after applying the HotFix1 for Serv-U 15.3.2, the option to enable "Allow Non-RFC-compliant " does not appear.

Product section

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

Cause

Serv-U HF1 was applied without upgrading to Serv-U 15.3.2 first.
Failure to copy the Client folder in the Serv-U installation path.

Resolution

Ensure that the Serv-U installer 15.3.2.172 has been installed in the environment.
- For Windows: Go to Control Panel > Programs > Programs and Features > See Serv-U version
- For Linux: Go to the Serv-U installation folder and see Serv-U-StartupLog.txt.
If the 15.3.2.172 has been installed but getting the issue:
- Make sure to copy the "Client" folder from the 15.3.2 HF1 to the installation path of Serv-U.
Upgrade to Serv-U 15.4.0.
- Serv-U File Server 15.4 Release Notes

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.