
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 233 Views
dnf update throwing the error
Dear RHEL SMEs,
I need assistance on the dnf update. the server is running with RHEL 8.2 and behind a corporate proxy server. Is there any way to work around the port 1080 ( SOCKS Proxy port). can we use a 443 or 80 instead of 1080. Kindly advise the resolution steps. Thanks.
Upendar
# dnf update
Updating Subscription Management repositories.
This system is registered to Red Hat Subscription Management, but is not receiving updates. You can use subscription-manager to assign subscriptions.
Red Hat Enterprise Linux 8 for x86_64 - BaseOS (RPMs) 0.0 B/s | 0 B 00:00
Errors during downloading metadata for repository 'rhel-8-for-x86_64-baseos-rpms':
- Curl error (7): Couldn't connect to server for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/baseos/os/repodata/repomd.xml [Failed to connect to proxy.example.net.au port 1080: Connection refused]
Error: Failed to download metadata for repo 'rhel-8-for-x86_64-baseos-rpms': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
#

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 27 Views
My Linux skills are rusty but I believe that technically, it’s possible to work around the SOCKS proxy limitation by using an HTTPS proxy over ports like 443 or 80. That said, it really depends on whether the HTTPS proxy is available in your environment and if IT Security permits this kind of traffic for package updates. Some setups block outbound package manager traffic, even on standard ports, depending on policy.