##[error]Failed to deploy web package to App Service. ##[warning]Can't find loc string for key: KuduStackTraceURL ##[error]KuduStackTraceURL https://$nameof-backend__dev:***@nameof-backend-dev.scm.azurewebsites.net/api/vfs/LogFiles/kudu/trace ##

Shuchita Chiwande 0 Reputation points
2024-06-24T08:07:20.1833333+00:00

##[error]Failed to deploy web package to App Service. ##[warning]Can't find loc string for key: KuduStackTraceURL ##[error]KuduStackTraceURL https://$nameof-backend__dev:***@nameof-backend-dev.scm.azurewebsites.net/api/vfs/LogFiles/kudu/trace ##[error]Error: Error: Failed to deploy web package to App Service. Conflict (CODE: 409)

I am getting this error. I am trying to generate a env file dynamically during deploy stage. I am using archive file publish build artifact in build stage and download artifact. I think i have set the path correct for the cmd line i am using to generate a env file during deploy stage. It is not a part of the artifact. I have set the environments correctly. What could be the issue?

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
7,726 questions
{count} votes

2 answers

Sort by: Most helpful
  1. ajkuma 26,036 Reputation points Microsoft Employee
    2024-06-24T12:17:49.2066667+00:00

    @Shuchita Chiwande , Adding to Deepanshukatara response.

    Following from the above, if the issue still persists, you may navigate to Kudu (console): http://”yoursitename”.scm.azurewebsites.net.

    • On your App Service Linux use the SSH or the “Bash” option, as in this case, we just need to access /home (or on Windows, through the Kudu Console)
    • Navigate to /home/site/locks, delete status.lock and info.lock
    • Navigate to /home/site/deployments.
      check to see if there may be folders named pending, temp and active. You can cat the pending file and ls temp-* and active, which should have a log.log and status.xml in these directories. Try deleting the temp-* folder and pending. Later, restart the WebApp and then check again.
    2 people found this answer helpful.

  2. Deepanshukatara-6769 9,190 Reputation points
    2024-06-24T08:22:32.8866667+00:00

    Hi Suchita, Welcome to MS Q&A

    First scaled up the plan to Basic if not then change WEBSITE_RUN_FROM_PACKAGE to 1 which tells the platform not to extract your zip but mount you zip as a folder for your app to run. If you need your app built by the platform, then this setting will not work for you.

    If you've already tried these steps or been down this path, then you'll need to provide some additional details:

    • Are you deploying your zip through the CLI, drag and drop on Kudu, through VS Code?
    • Did scaling your app service plan up resolve the issue?
    • Do you see any file names in D:\home\site\locks?
    • Anything in D:\home\site\deployments?

    Please check this doc also once , if it helps

    https://learn.microsoft.com/en-us/azure/app-service/deploy-run-package

    Kindly accept if it works

    Thanks
    Deepanshu


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.