// troubleshooting guide · microsoft power bi
Power BI Gateway Offline or Could Not Be Reached
- Status
- Workaround available
- platforms:
- Windows (gateway), Power BI service
- updated:
- November 16, 2026
- reports:
- 4
- Method
- how we research
RUNBOOK · power-bi/gateway-offline5 FIXES
// quick answer
This error means the Power BI service cannot reach your on-premises data gateway. Start or restart the 'On-premises data gateway service' on the gateway machine, update it, and make sure outbound port 443 to Power BI isn't blocked.
Most likely fix: Restart the gateway service
How to fix it
// try these in order, the most common fix is first
FIX 1Restart the gateway service
- 01Sign in to the gateway machine
- 02Open services.msc
- 03Find On-premises data gateway service, then Start or Restart it
- 04Check in the Power BI service that the gateway shows as online
Did this fix it?FIX 2Keep the machine awake and online
- 01Disable sleep and hibernation on the gateway host
- 02Use a server or always-on VM, not a laptop
Did this fix it?FIX 3Update the gateway
- 01Download the latest on-premises data gateway installer from Microsoft
- 02Run it over the existing install
- 03Sign in and keep the same gateway name
Did this fix it?FIX 4Open the network path
- 01Allow outbound port 443 from the gateway machine
- 02Allowlist Power BI endpoints in your proxy, firewall or tools like Zscaler
- 03Run the network test in the gateway app's Diagnostics tab
Did this fix it?FIX 5Check the data source itself
- 01From the gateway machine, confirm the SQL server, file share or ODBC source is reachable
- 02Fix source outages before retrying refresh
Did this fix it?
SANDBOX · power-bi RUNS IN YOUR BROWSER
Try it: browse a sample shop and watch visitors, funnels and live data arrive
A hands-on Microsoft Power BI-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.
Symptoms
Errors like 'The gateway is either offline or could not be reached', DM_GWPipeline_Gateway_Unreachable or GatewayNotReachable when refreshing or setting credentials.
Why it happens
- C-01Gateway machine is turned off, asleep or lost internet
- C-02The gateway Windows service stopped
- C-03Outdated gateway version (only the last six releases are supported)
- C-04Firewall, proxy, VPN or SSL inspection blocking outbound traffic
// this guide also covers
- power bi gateway offline
- the gateway is either offline or could not be reached
- dm_gwpipeline_gateway_unreachable
- power bi gateway not working
Still not working?
If Microsoft Power BI keeps failing, you're not alone. See every Microsoft Power BI problem users report or the alternatives people switch to.
Done fighting Microsoft Power BI? Our small team builds your own Microsoft Power BI alternative, or any software you need: web, mobile, games, desktop. Price agreed together.
Talk to usThe same problem in other apps
All not loading, error messages & connection guides →
Tableau "Unable to Start Due to an Internal Licensing Error" (Tableau)
Looker Studio GA4 Quota Exceeded Error (Looker Studio)
Metabase Dashboard Slow or Not Loading (Metabase)
Superset Dashboard Slow or Charts Timing Out (Apache Superset)
Other Microsoft Power BI errors
- Power BI Scheduled Refresh Failed
- Why Is My Power BI Report So Slow?
- Power BI Desktop Refresh and Power Query So Slow
- Power BI Desktop Not Opening or Stuck on Splash Screen
- Can't Sign In to Power BI Desktop
- Power BI Visual Has Exceeded the Available Resources
- Power BI Error: The Key Didn't Match Any Rows in the Table
- Power BI DataFormat.Error: We Couldn't Convert to Number