Cannot ping endpoint not on port 443 when creating a new Registry Endpoint

[h2cone]

Hello,

I have deployed two Harbor instances, for example https://harbor.foo.com and https://harbor.bar.com:65345, and both instances can reach each other on their respective networks. When I log in as admin to https://harbor.foo.com, go to "Registries" to create a new endpoint, and set the URL to https://harbor.bar.com:65345, after submitting the form I receive a "Failed to ping endpoint" error.

My Harbor version is 2.9.5. The error logs are:

2025-01-08T01:30:16Z [ERROR] [/pkg/reg/adapter/native/adapter.go:126]: failed to ping registry https://harbor.bar.com:65345: Get "https://harbor.bar.com/service/token?service=harbor-registry": dial tcp 112.11.77.146:443: i/o timeout

Did I miss something?

Thank you!

[wy65701436]

how did you deploy the harbor instances? through docker compose or helm chart? Did you validate the connection between harbor-core of https://harbor.foo.com and the harbor-core of https://harbor.bar.com:65345?

[h2cone]

how did you deploy the harbor instances? through docker compose or helm chart? Did you validate the connection between harbor-core of https://harbor.foo.com and the harbor-core of https://harbor.bar.com:65345?

Thank you for your comment. We deployed using Docker Compose, and within the container harbor-core at https://harbor.foo.com, we can successfully access https://harbor.bar.com:65345 using curl.

[chlins]

@h2cone Please check the value of the field externalURL in the harbor.yml for the instance of https://harbor.bar.com:65345.