Proxy can't connect to Functions CLI v4
See original GitHub issueAzure Static Web Apps CLI can’t connect to Azure Functions V4 CLI. The same issue with webpack or parcel proxy.
[swa] × Waiting for http://localhost:7071 to be ready
[swa] Could not connect to "http://localhost:7071". Is the server up and running?
But when I go to localhost:7071 I can see the “Your Functions 4.0 app is up and running” page working just find and I can send requests using postman or web browser and they work just fine.
> func --version
4.0.3780
I’m running Windows 11 22000.282. Tried turning the firewall off but didn’t help.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:13 (5 by maintainers)
Top Results From Across the Web
Angular-CLI proxy to backend doesn't work - Stack Overflow
When I type inside commander npm start then at the start I can see Proxy created: /api -> http://localhost:8080 . Well, so far...
Read more >Why can't I connect to my Amazon RDS DB or Amazon Aurora ...
There are a number of reasons that you might experience connection failures with RDS Proxy, even when RDS Proxy is in the Available...
Read more >Using Anypoint CLI with a Network Proxy
Anypoint CLI can be run through a network proxy to add a layer of security. To use the Anypoint CLI with a proxy...
Read more >Troubleshooting common errors within Burp Suite - PortSwigger
Go to the Proxy > Options tab. In the Proxy Listeners section, the table should show at least one entry where the Running...
Read more >Develop Azure Functions by using Visual Studio Code
If your trigger requires an access key or connection string to connect to a service, get it ready before you create the function...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I switched from node 17 to 14 and it started working.
NodeJS Version 16 LTS is working fine on Windows 10. Remember to reboot after uninstall / install. This issue can be closed, since it is not a related Issue to static-web-apps-cli? @anthonychu