Unable to deploy to staging slot with ERROR_DESTINATION_NOT_REACHABLE error

Question

Unable to deploy to staging slot with ERROR_DESTINATION_NOT_REACHABLE error

jsladovic 21

Hi,

We're running a Linux App Service (a .Net Core 3.0 App), deployments to which are handled through our Azure pipeline. The agents running the builds are located on a remote machine. When we added a staging environment, we tried to set up a build pipeline the same way, but the deployment fails with the following error during the Azure App Service deploy job:

##[error]Error: Error Code: ERROR_DESTINATION_NOT_REACHABLE

The error appears after the following line in the deploy job:

"C:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe" -verb:sync -source:package='F:\{agent_name}\_work\1\a\WebApp.zip' -dest:auto,ComputerName='https://{app-name}-staging.scm.azurewebsites.net:443/msdeploy.axd?site={app-name}',UserName='${app-user}__staging',Password='***',AuthType='Basic' -setParam:name='IIS Web Application Name',value='{app-name}' -enableRule:AppOffline -retryAttempts:6 -retryInterval:10000 -enableRule:DoNotDeleteRule -userAgent:VSTS_c18b017a-a9ee-4d9f-bd98-73b915148620_build_119_0

The main difference between here and the production pipeline which works is in the computer name parameter. The computer name for the production deployment is: https://waws-prod-am2-403.publish.azurewebsites.windows.net:443/msdeploy.axd?site={app-name}

My best guess would be that there is an issue with the connection from the deployment server to the staging server, but I'm not sure which checks I should perform there.

The Azure App Service deploy task is configured as such:

- task: AzureRmWebAppDeployment@4
  inputs:
    ConnectionType: 'AzureRM'
    azureSubscription: '{subscription name}({subscription ID})'
    appType: 'webApp'
    WebAppName: '{app-name}'
    deployToSlotOrASE: true
    ResourceGroupName: '{resource-group-name}'
    SlotName: 'staging'
    packageForLinux: '$(Build.ArtifactStagingDirectory)/*.zip'

The production pipeline is set up identically, with only the slot name being changed to "production". The pipeline variables, if there's any need for them are:

variables:
  solution: '**/*.sln'
  buildPlatform: 'Any CPU'
  buildConfiguration: 'Release'

Please do ask if there's anything else I need to share about this issue.

1 answer

Your answer

Answer 1

MughundhanRaveendran-MSFT 12,506

@jsladovic ,

Thanks for reaching out to Q&A.

Looking at the working and non - working scenario , the hostname endpoint is different. For the Production slot, the endpoint name is "stampname.publish.azurewebsites.net" (stamp name of the web app) and for staging it is "{app-name}-staging.scm.azurewebsites.net"

Please add this app setting "WEBSITE_WEBDEPLOY_USE_SCM" and set it to "false". Set to false for WebDeploy to stop using the Kudu deployment engine. The endpoint will change during the deployment. Also please keep this app setting specific to Staging slot.

https://learn.microsoft.com/en-us/azure/app-service/reference-app-settings?tabs=kudu%2Cdotnet#deployment

I hope this helps!

Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.

MughundhanRaveendran-MSFT 12,506 Reputation points

2022-01-10T07:23:45.51+00:00

@jsladovic , Just wanted to know if the above answer was helpful or not. Please let me know
jsladovic 21 Reputation points

2022-01-10T10:43:25.74+00:00
My apologies, one thing I forgot to mention is that I tried adding that configuration setting, but after setting it, I started getting a ##[error]Error: Error Code: ERROR_USER_UNAUTHORIZED error on the pipeline. The error description is:

More Information: Connected to the remote computer ("waws-prod-am2-403.publish.azurewebsites.windows.net") using the Web Management Service, but could not authorize. Make sure that you are using the correct user name and password, that the site you are connecting to exists, and that the credentials represent a user who has permissions to access the site. Learn more at: https://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_UNAUTHORIZED.

One thing I only just noticed is that the remote computer in the deployment is not the same one used while deploying, which is the following: https://{app-name}-staging.scm.azurewebsites.net:443/msdeploy.axd?site={app-name}

Could this be part of the issue? Also, we have used the WEBSITE_WEBDEPLOY_USE_SCM=false setting during production deployment, which works fine.
MughundhanRaveendran-MSFT 12,506 Reputation points

2022-01-13T06:06:53.347+00:00

@jsladovic , ERROR_USER_UNAUTHORIZED issue is seen when the user doesnt have proper RBAC permissions. Please assign contributor role and retry the deployment. From your inputs, I can assume that there are 2 client side machines that are used for deployment and only one of them fails?
jsladovic 21 Reputation points

2022-01-13T11:32:35.827+00:00

That's the odd part, we use the same machine and agent pool for both production and staging deployments, all the user roles are the same on both environments, but while the production deployment goes through without and issue, the staging fails with the aforementioned ERROR_USER_UNAUTHORIZED error. I have no idea what the difference between the two is.
MughundhanRaveendran-MSFT 12,506 Reputation points

2022-01-17T06:54:27.847+00:00

@jsladovic , Can you enable the debug flag in the pipeline and run the staging deployment? It might provide some additional logs.

https://learn.microsoft.com/en-us/azure/devops/pipelines/troubleshooting/review-logs?view=azure-devops#configure-verbose-logs
jsladovic 21 Reputation points

2022-01-18T09:28:46.047+00:00

Is there a way for me to respond with confidential data? There's quite a bit here and I'm really not sure which parts should be made public.

Share via

Unable to deploy to staging slot with ERROR_DESTINATION_NOT_REACHABLE error

1 answer

Your answer