-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Invalid usernameor password upon connection #44
Comments
Does this also happen, if you're using the token based Auth method? See Readme for an example. Token based Auth is recommended with never proxmox versions |
Yes, by two ways: I created an api token at the command line as given in your guide and in a second try from scratch where I tried by creating the api token in the gui. Result is the same. |
API endpoint must not contain any paths. Endpoint and port can be specified via cli args and from that the check script composes the complete url. E.g. |
That solved it. Thank you very much. |
Fixed with #52 |
I followed the documentation to create a role, a user nagios@pam, a password and a an API token.
When I try the following or similar:
./check_pve.py -u 'nagios@pam' -p "<pass>" -k -e 10.10.7.9:8006/api2/json/ -m version -V 8.0.0
Then I get the error:
UNKNOWN - Could not fetch data from API: Could not connection to PVE API: invalid username or password
The same when using the token.
The user nagios exists in the OS. I can ssh using nagios.
The user exists in the Proxmox GUI. Password was set per command line as described in the guide here as well as using the GUI. Same for the token. The role and privileges are visible in the GUI.
When I follow the PVE documentation by doing:
I get the data and no error.
I suspect the error message of the script is misleading and there is another error underlying.
Steps to reproduce the behavior:
Expected behavior
Get an icinga compatible result.
Environment (please complete the following information):
Linux 6.2.16-14-pve
PVE 8.0.4
Python 3.11.2
The text was updated successfully, but these errors were encountered: