Internal Server Error RRS feed

  • Question

  • We have a Web App deployed on https://meterbolic.org

    An internal IIS error occurs when we try to take a payment on the integrated Stripe service:
    The http errors are 403 and 500.0

    Where might we try to fix this internal server error so that the Stripe payment works?

    Many thanks for any advice.

    We have configured the web.config as follows:
        <webSocket enabled="false" />
            <clear />
            <rule name="DynamicContent" stopProcessing="true">
              <match url=".*"/>
              <conditions logicalGrouping="MatchAll">
                <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true"/>
                <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true"/>
                <add input="{REQUEST_URI}" pattern="^/(api)" negate="true"/>
              <action type="Rewrite" url="/index.html"/>
            <rule name="Reverse Proxy to Azure Functions" stopProcessing="true">
              <match url="api/(.*)"/>
              <action type="Rewrite" url="https://meterbolic-functions.azurewebsites.net/{R:0}" />

        <!-- Make sure error responses are left untouched -->
        <httpErrors existingResponse="PassThrough" />

    Tuesday, December 31, 2019 1:56 PM

All replies

  • Thanks for asking question! You may use App Service Diagnostics. This is our intelligent and interactive experience to diagnose and troubleshoot issues with your app. 

    1. Go to the Azure Portal(https://ms.portal.azure.com/).
    2. Select your app (Windows, Linux, or Functions) or App Service Environment.
    3. Click on “Diagnose and solve problems.”

    App Service Diagnostics homepage is separated into different problem categories to help you be more focused on the specific issue that you’re facing. Each problem category will have a description and keywords to help and describe what types of problems would fall underneath that category. You may click around these tiles to investigate your issue.  

    Also, you can enable Web Server Diagnostics as well as Application Diagnostics for your websites and check the logs when this happens again. You may refer to this link: https://azure.microsoft.com/en-us/documentation/articles/web-sites-enable-diagnostic-log/

    Let me know if issue persists.

    Friday, January 3, 2020 4:54 AM