Alex U (Customer) asked a question.

Edited May 19, 2026 at 11:38 PM
"Operate in FIPS 140-3 mode" causes major problems?

Successful in place upgrade from 8.8.12 to 10.0.2. Everything was working, including Server Manager (verified after a restart.)

-Then made configuration changes and restarted server.-

Config changes made:

  • -Turn on “operate in FIPS 140-3 mode”
  • -Turn on “Disable CBC Mode Ciphers”
  • -Deleted FTP Listener (turn off FTPS connections)
  • -Removed SSL Certs
  • -Removed all SSH Host Keys and Generated new with highest size each.

 

What's broken:

  • Some services will not start. Manual start yields 1053 error.
    • Progress Scheduler
    • Progress SSH Server
    • Progress WS_FTP server
  • Local Log in attempt to WS_FTP Manager fails
    • Login page displays but upon entering verified correct credentials, "An error occurred on the server when processing the URL."

 

Support was engaged and stated: "The config changes which you made shouldn't impact access to the server manager."

 

I uploaded logs as requested and was waiting for a response for a few days, so I attempted to directly edit the database that holds the configuration for WS_FTP server and disable FIPS 140-3. As soon as the data changes were saved, I was able to start the services and log in to WS_FTP Manager.

 

I am still awaiting contact from support as we need to enable FIPS, but wanted to get this info out in case others are looking at enabling FIPS or already did and experienced a similar issue. Bonus points for a solution or workaround!

  • 1 answer
  • 100 views

  • Alex U (Customer)

    Support reached out and it has been referred to Developers with an update promised "before end of week." However, we could not wait any longer. I backed up the PostgreSQL DBs and fully uninstalled and attempted reinstall of WS_FTP Server 10.0.2. There was a problem creating the PostgreSQL service on the reinstallation and a repair install could not fix.

    I fully uninstalled again, manually removed ALL remnants of PostgreSQL, Progress WS_FTP and Ipswitch WS_FTP, including empty folders, registry entries, IPS_username profiles, and Progress and Ipswitch environmental variables, as well as PGAdmin folders and contents in my admin account used to install and configure this server. I was then able to successfully reinstall WS_FTP Server 10.0.2., restore the DBs, and implement FIPS 140-3.

    My guess is remnants of an old version of PostgreSQL and/or WS_FTP server was in conflict with 10.0.2 or PostGreSQL 17.9 when FIPS 140-3 was turned on...