Couldn't find a good place to submit this question. It's basically just to see if anyone else has had the problem or if it's just me!
I use StarLink as my internet provider because I am on the road full time. Prior to June 7th (the date the new cloud API went into effect for the Power Platform) I had no issues. Now that the move has completed, I can no longer use StarLink when working on PowerApps. I have to use my LTE modem, the RV Park WiFi or as a last resort, my phone as a hotspot. Connecting with ANY of those three gives me no trouble when working on PowerApps. But the second I switch back to StarLink, I get an error about not being able to connect to my data. I switched over to StarLink for a teleconference yesterday and forgot to switch back to one of the others after it ended. Went back to work on my app. Worked for about five hours and then tried to publish. Nothing happened. Saved and exited, but then realized why it wouldn't publish. Switched back over to a working ISP and all my work was gone.
Does anyone else use StarLink as their ISP and if so, have you had this issue and how did you fix it???
This is due to issues where the default DNS the Starlink ISP provides to users isn't resolving Power Platform API domains. There is a workaround by configuring the user's Starlink router with a overridden DNS (Such as https://www.cloudflare.com/learning/dns/what-is-1.1.1.1/ or https://developers.google.com/speed/public-dns/docs/using) that will allow experiences using Power Platform to work as expected.
Also just tried this and seems to have resolved this.Thanks!!
Added the Google DNS servers (8.8.8.8, 8.8.4.4) to the custom DNS settings on the StarLink router and that seems to have resolved the issue after a router reboot.
Thanks!
I was able to fix this by switching to Google's IPv6 servers...it's possible that starlink ran out of IPv4 addresses, and there's a problem with the IPv6 DNS.
If you go to Control Panel-> Network and Sharing -> Change adapted settings -> Right click adapter -> Properties -> Internet Protocol Version 6 (TCP/IPv6) -> Use the following DNS Servers:
2001:4860:4860::8888
2001:4860:4860::8844
This fixed the problem for my boss.
Based on the reports I have seen the issues may be related to DNS lookups failing using StarLinks DNS for *.environment.api.powerplatform.com or *.tenant.api.powerplatform.com domains when using the default DNS settings provided by Starlink. You might be able to use you browsers developer tools to see messages in the console like:
You could then take the domain and try doing a lookup using the nslookup command.
For example running:
nslookup <some-id-from-the-log>.environment.api.powerplatform.com
which should return something like:
Server: one.one.one.one
Address: 1.1.1.1
Non-authoritative answer:
Name: tstil201wusga.westus.cloudapp.azure.com
Address: 20.245.152.248
Aliases: <some-id-from-the-log>.environment.api.powerplatform.com
ppapigw.us-il301.gateway.prod.island.powerapps.com
apigw-prdil301-us.trafficmanager.net
ppapigw.wus-il301.gateway.prod.island.powerapps.com
igw.wus-il301.gateway.prod.island.powerapps.com.privatelink.powerplatform.com
prdil301wusigw-tm.trafficmanager.net
but if your DNS servers aren't working correctly you might get something like
Server: <some-server>
Address: <some-address>
** <some-server> can't find <some-id-from-the-log>.environment.api.powerplatform.com: Unspecified error
If this is the case and things are working as expected when connected to other ISPs you may be able to work around the issue by changing your StarLink routers configured DNS and there are some popular free alternative DNS servers that may work better for you.
Use the $Response in PowerShell not the Command prompt, It looks like something is blocking the data access apis when accessed via StarLink. This is interesting, can you open a ticket with support and share the ticket number please.
Hi Kartikka,
Thanks for the response.
I do not have access to my work network's firewall settings. However, the issue happens on my personal laptop when connected to my StarLink router as well, so it can't be an issue with work firewall. There are no editable settings in the StarLink router that deal with firewall settings.
I am able to ping make.powerapps.com, but when I tried the second command, I get an error that "$Response" is not recognized as a command. This is what I tried in the command prompt:
$Response = Invoke-WebRequest -URI https://make.powerapps.com
These are the results:
Ping on StarLink
$Response = Invoke-WebRequest -URI https://make.powerapps.com (does not work in default command prompt)
When I attempt to access make.powerapps.com on StarLink, sometimes I see the existing apps listed, sometimes I don't. If it's a new day and I have a new browser instance with no cache, I get a message saying it can't access my data.
I also get the banner popup warning of the change to the Power Platform API whenever connected to StarLink.
When I attempt to edit or run an app, I get this error:
I have no idea what else to do.
Can you check your firewall rules? Are you able to ping the PowerApps url
and then try this as well
If either one of them is timing out, it could be a firewall issue. If that is the case, try adding these URLs to your approved list
Power Platform URLs and IP address ranges - Power Platform | Microsoft Learn
An update on my situation. The StarLink support suggested trying to log in to the PowerApps environment using an InPrivate session in the browser (Edge). I can't get this to work with my work laptop as it requires a certificate when I try to log in and none are available. However, I tried it on my personal PowerApps environment and it worked. So then it seems this would NOT be a StarLink issue but a Microsoft issue. Almost as if they are blocking any StarLink IP addresses. Unfortunately I don't know enough about routing to investigate further.
I've been having issues using the Power Platform when connected to Starlink . This is message it displays.
WarrenBelz
146,645
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
65,997
Most Valuable Professional