Need help with the built-in Veeam Backup and Recovery by HTTP template

[ws65infl]

I've tried everything I can think of and still getting access denied.
Both servers are in the same network.
The server Veeam is installed on is not a domain joined server. I setup a user account called zabbix, made it a member of Administrators group and Backup Operators group. In Veeam, I made that account have the Veeam Backup Administrator role in Veeam.
In the Zabbix template macros I did the following:
{$VEEAM.API.URL} https://IP of the Veeam Server:9419/api/
{$VEEAM.USER} zabbix user created on the Veeam Server)
{$VEEAM.PASSWORD} password for the zabbix user.

On the Veeam server, the firewall is on but I've allowed 9419 TCP and UDP inbound and outbound.

When I try to browse to https://IP of the Veeam Server:9419/api/ I get the same access denied 403 error.

About the only other thing I can think of is that maybe the server's self signed certificate is messing it up? Also, I have not exported that cert and imported into Zabbix, didn't think I needed to since I was supplying username and password in the macro.

I've been trying for two days now, no luck. I will be very thankful for any help on this issue.

[ws65infl]

One thing I forgot to mention, I'm using Zabbix 7 lts.

[ws65infl]

I still haven't figured this out

[ysus]

Try to remove /api/ from the end

The URL which works on my system is 'https://IP of the Veeam Server:9419'

[ws65infl]

Thanks ysus just tried that and got the same error

[ysus]

Well, as long as you have user and firewall configured properly I don't know what else to check...

[ws65infl]

I checked those just now and set to exactly what you have. The only other thing I can think of is that I see a self-signed certificate in the security tab in Veeam. Its the server Veeam is on that keeps refusing the connection. Swagger doesn't even open locally...I get your connection is not private and says NET::ERR_CERT_COMMON_NAME_INVALID...I had the thought of exporting that cert and importing it into Zabbix's certificate store but not sure how to do that and if it would even help. I think I will open a ticket with Veeam.

[Zaaappe]

Hi,

For {$VEEAM.API.URL} I use https://FQDN:9149/api

for {$VEEAM.USER} try using the account you normally use to access VEEAM like "you_user_account@your_domain.net".

and for {$VEEAM.PASSWORD}, your password.

Try that!

[ws65infl]

Thank you but it turns out its something in my Veeam install that even the Veeam techs could not figure out. Something in my system is blocking it and no one can figure out what it is!