c# WebApp connection refused after published
I've a problem with my webapp, but only after i publish it on azure.
If i start the web app from visual studio in my machine locally, and i try to call an api (on localhost:5001) it work normally, but when i try to call the api to web app published on azure (xxxx.azurewebsite.net) it always fails with a connection refused error
@AlessandroGrassi-5467 Thanks for reaching out. I tried spinning up an ASP.NET Core API app following this tutorial, but was unable to reproduce the mentioned error.
Could you please let me know the method you used to publish the app? Were there any error logs during the publish process? If not, do you see any errors on the Developer Tools Console while accessing the webapp?
@AlessandroGrassi-5467 Are you running a custom container? In which case, you should ensure to open the relevant ports on the container for incoming requests.
Which SKU is your app running on? If none of the other steps help, you can also consider scaling up to the next higher tier, so your app gets more compute to serve incoming traffic.
Do let us know if you have further questions.
i've publish the web app with visual studio, in the console app nothing appear, the web app seems that work normally.
what do you mean for custom container?
Initially for the first month the web app worked normally, and reply to API's correctly, but few days ago it stop worked and it reply to any api with this error
Recently i've done some test, it seems that the problem is about the application (c# application that i've created for test all api's) that call the api's. I've try to use postman (third part application that help to call api) to call a specific api and it work, the web app return a response, maybe the application that i've create don't have any certificate?
@AlessandroGrassi-5467 Have you had a chance to check this further?
Actually i've some problem with my subscription beacuse it's been suspended, i try solve this as soon as possible, then i'll check the resoirce limit quota
Sign in to comment
Sort by: Most helpful
@AlessandroGrassi-5467 Thanks for the response. Could you please also confirm which SKU/pricing tier your app is running on?
It could be that your web app has reached a resource quota limit that might apply to a Free or Shared scale service plan. Please try scaling up to the next higher tier so the application gets all the resources it needs.
Please check if that resolves the issue.
Sign in to comment