Query regarding Smart proxy with foreman

Problem: Query regarding Smart proxy with foreman

**Expected outcome:**Able to connect multiple foreman proxy servers with foreman

**Foreman and Proxy versions:**Foreman 3.13 with Katello 4.15

**Foreman and Proxy plugin versions:**Foreman 3.13 with Katello 4.15

Distribution and version: Rocky 9

Other relevant data:

We have a foreman setup with one foreman with two foreman-proxy servers(foreman-proxy1 and foreman-proxy2).

Foreman and foreman-proxy1 servers are in same location and foreman-proxy2 server is in another location. We have configured both proxy servers with same commands. We have done the sync from foreman server to foreman-proxy1 and could see the pulp storage utilization. But when I try to do the sync from foreman server to foreman-proxy2 server, I am getting error as “Last sync failed: There was an issue with the backend service pulp3: Timed out connecting to server” and could see in pulp storage with the error " Oops, we’re sorry but something went wrong foreman-proxy2 is unreachable. Timed out connecting to server".

Please let us know anything required for further.

Hi…

Could you please help us on this query.

This sounds like some basic networking issues. You should make sure that routing between smart-proxy2 and the main Foreman server is setup correctly in both ways and review the port and firewall requirements from the docs to ensure all the required ports are open on your (host and network) firewall. From the error message you posted, I would assume that port 9090 from Foreman to the smart-proxy is blocked.

We have checked from network end and we could see everything looks good. We have used the same commands which we used to configure smart-proxy1 for smart-proxy2. Is anything we can check for this issue? please let us know any other logs required for the same.

You should check the following logs for anything suspicious:

  • /var/log/foreman-proxy/proxy.log (depending on you configured loglevel, this might very well be empty)
  • journalctl -u 'pulpcore-api' there should be some requests to status and repository endpoints when the sync starts
  • journalctl -u ‘pulpcore*’ if the rest looks good.