Port 443 is fail

Question

Tried to install CRC Setup but it is showing fail

error:
ERRO unable to get verified hash for default bundle: Get "https://mirror.openshift.com/pub/openshift-v4/clients/crc/bundles/openshift/4.21.8/sha256sum.txt.sig": dial tcp: lookup mirror.openshift.com on [2401:4900:50:9::18d]:53: dial udp [2401:4900:50:9::18d]:53: connect: An attempt was made to access a socket in a way forbidden by its access permissions.

Please help me for this

Answer 1

Hello Clary,

Thank you so much for your response.

I checked and found that the anti-virus firewall needs to disable.

Thank you

[Moderator Note: Personal Info Removed]

Answer 2

Hi Prudhvi Sankurubotu,

I can also see that the Q&A Assist has already suggested some helpful suggestions. Please do take a moment to go through those steps and see if any of them make a difference.

In addition, may I also ask how you downloaded the CRC installer, for example, was it downloaded directly through a browser or via a specific tool?

It would also be helpful to know whether you’re experiencing similar issues when downloading other applications or accessing external sites. If the issue occurs with multiple downloads, it could further indicate a network or DNS-related restriction rather than something specific to CRC.

Please feel free to share any updates and I’ll be happy to assist further.

---

If you have additional questions about this answer, please click "Comment".

Note: If you want to receive email notifications about this thread, follow the steps in our documentation to enable email notifications.

Answer 3

The error indicates that Windows is blocking DNS/HTTPS traffic rather than a problem with the CRC installer itself. Port 443 and DNS (port 53) must be reachable.

Use these steps to troubleshoot on Windows 11:

1. Verify nothing else is using port 443
   • Open Windows Terminal or PowerShell as Administrator.
   • Run:

          netstat -ano | findstr :443
     

   • If another process is bound to 443 and interfering with outbound HTTPS, stop or reconfigure that software.
2. Check local firewall rules
   • Open Windows Security → Firewall & network protection → Allow an app through firewall.
   • Ensure the CRC installer (or the shell used to run it) is allowed for Private and Public networks.
   • If needed, temporarily turn off Microsoft Defender Firewall for the active network profile to test. If CRC works with the firewall off, add an allow rule for CRC and turn the firewall back on.
3. Check for security software or TLS‑inspecting proxy
   • If an antivirus, endpoint protection, or corporate proxy is installed, it may block or inspect HTTPS and DNS traffic.
   • Temporarily disable HTTPS inspection / web protection in that product and retry the CRC setup.
   • If using a corporate proxy, ensure it allows outbound HTTPS to external sites and is correctly configured in Windows and for CRC.
4. Confirm DNS and HTTPS connectivity from the machine
   • Open Windows Terminal and run:

          nslookup mirror.openshift.com
     

     If this fails, DNS is blocked or misconfigured.
   • Then test HTTPS reachability (example using curl if installed):

          curl -v https://mirror.openshift.com/ -o nul
     

     If connection is refused or times out, network/firewall is blocking outbound 443.
5. Check that no local service is conflicting with HTTPS
   • Ensure no local reverse proxy or cache is misconfigured on port 443. On systems using HTTPS services, verify they are correctly configured and not blocking outbound traffic.

Once DNS resolution (port 53) and HTTPS (port 443) work from the machine, rerun the CRC setup; the bundle hash download should succeed.

---

References:

• Validate HTTPS Configuration for Microsoft Connected Cache on Linux
• Troubleshoot Microsoft Connected Cache for Enterprise and Education