Unable to authenticate with the provided SmartDeploy Api Service URL

If you receive the error message "Unable to authenticate with the provided SmartDeploy Api Service URL" you can follow these steps to troubleshoot:

1. Open Services.msc and confirm that the MongoDB Service and the SmartDeploy Api Service are running.
2. If they are, open a browser and navigate to https://localhost:8080/Health to confirm the console service is running correctly. If everything is working properly it should display Healthy.
3. On the SmartDeploy Sign In page, expand Advanced and confirm the correct URL is set; https://localhost:8080.
4. Re-try logging onto the SmartDeploy console.

If the service cannot start, or you cannot reach the health URL, try these additional troubleshooting steps:

1. Restart both the MongoDB and SmartDeploy API services through the Windows Services application.
2. For virtual machines, be aware that hardware changes can cause authentication issues since the SmartDeploy API Service authentication is tied to the device's Endpoint ID. See the article below for the most common troubleshooting for that scenario. 
   What if I am unable to log in and getting “SCRAM-SHA-256” errors in my SDApiService.log file?

If issues persist, collect console logs by expanding Advanced on the Sign In page, and contact Support.