Skip to main content

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.

 

AWS, Azure and GCP backup appliances are not compatible yet with VBR v12. They won‘t work.

You need to wait for the new appliance + plugin versions of AWS, Azure and GCP.

 

The upgrade compatibility checker should have mentioned that. I had to remove my appliances from the VBR configuration before doing the upgrade.

 

Best,

Fabian


@CarySun  - the plug-ins for AWS and Azure will be soon after GA, they’re not in the RTM release for B&R. Google Cloud will be on GA. This is an important catch so I’ll make sure this is in the Upgrade Center notes.


m.. interesting. I didn’t use any Backup appliances, it’s an Azure blob only, not AWS or others, but the warning message is showing “Failed to connect to AWS plug-in: Failed to login to platform service”.


Can you please open a support case then? Doesn‘t sound expected. Maybe a bug then. Azure Blob is supported. But the AWS plugin shouldn‘t give you this error message if no appliances are configured.  

RTM is fully supported and our support will be able to help you.

 

Thanks

Fabian


Hello

The issue is confirmed by our team for In-place upgrades to RTM.

The cause are the outdated plugins which are still installed after the upgrade. A new installation of v12 RTM won‘t have that issue.

We will change that behavior for our GA release.
 

Best,

Fabian


@Mildur Thanks for the feedback!


Hi Markus

For now please ignore the warning. We plan to provide a better solution when GA is released. Also RTM can be upgraded to GA if we have a new build.

 

Best,

Fabian


Vbr11 is my server name.


@Mildur Thanks for the recommendation. I thought someone got the same warning as mine. I believed it was a bug.


Hi @ROLS733 

You need to wait for the “RTM-To-GA” Patch. It shouldn’t take to long.

I will update this post with the KB article after the release.

 

Best,

Fabian


The URL says …vbr11:9402…

I think you have to setup the connection again...


@Mildur Thank you for the update.


You can also update to the newest patch and check again if you see the error. We solved over 100 known issues with that patch.

https://www.veeam.com/kb4420


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.


Hi @ROLS733 

You need to wait for the “RTM-To-GA” Patch. It shouldn’t take to long.

I will update this post with the KB article after the release.

 

Best,

Fabian

What Mildur says - but I expect it Friday. The internal communication was that the patch would be readh Thursday close-of-business from the devs; then the KB made right after that - so Friday.


Same here. Configuration backup flags the above warning daily since the upgrade V11->V12(RTM).

No AWS used in the demo environment. So I consider this a cosmetical issue with the built-in plugin right now.

The Azure plugin seems to work though, as the demo is doing some SOBR offloading to Azure S3.

 


Did anyone open a support case regarding this issue?


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.


I found that after another reboot of the VBR 12 server the AWS & GCP errors have gone away :)


Found the result AWS Service was not running on the Server


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


No I havent - I don’t need them.

Are you saying you HAVE TO install them to get rid of this error in the log?


I am getting the “Warning Failed to connect to AWS plug-in” and “Warning Failed to connect to GCP plug-in” error from my Configuration Backup job too.

I am on:

 

This server was an in-place upgrade from V11.

I did not/do not have the AWS or GCP plugins installed.

Hi @clowg have you tried installing the AWS and GCP plugins?


I am getting the “Warning Failed to connect to AWS plug-in” and “Warning Failed to connect to GCP plug-in” error from my Configuration Backup job too.

I am on:

 

This server was an in-place upgrade from V11.

I did not/do not have the AWS or GCP plugins installed.


Hi Lennart

 

Please update the AWS plugin to the newest version (12.0.6.956). You can download the plugin on our download page
https://www.veeam.com/backup-replication-vcp-download.html.

 

Best,

Fabian


Comment