Restore Portal not working after v8 update

[dasfliege]

Unfortunately it did not fix the problem for us.
Can someone who got it working now please explain the exact configuration you use?

REST API Server:
- Do you use self-signed or public cert in the "REST API" tab of the configurator? If public cert, is it a wildcard?
- Do you use self-signed or public cert in the "Restore Portal" tab of the configurator? If public cert, is it a wildcard?
- Do yo have "Enable restore operator authentication only" ticked or not?

VBM365 Server:
- Do you use self-signed or public cert in the "REST API" tab of the configurator? If public cert, is it a wildcard?

Proxy:
- Do you use a reverse-proxy to access the restore portal from outside?

Azure:
- Do you have any other permission on the app registration then "user-read" and "access_as_user"?

[keironbell]

We have installed the latest patch from https://www.veeam.com/kb4656 but we are also still having the same error message.
Case is with Support (07493019) but not heard back for a couple of days.

Anyone else still having this issue after the patch?

[rknmit]

We had it too, even after the latest update.
It turned out to be Admin Consent that was somehow "broken"...

After re-creating the App registration and re-adding it on the Tenant side, together with applying Admin Consent on both sides, it started working.

[eclipse4ever]

Hi, we have just installed a new v8 solution with separate NATS, PostgreSQL and proxy servers.
The rest API and restore portal work fine on the VBO server.
But to follow best practice I have created a new VM to run rest API and restore portal.
The application ID used in the restore portal tab is the same as we already created it on the VBM365 server itself.
The VBM365 server restore/rest API still works, I can login and browse etc.
But on the standalone VM that should take the restore operator role, we get the error as mentioned in this fora

"The server has rejected the client credentials."

I started with the Veeam selfsigned SSL, but changed it to a public wildcard SSL as I had an assumption this was the error, as stated in KB4292
https://www.veeam.com/kb4292

Still get the error message: "The server has rejected the client credentials." on the standalone machine?

Standalone server running rest API and restore portal: don't work
VBM465 server running rest API and restore portal: works

[eclipse4ever]

Hi,
I managed to solve it.
We had changed the restore authentication SSL on the VBM server, so after we imported this into the rest of the API server under trusted root, it worked
https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=80

[dasfliege]

We're again having error "The server has rejected the client credentials." when logging in through restore portal on a separate server. Logging in on the VBM365 server itself is working fine.
We're on version 8.1.1.159. Anyone else having the same problem again?

[t7MevELx0]

This issue is happening again on 8.1.0. I haven't tested the restore portal on 8.1.1 yet, but I will soon. Did this bug come back in 8.1?

This is the same issue and I do have a ticket opened for it. They are claiming no one has reported this...

"The server has rejected the client credentials."

We are an MSP and I do see this error on multiple tenants.

[Polina]

@dasfliege
We need a new support case on this issue and fresh logs from you. And please provide me with the case ID.

@t7MevELx0
Hi Cody! Am I correct that 07649995 is your opened ticket on this?

[t7MevELx0]

@Polina

Yes, that's the case I have opened for this issue. It seems we have another environment running 8.1.1 that has a test organization with this issue.

I remember this being fixed in version 8.04. So this might be a regression or just a similar bug.

[t7MevELx0]

I'm still experiencing this issue on version 8.1.1.159 / 2045 (hotfix build).

@dasfliege - are you still seeing it as well? I already spent hours on a WebEx with Veeam support, and the case has been escalated to Advanced Technical Support. Unfortunately, they’re just repeating the same troubleshooting steps.

It would be helpful to know if you’ve resolved it or if others are still running into the same problem on 8.1.1.

[dasfliege]

@t7MevELx0
No i was able to fix it but actually don't know what exactly the problem was. Only thing i did was basically granting app permissions again, clicking through all the wizards and re-set certificates everywhere.
We're now using the following certificates:

VBM365 server:
Options -> REST API -> Trusted Wildcard Cert
Options -> Restore Portal -> Self Signed Cert which has permission for the app registration
Options -> Authentication -> Trusted Wildcard Cert. Same as for REST API

Restore Portal server:
Options -> REST API -> Trusted Wildcard Cert
Options -> Restore Portal -> Self Signed Cert which has permission for the app registration

I don't know if this configuration is best practice, as i have never received any feedback on my questions above about which certificate has to be used at which point. Helpcenter and Veeam Support actually only focus on self signed certs.
What i can say is that i never managed to get it working when i did NOT use our Wildcard Cert at the "Authentication" option. Tried to import trusted root certificate from the other server, but without success.