Using the latest version?
JFrog Platform User Guide

Skip to end of metadata
Go to start of metadata

The following table lists the set of known issues in Artifactory including the version in which they were discovered, and the version in which they were fixed. Click the issue ID for full details in JIRA.

Issue IDDescriptionAffected From VersionFix Version

Ruby gems connection leak to S3. Check for a non-closed stream that may cause a leak.
RTFACT-22654Unable to pull the images from via Artifactory: When trying to pull Docker images through, Artifactory only gets the manifest.json file and the layers are not downloaded. Only the marker files could be seen in the cache.

When running with Microsoft SQL database, after upgrading to version 6.13, deploying/deleting artifacts/directories and deleting existing repositories will fail with an error.
For example, "Could not check if Repo path '' is related to a Release Bundle"
Private JIRAWorking with Azure blob storage as the Artifactory binary provider, in some cases would result in timeout errors for uploads/downloads6.


Users associated with a group that is configured with admin privileges and additional non-admin group(s), do not have admin privileges.
After upgrading to Artifactory 6.8.0 or above, signing or distributing a Release Bundle from Distribution will fail6.
RTFACT-18524Upgrade will fail if loginBlockDelay is set to

After upgrading Artifactory to 6.6 and above, starting Artifactory can take long period due to index validation in the Oracle database
RTFACT-18502Massive permission target can consume excessive amount of memory6.
RTFACT-16246Import of security configuration file with large number of groups/permissions/users can fail5.

JFrog Artifactory 6.3.0 is not backwards compatible with previous versions for the purposes of distributing release bundles. Therefore, when distributing release bundles between Artifactory services with JFrog Distribution, you need to ensure that either both source and target services are version 6.3.0 and above, or they are both below version 6.3.0.
RTFACT-17418With DB sessions, Artifactory leaves an open transaction after forwarding a servlet request.
RTFACT-17228Mission Control DR security replication functionality is broken for Artifactory due to some security changes in Artifactory and Access (security component)
RTFACT-17060Upgrading to Artifactory 6 will fail if SSL / TLS certificate is configured on one or more of the remote repositories6.

When working with npm repositories, authenticating against Artifactory using the npm login command will fail with the following error in npm:

Registry returned 401 for PUT on <Artifactory URL>/api/npm/<repo name>





When working with the S3 cloud binary provider and the "Storage Quota Control" feature is enabled, in edge cases of multiple concurrent deployments, artifacts deployment may fail.
When working with Helm remote repository that proxies, Artifactory fails to index. Resolving packages from the repository fails.

When performing a System Import on an Artifactory instance running version 5.7 and above, and the folder being imported was exported from Artifactory 5.7.x or 5.8.x, when the import process is completed, Permissions will have not been imported and are missing from Artifactory.

To work around this known issue, and retrieve the Permissions, take the following steps:

  1. In the system export folder (the one you are trying to import), under /etc/access.bootstrap.json, look for the serviceId entry. For example:

    "serviceId" : "jfrt@01c9447sz818ke1cmkcb5z042f"
  2. In the exported folder, create a file named service_id under the following path: etc/security/access/keys/service_id
    In the service_id file, paste the serviceID field found in step 1. e.g: paste jfrt@01c9447sz818ke1cmkcb5z042f

  3. If you have not yet performed the import, you may do so now.
    If you already attempted the import and then discovered this issue, you only need to restart Artifactory and the permissions will be correctly restored.

When upgrading from version below 5.7 to version 5.7 and above while the Artifactory password encryption is enabled, Artifactory will fail to start up with the following error in logs: Couldn't convert configs encryption: javax.crypto.BadPaddingException: Given final block not properly padded : Couldn't convert configs encryption

Running apt-get update on Ubuntu Trusty (14.04) against Debian repositories fails with the following error: Sub-process https received a segmentation fault

For Artifactory HA installations, single-phase upgrades (with downtime) from version 4.x to version 5.6 without going through version 5.4.6 fails. Please refer to the Upgrade Notice in the Artifactory 5.5 Release Notes.
RTFACT-14672Git LFS client v1.x working against Artifactory Git LFS repository using SSH fails to upload or download LFS blobs.

When resolving a package from an npm repository, Artifactory throws a deserialize error to the log file if one of the package's dependencies in the corresponding package.json file is declared using the following format:

“<dependency_name>” : { “version” : “<version_number>” }.

For example: "deep-diff" uses this format. As a result, the npm client fails to resolve the package.

Note: For a workaround, please refer to the issue details.

A system import on a High Availability installation of Artifactory 5.4.x with files exported from a version that is below 5.4, will fail.
RTFACT-14530After upgrading an Artifactory HA cluster from version 5.x to 5.4.x, new nodes that you add to your Artifactory HA cluster will not start up.


Uploading or downloading files to Artifactory using access tokens with a subject that is longer than 64 characters fails with error 500.
RTFACT-14477Artifactory fails to start up when Tomcat is configured to only use HTTPS, or was configured with both HTTP and HTTPS but on different ports.
RTFACT-14495Artifactory is unable to connect to access service and as a result cannot start when Tomcat is configured with a Self-Signed chain certificate.


Following an upgrade from Artifactory version 4.4 or below to 5.3 directly, Artifactory will fail to start up.  
23-May-2017: If upgrading from 4.4 or below, we recommend waiting for a patch which should be released shortly.

Note: Upgrading from version 4.4.1 and above to 5.3 is not affected and Artifactory will start up after the upgrade.
RTFACT-13870Deploying artifacts larger than 100MB in size when using an S3 compatible storage provider can fail leading to unpredictable results.


User Plugins that contain the realms execution point will fail to be executed and throw an HazelcastSerializationException exception when running on Artifactory HA installations., 6.0.1
RTFACT-13923Artifactory might not start up following an upgrade to version 5.x on Windows when Artifactory is configured with a Keystore5.

Most downloaded widget in Artifactory home can cause the DB to stall.
RTFACT-14079When using FullDB or S3 as a binary provider and an NPM virtual repository, external dependencies cause a leak of resources that exhausts all of the DB connections that are never freed.


"downloadTagFile" and "downloadBranchFile" API endpoints throw a nullPointerException when a VCS remote repository has "Store Artifacts locally" disabled4.16.0

When viewing Smart Remote Repositories in the tree browser, folders under the repository that contain a space in their names, will not expand.

RTFACT-8194'docker pull' fails on remote repositories when 'Store Artifacts Locally' is disabled.3.9.0

'npm install' fails when all of the following conditions occur together:

  • You are trying to resolve a scoped package from a virtual repository and,
  • The scoped package is actually hosted under one of the remote repositories aggregated by the virtual repository and,
  • That remote repository has 'Store artifacts locally' disabled.
RTFACT-13004When trying to retrieve an item's properties from Docker V2 repositories using the /api/storage REST API endpoint, a 401 error is returned to the client.3.4.2

Python metadata calculation will fail if the Python metadata version is set to 1.2 inside the METADATA or PKG-INFO files.

NuGet virtual repositories that aggregate more than one local or remote repository may omit results when searching for a package
RTFACT-10132'NuGet install' does not enforce include / exclude patterns on virtual NuGet repositories2.
RTFACT-12959Anonymous users cannot download folders even if anonymous access is enabled.

Uploading a file containing a dot in the target path will fail and a 500 error will be returned to the client

Note: The maven-site-plugin creates upload URLs containing a dot. Therefore, uploading artifacts through the plugin is currently not supported


When all artifacts have been deleted from a folder, the folder is not pushed to the pruning queue even though it is empty, and is, therefore, not deleted.

RTFACT-12260When performing a full system export on an instance with blacked out repositories, and then doing a corresponding import on a target instance, the content and metadata of the blacked out repositories are not imported.2.0.0
RTFACT-9343Promoting Build Info that contains a dependency or an artifact that has the same checksum of an item that already exists may result in a race condition for the same target path.2.0.0

  • No labels