XRAY: How to remove the message "JFrog Xray is unavailable. For details, please check Artifactory's log files”

AuthorFullName__c
Marwa Sharif
articleNumber
000005642
FirstPublishedDate
2023-03-21T13:37:57Z
lastModifiedDate
2025-07-28

XRAY: How to remove the message "JFrog Xray is unavailable. For details, please check Artifactory's log files”

This article aims to discuss the recurring error message that reads "JFrog Xray is unavailable. For details, please check Artifactory's log files." This error will persistently appear in the Artifactory User Interface, even with the Xray node disabled or removed from the topology.

This issue might occur if there are any configuration details of Xray remain in the artifactory.config.latest.xml file which resides in the $JFROG_HOME/artifactory/var/etc/artifactory folder. 

Nevertheless, to remove this message, you can perform the following two options below:

Option 1:

Navigate to artifactory.config.latest.xml file found inside path $JFROG_HOME/artifactory/var/etc/artifactory and change "enabled" from "true" to "false" under the xrayConfig.

Rename the file from “artifactory.config.latest.xml” to “artifactory.config.import.xml” and then restart the Artifactory instance for the changes to take effect.
NOTE: If you have an HA cluster, please ensure to restart each node.

Option 2:

In Artifactory UI by navigating to the Admin tab | Artifactory | Advanced | Config Descriptor, then search for the <xrayConfig> tag and change "enabled" from "true" to "false" as shown below to resolve the issue of removing the Xray message.

  <xrayConfig>
        <enabled>false</enabled>
        <baseUrl>http://localhost:8046/xray/</baseUrl>
        <user></user>
        <password></password>
        <artifactoryId>default</artifactoryId>
        <xrayId></xrayId>
        <allowDownloadsXrayUnavailable>false</allowDownloadsXrayUnavailable>
        <allowBlockedArtifactsDownload>false</allowBlockedArtifactsDownload>
        <blockUnscannedTimeoutSeconds>60</blockUnscannedTimeoutSeconds>
    </xrayConfig>


For more information, you may refer to this page.