New answers tagged

1

To make it work, you need to check the "This server requires a secured connection (SSL)" checkbox and restart the server.


1

Select the Default agent pool in the Releases Run on agent - Agent pool field. It appears this gets set to another value when creating a new release. Once Agent pool was set to Default, the error went away.


0

The official solution is documented here: MS Docs: Create ILB ASE - DNS Configuration You need to have DNS entries for your ASE so that the deployment task can reach it; but if you have an internal only ASE, those entries aren't created in public DNS, and MS don't manage private DNS. MS propose creating the DNS entries in your internal DNS: Create Zone {ASE ...


Top 50 recent answers are included