[GH-ISSUE #32] [Bug]: pbs and pve not accepting api keys #126

New issue

Closed

opened 2026-03-13 17:13:37 +03:00 by kerem · 2 comments

kerem commented

2026-03-13 17:13:37 +03:00

Owner

Originally created by @ArMaTeC on GitHub (Feb 20, 2026).
Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/32

Bug Description

First time user and im getting stuck at the first milestone with the error
PVE authentication failed: PVE 401 /version:

API key format(not a real key): root@pam!proxcenter!tokenid=4504w1c9-cd9b-408d-b20c-844bbc8d4198

Steps to Reproduce

Enter server name
Enter server url with port
Add the api key
click save
get this error "PVE authentication failed: PVE 401 /version:"

Expected Behavior

server is added

Actual Behavior

PVE authentication failed: PVE 401 /version:

ProxCenter Version

Latest docker

Proxmox VE Version

9.1.5

Browser

No response

Logs / Screenshots

No response

Originally created by @ArMaTeC on GitHub (Feb 20, 2026). Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/32 ### Bug Description First time user and im getting stuck at the first milestone with the error PVE authentication failed: PVE 401 /version: API key format(not a real key): root@pam!proxcenter!tokenid=4504w1c9-cd9b-408d-b20c-844bbc8d4198 ### Steps to Reproduce 1. Enter server name 2. Enter server url with port 3. Add the api key 4. click save 5. get this error "PVE authentication failed: PVE 401 /version:" ### Expected Behavior server is added ### Actual Behavior PVE authentication failed: PVE 401 /version: ### ProxCenter Version Latest docker ### Proxmox VE Version 9.1.5 ### Browser _No response_ ### Logs / Screenshots _No response_

kerem

2026-03-13 17:13:37 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-13 17:13:53 +03:00

Author

Owner

@adminsyspro commented on GitHub (Feb 20, 2026):

Hi, thanks for reporting this.

Looking at your token format, the issue is likely there. You wrote:

root@pam!proxcenter!tokenid=4504w1c9-cd9b-408d-b20c-844bbc8d4198

The correct Proxmox API token format is user@realm!tokenname=secret, with a single ! separator. If your token is named "proxcenter", it should be:

root@pam!proxcenter=4504w1c9-cd9b-408d-b20c-844bbc8d4198

The 401 /version error confirms that Proxmox itself is rejecting the credentials, which points to a format issue rather than a ProxCenter bug.

Also make sure the token was created with --privsep 0 or has explicit permissions assigned to it (not just inherited from the user).

Let us know if that fixes it.

@adminsyspro commented on GitHub (Feb 20, 2026): Hi, thanks for reporting this. Looking at your token format, the issue is likely there. You wrote: `root@pam!proxcenter!tokenid=4504w1c9-cd9b-408d-b20c-844bbc8d4198` The correct Proxmox API token format is `user@realm!tokenname=secret`, with a single `!` separator. If your token is named "proxcenter", it should be: `root@pam!proxcenter=4504w1c9-cd9b-408d-b20c-844bbc8d4198` The `401 /version` error confirms that Proxmox itself is rejecting the credentials, which points to a format issue rather than a ProxCenter bug. Also make sure the token was created with `--privsep 0` or has explicit permissions assigned to it (not just inherited from the user). Let us know if that fixes it.

kerem commented

2026-03-13 17:13:58 +03:00

Author

Owner

@ArMaTeC commented on GitHub (Feb 20, 2026):

Yes that fixed the issue thank you

@ArMaTeC commented on GitHub (Feb 20, 2026): Yes that fixed the issue thank you