Cannot create Maven - Delete SNAPSHOT Task

Sonatype Nexus Repository
1

Hi,

I’m trying to create a task to delete Maven snapshots using Nexus 3.84.1. Specifically, I’m trying to use the “Maven - Delete SNAPSHOT” task.

When I go to select a repository, the UI shows a “Loading” spinner, but never actually shows a list of repositories:

Screenshot 2025-09-24 at 16.30.36
Screenshot 2025-09-24 at 16.30.361758×1168 163 KB

Eventually, the UI times out with the error: “Operation failed as server could not be contacted”

Screenshot 2025-09-24 at 16.36.58
Screenshot 2025-09-24 at 16.36.58836×178 11.3 KB

I see the same problem if I try to create a task of type “Maven - Delete unused SNAPSHOT”, but I am able to create other Maven tasks like “Repair Base Version” successfully - the list of repositories loads fine there. So perhaps the problem is specific to tasks require a repository that can contain SNAPSHOT versions.

I’ve tried simply typing the identifier of the repository I want to use in the input field (i.e. “snapshots”), but the text disappears and is replaced by a placeholder when I switch focus to the next field.

Is there anything I can do to repair the instance so that I can select a SNAPSHOT repository and create the task? I’ve seen this feature work on another instance of the same version, so it seems to be something wrong with the data itself.

Thanks,
Martin

2

I’d suggest examining the nexus log for any errors, and examine the request.log to see if it contains a request or whether it is being blocked by a browser extension, firewall, or proxy.

3

Thanks, Matthew. I should’ve also mentioned that I’d checked without a proxy and without any browser extensions.

I was sceptical about your suggestion of a firewall because I’m not aware of anything relevant, but I set up SSH port forwarding, forwarding a port on my local machine to Nexus, and pointed the browser at that. And sure enough, that works!

So, it’s clearly something on the network interfering and not Nexus, and I have a workaround, even if I don’t know what’s blocked it or why (the request and response seem quite mundane).

I said that I’d seen it working on a different instance of the same version… but that was on a local VM, so I didn’t have the same issue there.

Thanks again.