пробовал тоже ошибка 404

у тебя рест апи вообще работает?

Кто отдает 404

/usr/bin/curl -X GET -u robot-developer:<my_pass> https://my.nexus/service/local/status

Вот это что нить отдает?

да ту же ошибку 404

а так если
/usr/bin/curl -X GET -u robot-developer:<my_pass> https://my.nexus/service/local/status -I -H "User-Agent: curl/"

так же все 404 ошибка

HTTP/1.1 404 Not Found
Server: nginx/1.14.2
Date: Wed, 05 Aug 2020 17:00:37 GMT
Content-Type: text/html
Content-Length: 1891
Connection: keep-alive
X-Content-Type-Options: nosniff
Pragma: no-cache
Cache-Control: no-cache, no-store, max-age=0, must-revalidate, post-check=0, pre-check=0
Expires: 0
X-Frame-Options: DENY

The intent of the 404 is so that anonymous users with no permissions to a repository that exists inside of NXRM can learn of its existence, and then perhaps attempt to perform some other exploit against it.

We will review this issue again internally, but if you can explain why returning 404 when anonymous access is disabled is causing a problem, that would help us decide if we have cause to change this.

а у тебя какая версия нексуса?

почти свежайшая

I’m having this same issue on OSS 3.24.0-02, including using the latest Docker image and we’re not attempting to use NXRM3 in any way, yet this error is cropping up and causing our Nexus server to go offline for circa 10 minutes at a time.

2020-06-09 17:38:55,019+0000 WARN [qtp22457663-656] *UNKNOWN org.sonatype.nexus.siesta.internal.WebappExceptionMapper - (ID 915b162b-d3c9-4fa1-8f04-109b2534a5a6) Response: [404] (no entity/body); mapped from: javax.ws.rs.WebApplicationException: Path not found

пишут че то про лицензию

логи то посмотри

что пишет про этому поводу нексус

ок спасибо гляну

к стате

а апишка то у тебя на каком порту висит?

в примерах просто вот такое curl -X GET http://localhost:8081/service/rest/v1/status

веб морда   если на 80