Proxmox server throwing 403 error for monitoring

[TheGorf]

This is y Zabbix 7.4.1 server. I've configured my API key and user and everything seems to be fine. But when I add the host, all the standard checks come back with HTTP 403 errors:

Cannot perform request: Operation timed out after 3003 milliseconds with 0 bytes received

I was reading this thread: https://forum.proxmox.com/threads/mo...orking.112477/

Where they mentioned manually running the check, but I can't figure out anything that describes how to do that. I'm hoping someone can help me out. Because I can't figure out for the life of me how to troubleshoot this.

[cyber]

From zabbix server or proxy command line, whichever is doing these queries for you... using curl for example.
That tmeplate has 3 main items. "API service status", "Get cluster resources", "Get cluster status". All the rest is based on the data obtained from those "Get.. " items.
If you open the items config you will see URL-s there

https://{$PVE.URL.HOST}:{$PVE.URL.PORT}/api2/json/cluster/status
https://{$PVE.URL.HOST}:{$PVE.URL.PORT}/api2/json/cluster/resources

And also authorization headers config... Using all this knowledge, replace macros with real values, construct correct curl command line and test, do you have connection, do you get anything back etc... use "time" command to understand, how long it takes, if you get answers... It might be a simple solution to just increase the timeout in item config.. default is 3 sec (as your 3003ms indicates also)...

[TheGorf]

Sorry, what does authorization headers config mean?

[Markku]

This is how I configure PVE:

• User group: monitoring
• User: zabbix (member of monitoring group)
• Permissions: monitoring group is assigned PVEAuditor role (path = /, propagation = true)
• API token is created for zabbix user (expire = never, privilege separation = no)

Then configure the Zabbix template according to the template instructions.

Update: From the template instructions:

• Copy the resulting Token ID and Secret into the host macros {$PVE.TOKEN.ID} and {$PVE.TOKEN.SECRET}.
• Set the hostname or IP address of the Proxmox API VE host in the {$PVE.URL.HOST} macro. You can also change the API port in the {$PVE.URL.PORT} macro if necessary.

Markku

[cyber]

Sorry, what does authorization headers config mean?

Does this explain enough?

[TheGorf]

Does this explain enough?

No. What is that? Where is it in the console? How do I get to it? Then, what do I do with it? Can you point me to the specific documentation that explains how to use it to use the curl tool?

[Markku]

I'd recommend just trying what I said above and only going to curl route if nothing else helps. I just implemented two PVE servers with the Proxmox VE by HTTP template with that setup.

Markku

[TheGorf]

I'd recommend just trying what I said above and only going to curl route if nothing else helps. I just implemented two PVE servers with the Proxmox VE by HTTP template with that setup.

Markku

I basically walked back through what you recommended. I can't get it to work. The API just keeps throwing 401's.

[TheGorf]

Ping. Anyone?