Issue setting up Octopus feed for Nexus Docker Registery

I’m trying to set Docker Container Registry feed.
I’m using Sonatype Nexus Repository ManagerOSS 3.38.1-01 as a Docker Registry and
Octopus v2022.1 (Build 2584)

The feed test is returning
“No connection could be made because the target machine actively refused it. (nexus:<portNumber>) No connection could be made because the target machine actively refused it.”

I know there is no issue with the Nexus Docker Registry as I’m able to pull images from it.
The Octopus servers has no firewall issue as https://<nexusUrl>/v1/_ping connection returns 200 status on the servers.

Do you have any suggestion on how to analyse this issue?


Thanks for reaching out on our community forum! This seems a bit tricky as normally, that error means firewall issues or that no services are running on the specified port. I know you mentioned the Octopus server having open firewall settings, but you may also need to check the Nexus server firewall settings. You might need to whitelist the Octopus server IP address.

Also, what port is your docker registry on? If the firewalls are not the issue, the port could be. The Sonatype documentation uses port 18080 in the docker registry examples, so if your ping and Octopus feed setup is pointed to just https://nexusUrl, which would be (443), that might explain why you see that error.

Hopefully, that helps get you pointed towards the solution, let us know how you progress.


This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.