RHEL 7.6 EUS repo sync showing error 502 proxy error

Problem:
We have build a new foreman server version 2.3.2 Katello 3.18, when we are syncing RHEL repos all repos are synced successfully, except few showing below error. Although we do not have any proxy in our environment and I ran below command to configure foreman

foreman-installer --scenario “katello” --foreman-initial-admin-username admin --foreman-initial-admin-password redhat --foreman-initial-organization “xxxx” --foreman-initial-location “xxxx” --foreman-proxy-dhcp “false” --foreman-proxy-dns “false”

PulpRpmClient::ApiError: Error message: the server returns an error
HTTP status code: 502
Response headers: {“date”=>“Tue, 26 Jan 2021 21:39:17 GMT”, “server”=>“Apache”, “content-length”=>“445”, “connection”=>“close”, “content-type”=>“text/html; charset=iso-8859-1”}
Response body:

502 Proxy Error

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /pulp/api/v3/content/rpm/packages/.

Reason: Error reading from remote server

Expected outcome:

Repo Sync complete successfully

Foreman and Proxy versions:

foreman-release-2.3.2-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_docker-0.0.7-1.el7.noarch
tfm-rubygem-foreman-tasks-core-0.3.4-1.fm2_1.el7.noarch
z1foreman02.mocr-nt1.otsuka.com-foreman-proxy-client-1.0-1.noarch
tfm-rubygem-foreman_virt_who_configure-0.5.5-1.fm2_3.el7.noarch
z1foreman02.mocr-nt1.otsuka.com-foreman-client-1.0-1.noarch
foreman-debug-2.3.2-1.el7.noarch
foreman-installer-2.3.2-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.15-1.fm2_2.el7.noarch
tfm-rubygem-foreman-tasks-3.0.2-1.fm2_3.el7.noarch
z1foreman02.mocr-nt1.otsuka.com-qpid-client-cert-1.0-1.noarch
z1foreman02.mocr-nt1.otsuka.com-qpid-router-client-1.0-1.noarch
foreman-installer-katello-2.3.2-1.el7.noarch
rubygem-foreman_maintain-0.7.1-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.3.0-1.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.4.0-1.el7.noarch
z1foreman02.mocr-nt1.otsuka.com-qpid-broker-1.0-1.noarch
foreman-2.3.2-1.el7.noarch
z1foreman02.mocr-nt1.otsuka.com-foreman-proxy-1.0-1.noarch
foreman-postgresql-2.3.2-1.el7.noarch
z1foreman02.mocr-nt1.otsuka.com-puppet-client-1.0-1.noarch
tfm-rubygem-hammer_cli_foreman_virt_who_configure-0.0.7-1.el7.noarch
foreman-dynflow-sidekiq-2.3.2-1.el7.noarch
foreman-proxy-2.3.2-1.el7.noarch
z1foreman02.mocr-nt1.otsuka.com-apache-1.0-1.noarch
foreman-cli-2.3.2-1.el7.noarch
katello-ca-consumer-z1foreman02.mocr-nt1.otsuka.com-1.0-1.noarch
tfm-rubygem-hammer_cli_foreman-2.3.0-1.el7.noarch
tfm-rubygem-foreman_remote_execution-4.2.1-1.fm2_3.el7.noarch
z1foreman02.mocr-nt1.otsuka.com-qpid-router-server-1.0-1.noarch
tfm-rubygem-foreman_virt_who_configure-doc-0.5.5-1.fm2_3.el7.noarch
foreman-service-2.3.2-1.el7.noarch

Foreman and Proxy plugin versions:

Distribution and version:

RHEL 7.9

Other relevant data:

Did the proxy error got resolved?
I am facing the same issue,Do you know what is the reason of this issue?