403 access denied Error after deploying node js proxy in azure app service

JS 1 Reputation point
2022-09-27T03:21:21.557+00:00

Hi

I am trying to deploy a node Js proxy application into azure app service, I tried to push the code from
Visual code and its deployed successfully. But when I tried to browse the app service url it is showing you don’t have access to this and showing 403 error, Please share the examples or details why I am
Seeing this issue ?

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,925 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. brtrach-MSFT 15,256 Reputation points Microsoft Employee
    2022-09-29T03:35:35.067+00:00

    @JS There are three main reasons that come to mind as to why we typically see 403 errors.

    The two below errors are the HTTP status and HTTPSubStatus error code. The Sub Status code can provide you with a more direct understanding of why you are receiving a 403 error. To view the SubStatusCode, please enable Application logging, generate a request or two on your site that results in a 403 error, wait roughly 15 minutes to ensure the event is captured in logging, and then review the logs. For more information on diagnostic logging, please see here.

    1. 403.503 implies that the request was blocked as part of an IP restriction. If you have set network restrictions, please navigate to your web app in the Azure portal and go to the networking blade. From here see if the access restrictions are turned on. If so, you need to review your access restrictions to include your client IP.
    2. 403.72 implies that your application is expecting a client certificate and the certificate is not found or loading correctly. For this, please ensure that you have correctly located and coded your client certificate.

    We hope one of those two scenarios aligns with what you are seeing but there are other 403 substatus codes. If this does not align, please let us know what substatus code, if any, you see in your application logs.

    0 comments No comments