Network Management

RabbitMQ Fatal error "insufficient security - no suitable ciphers"

This article describes the issue where RabbitMQ is not working as expected and you receive the error: "Insufficient security - no suitable ciphers showing in the Orion RabbitMQ logs."

First published date

5/13/2019 3:50 PM

Last published date

3/13/2025 9:55 PM

Overview

This article describes the issue in which RabbitMQ is not working as expected, and you receive a Fatal Error message of Insufficient Security.

​​​​​​If you are having this issue, check C:\ProgramData\SolarWinds\Orion\RabbitMQ\Logs and verify the following error in the RabbitMQ log file:

[info] TLS server: In state hello at tls_handshake.erl:201 generated SERVER ALERT: Fatal - Insufficient Security - no_suitable_ciphers

Product section

Orion Platform

Cause

Operating system Ciphers do not match the set used or supported by the application.

Resolution

For information on currently supported ciphers, see Ciphers supported by RabbitMQ in FIPS mode and in non-FIPS mode.

Resolution 1

  1. Make a backup or snapshot of the Orion server.
  2. Download the tool: https://www.nartac.com/Products/IISCrypto/ 
  3. Log in to the server hosting the main polling engine.
  4. Open Orion Service Manager and stop the Orion services:

  5. Open the tool as Administrator.
  6. Select Best Practices and click Apply:

  7. Restart the Orion server.
  8. Repeat steps 3-7 on all Orion servers (on the HA backup of the main polling server if available, then on any additional polling servers, additional web servers, and any other HA servers).

Resolution 2

  1. Download https://www.nartac.com/Downloads/IISCrypto/IISCrypto.exe 
  2. Log in to the server hosting the main polling engine.
  3. Open the tool as Administrator.
  4. Select the Cipher Suites tab.
  5. Enable the following Ciphers and Apply:

  6. Reboot the Orion server.
  7. Run Configuration Wizards. The Services checkbox should be enough.
  8. On SolarWinds Platform versions earlier than 2022.x, complete the following steps:
    1. Open the Global settings page - /orion/admin/advancedconfiguration/global.aspx
    2. Select OverMessageBus in NewPubSubClient settings in Global tab.
    3. Select OverMessageBus in NewPubSubClient settings in Server-specific tab on all affected servers.
    4. Reboot the Orion Services.
  9. Repeat the steps on all Orion servers (on the HA backup of the main polling server if available, then on any additional polling servers, additional web servers, and any other HA servers).