Cloud customer?
Start for Free >
Upgrade in MyJFrog >
What's New in Cloud >


This page provides tips to solve common problems that users have encountered.

Page Contents

JFrog Platform

The following structure is common across all JFrog products.

Folder/File Name


Contains helper scripts for installer.
Contains third party software.
Product specific bundles (for non Docker Compose installers)
Docker Compose templates (only for Docker Compose installers).
Main installer script (for non Docker Compose installers).
Main configure script (only for Docker Compose installers).
Read me file providing the package details.

Depending on the installer type:

  • RPM / Debian Installers: Set the data directory path in the variable JF_PRODUCT_VAR to the customized data folder and start the services. Set the system environment variable to point to a custom location in your system's environment variables files. See Ubuntu System environment variables.

  • Archive Installer: By default, the data directory is set to the unzip-location/var. You can symlink this directory to any folder you want.

  • Docker Compose Installer: Set the JF_ROOT_DATA_DIR variable in the .env file that comes packaged with the installer.

It is recommended to run a health check on the specific JFrog product Router node, which is connected to all the node's microservices. This will provide you with the latest health information for the node.

For example, Platforms's Health Check REST API.

GET /router/api/v1/system/health

Each microservice has its own service log. However, it is recommended to start your debugging process by using the console.log, which is a collection of all service logs of all products in a node. Learn More >

JFrog Artifactory, Insight and Distribution are bundled with Java 11. To customize the Java run time, configure the shared.extraJavaOpts in the system.yaml.

The default ports used by each JFrog Product can be modified in the Product system.yaml file.
For example, to set Artifactory to run on a different port (and not on the default 8081 port), perform the following:

  1. Open the Artifactory $JFROG_HOME/artifactory/var/etc/system.yaml file. 
  2. Add or edit the new port key under the artifactory section.

      port: <your new port, for ex: 8089>


Examples for all the different configuration values, including application ports are available in the $JFROG_HOME/<product>/var/etc/system.full-template.yaml file.

Access Service


During startup, Artifactory fails to start and an error is thrown:

java.lang.IllegalStateException: Provided private key and latest private key fingerprints mismatch.

Artifactory tries to validate and compare access keys' fingerprint that reside on Artifactory's database and the local file system. If the keys do not match, the exception above will be thrown along with the mismatching fingerprint IDs.
This could occur during an attempted upgrade/installation of Artifactory.


Follow the steps below to make sure that all instances in your circle of trust have the same private key and root certificate: 

Key rotation will invalidate any issued access tokens

The procedure below will create new key pairs which in turn will invalidate any existing Access Tokens.

    1. Create an empty marker file called bootstrap.reset_root_keys under $ARTIFACTORY_HOME/access/etc/
    2. Restart Artifactory.
    3. Verify that the $ARTIFACTORY_HOME/logs/artifactory.log or $ARTIFACTORY_HOME/access/logs/access.log file shows the following entry:
    *** Skipping verification of of the root private fingerprint ***
    *** Private key fingerprint will be overwritten ****************

SSL / TLS Issues

Here are some Java options to help troubleshoot SSL/TLS issues in Artifactory:


Reverse Proxy Issues

The error "httputil: ReverseProxy read error during body copy errors" shows up in the logs (console, application logs). The error originates from treafik, and there is no actual affect observed related to these errors.

Access Tokens 

SymptomsAuthentication with an access token doesn't work with an error that says "Token validation failed".
CauseThe implementation of access tokens was changed in Artifactory 5.4. The change is backwards compatible, so tokens created with earlier versions of Artifactory can be authenticated in the new version, however the reverse is not true. Tokens created in versions 5.4 or later cannot be authenticated by versions earlier than 5.4.
ResolutionEither upgrade your older Artifactory instances, or make sure you only create access tokens with the older instances

High Availability


To adjust the active node name and IP on the secondary node after a HA installation, it is recommended to re-run the installation wrapper script. Alternatively, manually modify the following files:

RPM/Debian Installation
  1. $JFROG_HOME/xray/var/etc/system.yaml 
Docker Compose Installation
  1. $JFROG_HOME/xray/var/etc/system.yaml 
  2. <installation folder>/.env
  3. $JFROG_HOME/xray/app/third-party/rabbitmq/rabbitmq.conf



Disk that is storing Elasticsearch data has exceeded 95 % storage

1. Stop the services.

2. Clear space on disk used to store Elasticsearch data.

3. Start the services.

4. Change Elasticsearch indices setting to RW (read-write).

curl -u<username>:<password> -XPUT -H "Content-Type: application/json" http://localhost:9200/_all/_settings -d '{"index.blocks.read_only_allow_delete": null}'

Default username and password for internal Elasticsearch is admin.

Debug Log Configuration

From version 4.x the logback.xml has a different way to enable debug logging.

To configure the Insight log for debug logging:
In the $JFROG_HOME/var/opt/jfrog/mc/etc/insight/logback.xml file, modify the logger name line as follows:

<logger name="org.jfrog.insight" level="DEBUG"/>

Changes made to the logging configuration are reloaded within several seconds without requiring a restart.

Insight Trends Not Displaying

Incorrect Elasticsearch indices used.
  1. Log in to the Insight container.

  2. Disable AUTO_CREATE.

    curl -H 'Content-Type:application/json' -XPUT localhost:8082/elasticsearch/_cluster/settings -d'{"persistent":{"action.auto_create_index":"false"}}' -uadmin:admin
  3. Delete index in Elasticsearch by issuing: 

    curl -XDELETE http://localhost:8082/elasticsearch/active_request_data -uadmin:admin 
  4. Delete index in Elasticsearch by issuing:

    curl -XDELETE http://localhost:8082/elasticsearch/active_metrics_data -uadmin:admin
  5. Delete template.

    curl -X DELETE localhost:8082/elasticsearch/_template/request_logs_template_7 -uadmin:admin
  6. Delete template.

    curl -X DELETE localhost:8082/elasticsearch/_template/metrics_insight_template_7 -uadmin:admin
  7. Stop Insight.

  8. Start Insight.




When running Pipelines install, you receive the following message:

# Setting platform config


Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

The Docker service is not running. This can be verified by running  docker info.


Restart the Docker service:

$ systemctl stop docker
$ systemctl start docker
$ systemctl restart docker
$ service docker restart
$ service docker stop
$ service docker start

Node initialization

check_win_containers_enabled : Windows Containers must be enabled. Please install the feature, restart this machine
and run this script again.

The node does not have containers enabled.


Enable containers for Windows. Run the following in PowerShell with elevated privileges and then restart the machine.

> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
> Enable-WindowsOptionalFeature -Online -FeatureName Containers -All

When initializing a new node, an error in the output states that node is not found. Initialization then fails.


NodeJS is installed, but misconfigured. The error most likely occurred because it was not found in the path.


Uninstall NodeJS and allow the build node initialization to reinstall.

If NodeJS was originally installed as part of node initialization, the following commands should work.

On Ubuntu, CentOS, or RHEL
$ sudo rm -rf /usr/local/bin/node
$ sudo rm -rf /usr/local/lib/node_modules/npm/
On Windows
> choco uninstall nodejs

Pipelines Error Messages

This section lists commonly-encountered Pipelines error messages, possible causes, and some suggestions for resolving the errors. If you have trouble fixing any of these errors, submit a request to Support for further investigation. 

Error: All resource versions are not fetched

All resource versions are not fetched. Requested resource versions: 16; received resource versions: []

After the run was triggered, but before it started running, one or more resources in the pipeline were reset. Hence, while fetching the resources associated with the run, the resource version was returned as an empty array.


Re-run the pipeline. 

When a resource is reset, it wipes out the resource version history and resets it to a single version, which is now considered the latest. This version is used for the new run.

Error: fatal: reference is not a tree

fatal: reference is not a tree: 679e2fc3c2590f7dbaf64534a325ac60b4dc8689

This could be a result of using git push --force  or  git rebase , which deletes the commit and causes the pipeline to not run.



  • Reset the resource and then trigger the pipeline again. Note that if there are several GitRepo resources in the pipeline, this needs to be done for all of them.


  • Push another commit so that all the resources are updated automatically.

Error: Failed to create pvc for node

Failed to create pvc for node

Either the Kubernetes configuration does not have access to create a Persistent Volume Claim (PVC) resource or Pipelines cannot connect to the provided Kubernetes host server.


Review the Kubernetes configurations and verify that the Kube Config provided while creating the Kubernetes Integration has adequate permissions.

Error: SCM provider credentials do not have enough permissions

The credentials provided for the integration "<integration_name>" do not have enough permissions. Ensure that the credentials exist and have the correct permissions for the provider: github.

The credentials (username and/or token) provided while creating the integration are either incorrect or insufficient.


Ensure that the credentials provided for the SCM provider are correct and have sufficient permissions.

Error: SCM provider URL is invalid

The URL provided for the integration “<integration_name>” is invalid. Provide a valid URL for the SCM provider and try again.

The SCM URL provided while creating the integration is incorrect.


Ensure that the URL provided for the SCM provider is correct.

Error: SCM provider repository path is invalid

The repository path "<repo_path>" is either invalid or does not exist. Ensure that the repository path exists and has the correct permissions for the integration: <integration_id>.

The repository path provided for the SCM provider is either incorrect or does not exist.


Ensure that the repository name provided for the SCM provider is correct.

Error: Step type cannot be updated

type cannot be updated from <step_type> to <step_type> in step <step_name>

Example: build/ci/pipelines.yml: type cannot be updated from Bash to Matrix in step e2e_local_tests


After the pipeline performs a sync, a step's type should not be modified, as it can cause pipeline sync errors.


Though not recommended, if you do want to change a step's type, perform the following steps:

  1. Change the step's name and type
  2. Wait for pipeline sync
  3. After the sync completes, change the step's name back to the old name

Error: Ubuntu 16.04 not supported

Ubuntu_16.04 has reached end of support. Please upgrade to a higher version.

Ubuntu Linux 16.04 LTS reached the end of its five-year LTS window on April 30th 2021 and is no longer supported by its vendor. Due to this, Pipelines no longer supports your existing Ubuntu 16 node pools.

  • Dynamic Node Pools: Existing Ubuntu 16 dynamic pools will be automatically migrated to Ubuntu 18 provided those were created with the default build plane images. If you have any custom Ubuntu 16 node pools, they must be manually migrated to Ubuntu 18 or higher. 
  • Static Node Pools: Upgrade all your existing Ubuntu 16 static node pools to Ubuntu 18 or higher.

For information about the supported Ubuntu versions, see the System Requirements Matrix.

Error: CentOS 8.0 not supported

CentOS 8 has reached end of support. Please change the OS to another supported version. For the list of supported versions, see System Requirements.

CentOS 8.x reached end-of-life is on December, 2021 and is no longer supported by its vendor. Due to this, Pipelines no longer supports your existing CentOS 8 node pools.

  • Dynamic Node Pools: Existing CentOS 8.x dynamic pools will be automatically migrated to CentOS 7.0 provided those were created with the default build plane images. If you have any custom CentOS 8.x node pools, they must be manually migrated to either CentOS 7.0 or a different OS. 
  • Static Node Pools: After upgrading to the next major release of Pipelines, either remove any CentOS 8.x node pools or change the machine image to a different OS. 

For the list of supported OS versions, see System Requirements.

Error: postHook returned error 422

Failed to sync hook with err: Webhook creation failed for path: userName/repoName and integration: myGithub with err: postHook returned error 422 for userName/repoName

This is usually the result of too many webhooks.  GitHub allows 20 webhooks per repository.


In GitHub, go to the Settings | Webhooks tab for the relevant repository and delete all the failed webhooks.

Error: Connection was not successful

Connection was not successful

One of the reasons for this message to appear is when the Artifactory/Distribution URL provided for the integration is incorrect.


Verify that your Artifactory/Distribution URL provided for the integration is correct. If you find that it is incorrect, update the URL and use the Test Connection button to verify, and then save.

  • No labels
Copyright © 2023 JFrog Ltd.