Forum Discussion
Gateway Unreachable
All are failing on Scheduled Refresh
All reports work when manually refreshing.
I have checked Gateway Status and I have chcked Connection to SQL Server.
Cluster URIWABI-US-NORTH-CENTRAL-J-PRIMARY-redirect.analysis.windows.net
Activity ID90a01224-d153-4fcb-836b-c4a3d71bd363
Request ID4ea3aefd-6daa-4b58-9b5e-c8e0c2be186a
Time2025-11-22 16:35:01Z
{
"error": {
"code": "DM_GWPipeline_Client_GatewayUnreachable",
"pbi.error": {
"code": "DM_GWPipeline_Client_GatewayUnreachable",
"details": [
],
"exceptionCulprit": 1,
"parameters": {
}
}
}
}
12 Replies
Hi pdolan_tapco ,
Try below things to fix the issue.
1. On the gateway machine: restart the service
On-premises data gateway → Restart
2. Run Diagnostics
Gateway app → Diagnostics → Verify:
Cloud connection = Success
Service Bus = Success
3. Ensure outbound ports are open
Your network/firewall must allow,
443, 5671–5672 and Wildcard domains.
4. Check Gateway Cluster Health
Power BI Service → Settings → Manage Gateways
All nodes must be Online
Remove/disable any "grey" or "Not Connected" nodes.
5. Check if a VPN is active
VPNs often break scheduled refresh because they intercept AMQP.
If using VPN Exclude gateway traffic Or run gateway on a server that is not behind VPN.
If my response as resolved your issue please mark it as solution and give kudos.
thanks for the quick response, I will have my admins check and let you know.
I am getting - ncu.frontend.clouddatahub.net N/A FAILED
pdolan_tapco Perhaps check firewall rules on the gateway server and make sure that the Service is able to contact the gateway. There are a number of troubleshooting steps you can take as well: Troubleshoot the on-premises data gateway | Microsoft Learn
I checked that link, I am pointing to firewall too, Weird error, because I can refresh them manually and I can check the status of the onprem gateway.
I am getting - ncu.frontend.clouddatahub.net N/A FAILED
Hi pdolan_tapco ,
Thank you for reaching out to the Microsoft Fabric Community Forum.
The FAILED result for ncu.frontend.clouddatahub.net means the gateway machine cannot reach a required Power BI Cloud Data Hub endpoint. When this endpoint is blocked, the gateway cannot open the Service Bus channel, which is why scheduled refresh is failing.
Please verify the following on the gateway server:
Allow outbound access to *.frontend.clouddatahub.net and *.servicebus.windows.net.
Ensure ports 443, 5671, 5672 are open with no SSL inspection or proxy filtering.
If you use a corporate firewall, Zscaler, or a VPN, bypass gateway traffic or whitelist all Power BI network endpoints.
After updating the network rules, re-run the Diagnostics. The gateway should report all checks as Success, and scheduled refresh will start functioning normally.
Thank you.
Hi pdolan_tapco ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you.
DNS Gateway was changed on internal server, 1 out of 33 endpoints was found unreachable during diaganostics
Hi pdolan_tapco ,
Thank you for the update. From your note about the DNS gateway change, it seems the issue is related to DNS resolution and not the Power BI Gateway service. To help identify the cause, could you confirm which specific endpoint is still shown as unreachable in the Gateway Diagnostics?
Hi pdolan_tapco ,
We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
If you still require support, please let us know, we are happy to assist you.Thank you.
