Redhat proxy repo continually times out waiting for pool connection

Hi, Im using OSS 3.66.0-02 and it seems like, we have below issue, and I’m not sure what’s causing it. Nexus health checks indicate that it couldn’t reach the Red Hat registry at registry.access.redhat.com.

2024-08-14 16:29:36,053+0200 INFO  [qtp312409770-2347]  *UNKNOWN org.sonatype.nexus.repository.httpclient.internal.HttpClientFacetImpl - Repository status for redhat-proxy changed from AVAILABLE to AUTO_BLOCKED_UNAVAILABLE until 2024-08-14T16:30:16.053+02:00 - reason java.net.SocketTimeoutException: Read timed out for https://registry.access.redhat.com
2024-08-14 16:29:36,054+0200 WARN  [qtp312409770-2347]  *UNKNOWN org.sonatype.nexus.repository.docker.internal.orient.DockerProxyFacetImpl - Exception java.net.SocketTimeoutException: Read timed out checking remote for update, proxy repo redhat-proxy failed to fetch v2/_catalog, content not in cache.

Could you please clarify what is missing?

That doesn’t suggest a connection pool to me, the error suggests that Nexus cannot connect to the remote registry due to a networking issue.

@mpiggott We can reach https://registry.access.redhat.com from nexus server, so it dont think there is a network issue. The timeout exception occurs when i configured as proxy repo in nexus