HTTP Error 500.30 - ASP.NET Core app failed to start

Common solutions to this issue:

Troubleshooting steps:

For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS.

Oct 3, 2024

Contact Us today~

To import the previous blog content, we need the XML file from the previous blog. 

  1. Inform the client that they must retrieve and provide an XML file from their current website provider
  2. Once the blog is created in the CMS and you receive the XML file from the client, submit an IT ticket with the XML file attached.
    • Sample IT ticket
      • TIP: Along with providing the Dealer ID and staging URL (or Primary Domain if the site is Live), be sure to include the link to the blog as an Example URL so IT can easily locate where to complete the import.
    • Reference the Implementation IT Ticket QA Scorecard SKB for help creating the IT ticket
  3. Once the blog is imported, review the blog to ensure that there are no replacement codes visible and/or broken images and links. Resolve/clean up any issues you discover during your review.
    • TIP: If the import has images, during your review, you’ll also need to check the images to ensure that are not still residing on the previous provider’s servers. If they are, once that site is taken offline, all of the client’s images will go offline too. To do so, right click on an image and select “Open image in new tab“. Go to the new tab and review the URL in the address bar. If it does not contain our blog URL slug including “/wp-content/uploads/” directories (i.e.: /blogs/4643/wp-content/uploads/2024/09/673012249.jpg), then the image is probably not on our servers. In this case, please update your ticket asking IT to reimport the XML selecting to download images/author’s to make sure all authors and images were downloaded onto DealerOn’s servers.  (Example IT ticket)
  4. See Important Note About Blog Redirects.

HTTP Error 500.30 - ASP.NET Core app failed to start

HTTP Error 500.30 - ASP.NET Core app failed to start

Common solutions to this issue:

Troubleshooting steps:

For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS.