Unable Access to Portal

[S.Net]

hi everyone, I've a strange issue with VMA web portal because since today I'm not able to access due authentication not valid. I tried to reset the credentials but via SSH I'm able to access into VM but not via web.

There's something that I can do?

thanks

[Vitaliy S.]

Hi S.Net,

What's the exact error message you're seeing? Just to make it clear, you can log in to the appliance via SSH but cannot do the same with the the same user credentials? Is it a standalone appliance or managed by VBR?

Thanks!

[S.Net]

Authentication failed. Invalid username or password

is a standalone appliance on Azure. via SSH works fine.

[Vitaliy S.]

Ok, let me sync up with our QA team and I will let you know they think on this. If you want a faster solution, it's better to contact our technical support team.

[S.Net]

mmm...what happen if I say that is the free edition? there's no way to open a ticket

[nielsengelen]

You should be able to open a case on a best effort under free products in the list.

[S.Net]

ok....but in the meantime, can you check in your team?

thanks

[Vitaliy S.]

Have you tried logging in to the web UI with another account? Do you see the same issue? Also, are you able to use REST API calls with that account?

[S.Net]

I created a new sudo account via SSH and the result is the same. nothing via API because we don't have integration

thanks

[Vitaliy S.]

Integration is not needed to test APIs login. This test is needed to isolate the problem either to UI only or other components.

[adaorbb]

I have this exact same issue. Logging in via SSH is fine, but same accounts cannot log in to the Veeam Backup for Azure VM via the browser. Error msg: "Authentication failed. Invalid username or password."

[nielsengelen]

You can reset the password using this KB. If this doesn't solve the issue, first try rebooting the appliance (to assure all services start correctly) and if that doesn't work, please open a support case for insight via logs. If you do need to open a case, please share the case ID for future reference.

[malexander]

I'm having the same problem new Veeam for Azure v5. No login issues for the for a few hours, then get the Authentication Failed error. I have two logins defined and both get the same error. I'm able to logon to the OS without just fine with the default user account. I rebooted the VM multiple times. Is there a fix for this?

[Vitaliy S.]

Hi Michael,

I'm not aware of such a situation/fix, so there must be something unique in your case. Our support team will be able to help you.

Thanks!

[barellag]

Hello,

In case you encounter this issue, check the permissions for the file /etc/shadow and also the group owner.
You can run the following commands over SSH:

sudo chgrp veeamazure /etc/shadow
sudo chmod 640 /etc/shadow

Test the login again.

[prairie_it]

We're experiencing this same issue. Changing password via SSH was successful, in that I could login via SSH again with the new password. However the web portal remains inaccessible, and the veeam b&r software cannot communicate with the appliance with the credential either even though it works fine via SSH.

Other chmod commands suggested above weren't fruitful.

Anyone have any luck fixing? We noticed the issue happened starting exactly 1 year after setting up the appliance -- to me indicating something may have expired somewhere, but it's not at all clear where or how to resolve.

[Vitaliy S.]

This could be a certificate on the appliance. If you're unable to open the web UI and connect to this appliance from Veeam B&R, it's better to reach out to our support team, as it is hard to troubleshoot such issues over the forums. Let us know your case ID so that I could update the thread with a solution for future readers.

[prairie_it]

We've had success getting in.

1. Sign in via SSH
2. Connect to postgre: sudo -u postgres psql postgres
3. Connect to the azure veeam database: \c veeamazure
4. Review the account setup: select * from azure_account;
5. Note we found that our account had an expiration date on it. Repaired by: update azure_account set expiration_date='2025-06-09';

Then the login started working as before. Not sure why the account has an expiration in the database. If your select doesnt show expiration set then I wouldn't run the update. Note: there's only 1 record in the azure_account table so running update wide open only hits that one.

Nick

[nielsengelen]

Hi Nick,

Thanks for sharing. Ideally, we do advise working with support in case this issue happens to ensure everything is resolved correctly.

[janellejames]

Hello,

In case you encounter this issue, check the permissions for the file /etc/shadow and also the group owner.
You can run the following commands over SSH:

sudo chgrp veeamazure /etc/shadow
sudo chmod 640 /etc/shadow

Test the login again.

Has anyone figured out why this is happening repeatedly? We're about to write a python function to run these commands (to change group and permissions on /etc/shadow) before issuing API calls.

[nielsengelen]

Hi Janelle,

If you face this issue more often, I would suggest contacting support and letting us know the case ID so we can dig into the details.