ackage updates need to be processed through the Advanced Tools / Kudu / SCM console, which is why the URL includes *.scm.azurewebsites.net. Redirecting to a custom domain will not work because that address points to the app's front-end, whereas the Kudu console runs separately and requires the original Azure-provided URL to function correctly.
To my knowledge, Azure does not currently support masking the Advanced Tools console with a custom domain name. This is by design, as Azure needs the original URL in the request header to process requests—simply adding a CNAME record will not achieve this.
Update fails on custom domain
1
Thank you for submitting your feature request—we truly value input from our community.
Next steps:
• We will review your request and update its status as it progresses through our evaluation process.
• If any clarification is needed, we'll follow up with you directly in the comments.
We also encourage the community to influence our decision through comments, votes, and feedback.
Next steps:
• We will review your request and update its status as it progresses through our evaluation process.
• If any clarification is needed, we'll follow up with you directly in the comments.
We also encourage the community to influence our decision through comments, votes, and feedback.
Thanks Tushar, What version are you on currently? What error are you seeing when updating? Did you follow the steps outlined in: How to Customize the Nerdio Manager URL
After setting up a custom domain on the WebApp in Azure you should still be able to use the update functionality, both Automated Runbook or Cloud Shell update methods. The update process still relies on SCM urls as they should not be removed and are required as you mentioned in your original post.
The update process is not dependent on the URL you use to access the Nerdio Manager, the Subscription, Resource Group, and WebApp are passed into the update process.
Let me know if I missed something.
For those with private endpoints;
It would be good if Nerdio can allow admins to change the FQDN of the SCM, to a custom domain / private IP endpoint address, as the updates for either Automation Job or Azure CLI will use Azure DNS, therefore the public address will be utilised.
The workaround at the moment is to enable public access briefly during the upgrade process, then disable public access for the App Service.
Please sign in to leave a comment.
Comments (3 comments)