I Gateway apparently cant reach we.frontend.clouddatahub.net

[MuhammadKazim]

So I have a on prem gateway on a windows VM. When I connect to it using Copy Data I am able to connect but when it comes to selecting tables window then this error shows.

Port 443 is open on the VM for inbound and outbound (I used telnet to test). I pinged and telnetted the url mentioned from the VM and both worked fine. I also ran a network diagnostics test from the VM and it gave 31/31 success. However it still gives this error. I tried the same thing with a gateway on my own laptop its working fine. Oddly enough, it shows the columns when i use dataflow gen 2 instead of copy job

[v-pnaroju-msft]

Hi MuhammadKazim,

We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft]

Thankyou @DataGuru412 and @tayloramy for your response.

Hi MuhammadKazim,

We appreciate your inquiry through the Microsoft Fabric Community Forum.

We would like to inquire whether have you got the chance to check the solutions provided by @DataGuru412 and @tayloramy to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

[tayloramy · Accepted solution]

Hi @MuhammadKazim, 

Your screenshot shows the Copy Data table picker failing because the on-premises data gateway on the VM can’t reach the Fabric pipelines frontend for your region: we.frontend.clouddatahub.net. Laptop works > VM doesn’t, which strongly points to outbound network/proxy/TLS inspection or an outdated gateway build on the VM. Dataflow Gen2 can succeed because it often uses a different backend path than the Copy Data wizard.

Quick solution

1. Allowlist the endpoint family
   Ensure outbound HTTPS 443 to *.frontend.clouddatahub.net (and other Fabric URLs for Pipelines). See: Add Fabric URLs to your allowlist.
2. Gateway is outbound-only
   You don’t need inbound opens; focus on outbound 443 and the gateway’s service bus endpoints. See: Gateway communication settings.
3. Update the gateway on the VM
   Install the latest monthly gateway build (old builds often break on newer endpoints/TLS). Supported gateway monthly updates.
4. Proxy/TLS inspection
   If your VM uses a corporate proxy or SSL inspection, configure the gateway to use the proxy and bypass inspection for *.frontend.clouddatahub.net (and other Fabric endpoints). Configure proxy settings for the gateway • Proxy setup guide.
5. TLS 1.2+ and strong crypto
   Confirm TLS 1.2 is enabled and .NET “strong crypto” is on for the VM. See TLS notes in Gateway communication settings.

Why diagnostics and telnet can “pass” but the wizard fails

• The 31/31 network test and telnet :443 only prove a socket can open; they don’t validate DNS, SNI, TLS handshake, cipher, or proxy auth to we.frontend.clouddatahub.net.
• Dataflow Gen2 uses a different path; Copy Data’s table enumeration hits *.frontend.clouddatahub.net, so that specific host must be reachable without interception.

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

[DataGuru412]

Hi,

I faced similar issue earlier in one of workspace and came to know permission issue for service account and my Account. Please, make sure the Gateway connection which you are creating has proper permission.

I hope this may help you.

Thanks 

RJ