The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hello community,
We have today upgraded our on-prem data gateway as requested, but after update we found certain ports need now to be opened in our company's firewall in order to establish a connection between the gateway and the Power BI service.
We are now starting the requried internal approval process that could take a few days to complete.
Our problem is now we cannot roll back to prior gateway version which is rendering the service useless given we have no way to connect to our SSAS Tabular data models for refresh.
Any idea of how we could go about rolling this back until we can get the firewall ports opened?
Appreciate your help and guidance.
Esteban
Solved! Go to Solution.
We worked with IT to have the ports opened and IP addresses whitelisted and now the gateway is working ok.
Thanks,
Esteban
Hi @Anonymous
Here is the link that details all the ports that are required to be opened.
https://powerbi.microsoft.com/en-us/documentation/powerbi-gateway-onprem/
As well as further down there is a section where you can force the Power BI Gateway to use HTTPS but it will be a bit slower.
Forcing HTTPS communication with Azure Service Bus
hi @GilbertQ,
We did try that but did not work ... even though we force it to use HTTPS through port 443, it still tries to use 9*** ports which are closed in our firewall.
Is there a way we can install the older version of the gateway that did work up until yesterday when we started the upgrade?
Thanks,
Esteban
We worked with IT to have the ports opened and IP addresses whitelisted and now the gateway is working ok.
Thanks,
Esteban