Hi @Dejan Srdjevic
The WEBSITE_NODE_DEFAULT_VERSION conflict occurs when changing to Node.js 20, which may cause compatibility issues with your web.config or app dependencies, especially with the run.cjs path in production. Change run.cjs to your app’s main file (e.g., index.js). Example
web.config: <configuration>
<system.webServer>
<handlers>
<add name="iisnode" path="index.js" verb="*" modules="iisnode"/>
</handlers>
<rewrite>
<rules>
<rule name="DynamicContent">
<conditions>
<add input="{REQUEST_FILENAME}" matchType="IsFile" negate="True"/>
</conditions>
<action type="Rewrite" url="index.js"/>
</rule>
</rules>
</rewrite>
<httpErrors existingResponse="PassThrough" />
</system.webServer>
</configuration>
- Use Kudu console and run npm cache clean --force, then restart your app.
- In Azure portal, enable Application Logging and Detailed Error Messages under Diagnose and Solve Problems.
- Run locally with NODE_ENV=production to ensure compatibility.
- Run npm install, npm outdated, and npm audit fix to update packages.
- Ensure no conflicts exist in your GitHub Actions workflow and enforce Node.js 20 with:
az webapp config set --name <your-app> --resource-group <your-resource-group> --linux-fx-version "NODE|20"
Please accept as "Yes" if the answer provided is useful , so that you can help others in the community looking for remediation for similar issues.