+7
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. |
Best answer by Mildur
View original
+7
M..interesting, the configuration backup is back to normal after I migrated the existing VBR 12 server (it was migrated from v11a to v12 RTM) to the new server with PostgreSQL. I did not try to migrate to the new server with Microsoft SQL yet.
Did anyone open a support case regarding this issue?
being out of office today I could open one tomorrow ...
+14
Did anyone open a support case regarding this issue?
Same with us since the RTM 12 upgrade of Veeam. When doing a configuration Backup the AWS warnign appears int ehWe also don’t use AWS warning appears in the result.
“Warning Failed to connect to AWS plug-in: Failed to login to platform service: The HTTP resource that matches the request URI 'https://server:9402/api/v1/account/login' is not supported.”
After typing the uri into a web browser session on the local backup server I receive the following answer:
errorCode "MethodNotAllowed"
message "HTTP Method not allowed"
resourceId null
Further investigations look like that the Veeam service has got a problem with self signed certificate on the local backup server.
Is there any update on this issue, yet?
Same here. Configuration backup flag is warning since the upgrade V11->V12(RTM).
No AWS used at all … on both servers :-( that have been upgraded ...
+8
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.
+10
+7
+12
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
+7
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”.
+12
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
+7
Vbr11 is my server name.
+17
The URL says …vbr11:9402…
I think you have to setup the connection again...
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
