Backup Configuration job warning after upgrade to VBR12 RTM
Any idea for this? It’s pure Hyper-V with Azure, not AWS.
1/31/2023 10:06:49 AM Warning Failed to connect to AWS plug-in: Failed to login to platform service: The HTTP resource that matches the request URI 'https://vbr11:9402/api/v1/account/login' is not supported.
Page 2 / 2
I just did update my lab from RTM to GA, and the warning no longer appears. So solved in my case.
I am receiving the “Failed to connect to AWS plug-in” warning even though I upgraded using the GA ISO. I am on build 12.0.0.1420.
In version 12.0.0.1420 I also have this warning.
Hello
If you still see the warning, you can uninstall the aws plugin on your backup server. A new plugin version will soon be provided with the new version of Veeam Backup for AWS.
Best,
Fabian
Just wanted to mention that this issue is being encountered with a client of mine that was upgraded to the v12 GA release. Looking at manually running the plug-in installers over again from the install media and seeing if that does the trick.
Same here. Build 12.0.0 1420 P20230223
Unfortunately, I’m not able to uninstall AWS-Plugin:
I installed the latest patch release, and am still getting the errors in the Config Backup job log:
27/04/2023 10:00:31 AM Warning Failed to connect to AWS plug-in: Failed to login to platform service: No connection could be made because the target machine actively refused it X.X.X.X:9402
27/04/2023 10:00:26 AM Warning Failed to connect to GCP plug-in: Failed to login to platform service: No connection could be made because the target machine actively refused it X.X.X.X:9403
Found the result AWS Service was not running on the Server
I found that after another reboot of the VBR 12 server the AWS & GCP errors have gone away :)