Did you get a solution for this issue?
I had the same issue after I tried to update the templates after upgrading App Volumes to 2.16.0.
As in the logs stated the path to the datastore browser over the web URL was corrupted due the second “https” entry at the beginning of the URL so that AVM tried to resolve https://https://vcenter.domain.tld. I tried to change to URL in the App Volumes Manager interface under “Configuration > Machine Managers” without success so I tried to change the configuration in the SQL database.
The following workaround resolved the issue:
Notice: Take a full backup of the App Volumes Manager database
- Stop the App Volumes Manager service on all instances
- Login to the SQL database via SQL Server Management Studio
- Open the dbo.machine_managers table in the App Volumes database
- Edit the column “host” from the designated vCenter server instance and remove the “https://” entry from the URL string so that only the FQDN of the vCenter is left
- Start the first App Volumes Manager service and verify the Template upload mechanism
- Start the other App Volumes Manager services
@VMware: please verify if this is an appropriate workaround for this problem and why is it possible to insert an URL as Machine Manager address?