Christine Garcia
Christine Garcia

Reputation: 23

Unable to connect to azure pipeline, but deploy still works in app service deployment center?

I keep getting this error message in the Azure App service deployment center:

We were unable to connect to the Azure Pipeline that is connected to this Web App. This could mean it has been removed from the Azure Dev Ops Portal. If this has happened, you can disconnect this pipeline and set up a new deployment pipeline.

The thing is, it stil says that it successfully deploys, but If you try to access swagger for example, you get an HTTP error 500, (swagger does work localy). I have tried restarting the app service, going back commits, to see if that would help, but nothing is working. All Json data has been doubel chekced so that isn't the problem either. Anyone know of a fix?

Upvotes: 0

Views: 1591

Answers (1)

Harshitha Veeramalla
Harshitha Veeramalla

Reputation: 1753

We were unable to connect to the Azure Pipeline that is connected to this Web App. This could mean it has been removed from the Azure DevOps Portal. If this has happened, you can disconnect this pipeline and set up a new deployment pipeline.

  • Th error says that files are missing in the current build , try with new deployment pipeline.
  • You might have added an archive step in the build pipeline. This causes the artifact to be zipped before publish.
  • In the release pipeline if you use Azure App Service Deploy task , This internally uses Zip Deploy, that will zip the files.
  • Remove the archive step, the double zipping will be avoided.

HTTP error 500

  • Make sure the XML documentation file output is in bin and not in bin\Debug or bin\Release (verify this for all build configurations).

Upvotes: 1

Related Questions