ARTIFACTORY: Why can push replication fail with 405 errors?

AuthorFullName__c
Elina Floim Alper
articleNumber
000005801
FirstPublishedDate
2023-06-27T18:27:57Z
lastModifiedDate
2025-07-20

ARTIFACTORY: Why can push replication fail with 405 errors?

When setting up push replication, we may get 405 errors when trying to trigger the replication. For example:
 

2023-06-21T13:26:35.112Z [jfrt ] [ERROR] [9ac25d36cf12f56c] [o.a.a.c.BasicStatusHolder:209 ] [umer-1687353837498-0] - Error while deploying item 'docker-local:test-image/test1/test2/elina-test/986/sha256__1b7ca6aea1ddfe716f3694edb811ab35114db9e93f3ce38d7dab6b4d9270cb0c on Url:https://TARGET_URL/artifactory/api/docker/test-docker-local ':  [405]


This issue can occur when the target Artifacotry URL that is configured in the replication settings of the repository is set with an api/<package_type> prefix. Unlike pull replication, which requires adding the api/<package_type> prefix to the URL for certain package types, this is not required for push replication. When configuring push replication, the URL of the target local repository on a remote Artifactory server should use the following format:
 

https://ART_HOST/artifactory/<REPO_NAME>