Hi item found using search api but can’t be deleted or read ( returns 404) when using assets api. our asset is a raw asset Sometime it does work, but mostly it doesnt. see below - query the same asset 3 times with no quote, double quote and single quote - all returning 404. curl -u ‘…’ -X GET…

Hi Ori Keren, You are getting 404 Not Found response when trying to get or delete an asset, because that asset does not exists in your repository. However, you keep seeing the asset in your search results, because your search index might be out of date. Please run “Repair - Rebuild repository sear…

thanks Dawid for answering I will ask the nexus owner to repair the indexes , still , can it be that I can see the same artifact in the UI, but still have a 404 when trying to delete it using the api? For the above example - I can see price-managementhook/price-managementhook-2012.12.1-3.tgz in t…

If you have a paid licence you can open a support ticket, so we can take a look at what’s happening on your Repository instance.

I will check with our IT team about licensing today I saw a similar case which ended with a 405 error, the search API worked ok and returned the ID, the object is also visible in UI. Can you share why 405 is thrown here ? “path” : “account-financialaccounthook/account-financialaccounthook-2109.13…

I don’t believe that NXRM will throw a 405 based on the url you are showing and what the REST API says. It’s possible you are getting blocked by a proxy server (ie nginx). Check the sonatype-work/nexus3/log/request.log to ensure that your request is actually reaching the nexus instance. If it is you…

Hi There is no proxy present between the two machines, the search api as well as deletion of docker images and even certain Delete assets (few) calls do pass without problem, majority of the delete assets call that I generated in script (first run search, next build the delete assets call based o…

Hi we checked Nexus request logs - the requests are there, we also checked the general nexus.log - nothing is showing in the case of 405 error I also tried to use the GET asset API for the same ID which I received using the search API, this is resulting in 404 error (not found) last thing we did…

Nexus 3 inconsistent api results

Sonatype Nexus Repository

orik318 (Ori Keren) August 18, 2022, 1:26pm 9

the 405 issue is now resolved - there was a typo in the URL
issue resolved

Topic		Replies	Views
Nexus 3 rest api for delete asset returns 405 error Sonatype Nexus Repository	1	1238	August 11, 2022
Search returns unavailable component Sonatype Nexus Repository maven	1	1421	March 12, 2020
Sonatype Nexus Repository Components and Assets API Issues Sonatype Nexus Repository help , nexus-repository , api	2	473	February 7, 2024
Search using search api sometimes results in empty responses Sonatype Nexus Repository	7	2578	November 16, 2022
REST API - Finding asset by asset ID fails Sonatype Nexus Repository help , rest	3	4879	August 8, 2018

Nexus 3 inconsistent api results

Related topics