We’ve may have already experienced issues with Deploying DevOps like error code “error_could_not_connect_to_remotesvc.” At Bobcares, our DevOps Consulting Service can help you with some quick fixes.

Fixing the DevOps Error Code “error_could_not_connect_to_remotesvc”

An inability to set up a connection to a remote service typically occurs by the error code “error_could_not_connect_to_remotesvc”. This could occur for a number of reasons such as Network Issues, Service Availability, Incorrect Config, Firewall issues, and more.

Storage Issue

Mostly, we see the above error when there is an issue with the storage space in the shared App Service plan. In such cases, we’ve to look at some of the following:

1. Check if Azure app service is working fine (ping the remote machine).

2. Ensure the msdepsvc or wmsvc service is started on the remote server.

3. Make sure firewall isn’t blocking incoming connections on ports 80 (msdepsvc) and 8172 (wmsvc).

4. Add “-retryInterval:6000 -retryAttempts:10” to Additional Arguments in Azure App Service Deploy task.

5. If the issue persists in Azure pipeline, check if it occurs locally.

Solution: In this case, we need to upgrade to a larger plan.

Deployment Issue

Sometimes, the error may also occur when the deployment failed due to agent pool lacking deployment rights (IP not whitelisted for production App service).

Solution: Fiddler traffic capture changed in machine.config, which prevented Visual Studio from being deployed to Azure.

[Want to learn more? Click here to reach us.]

Conclusion

The article explains about two cases in which we may see the DevOps Error Code “error_could_not_connect_to_remotesvc” and the solution for the issues offered by our Tech team.