starred/proxcenter-ui

Fork 0

mirror of https://github.com/adminsyspro/proxcenter-ui.git synced 2026-04-25 14:35:56 +03:00

[GH-ISSUE #52] [Bug]: Unable to add self-signed certificate PBS #63

New issue

Closed

opened 2026-03-07 19:27:06 +03:00 by kerem · 2 comments

kerem commented

2026-03-07 19:27:06 +03:00

Owner

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

Bug Description

Trying to add a PBS with self-signed certificate, successfull add in UI without error but no data in Proxmox Backup Server section

Steps to Reproduce

Go to "Connections" tab, Add PBS, then fill the form with Ignore TLS certificate errors ticked.
Next, go to Backups tabs > PBS, select the PBS Server and see you have no info at all.
Finally, when multiple fetch fail, we can see error in docker logs

Expected Behavior

Fetch data from PBS

Actual Behavior

Fetch Error

ProxCenter Version

latest

Proxmox VE Version

latest

Browser

Chrome

Logs / Screenshots

[entrypoint] Starting...

 ██████╗ ██╗  ██╗ ██████╗
 ██╔══██╗╚██╗██╔╝██╔════╝
 ██████╔╝ ╚███╔╝ ██║
 ██╔═══╝  ██╔██╗ ██║
 ██║     ██╔╝ ██╗╚██████╗
 ╚═╝     ╚═╝  ╚═╝ ╚═════╝
 ProxCenter v1.2.0-d328f2d — Community Edition

 Unified server on port 3000
 ├─ HTTP + WebSocket  http://0.0.0.0:3000  ✓
 └─ Database          SQLite             ✓

 WebSocket routes
 ├─ /api/internal/ws/shell           Node/VM/CT shell
 ├─ /api/internal/ws/console/{id}    VM/CT console
 ├─ /ws/shell                        (alias)
 └─ /ws/console/{id}                 (alias)

[inventory] Fetched from Proxmox in 145ms
[inventory] Fetched from Proxmox in 2618ms
[inventory] Fetched from Proxmox in 214ms
[inventory] Serving stale data, revalidating in background
[inventory] Background revalidation completed in 130ms
License features fetch failed: fetch failed
[inventory] Serving stale data, revalidating in background
[inventory] Background revalidation completed in 181ms
License features fetch failed: fetch failed
[inventory] Fetched from Proxmox in 135ms
PBS status error: Error: self-signed certificate
    at ignore-listed frames {
  code: 'DEPTH_ZERO_SELF_SIGNED_CERT'
}
PBS status error: Error: self-signed certificate
    at ignore-listed frames {
  code: 'DEPTH_ZERO_SELF_SIGNED_CERT'
}
PBS status error: Error: self-signed certificate
    at ignore-listed frames {
  code: 'DEPTH_ZERO_SELF_SIGNED_CERT'
}

Originally created by @erwanclx on GitHub (Feb 25, 2026). Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/52 ### Bug Description Trying to add a PBS with self-signed certificate, successfull add in UI without error but no data in Proxmox Backup Server section ### Steps to Reproduce Go to "Connections" tab, Add PBS, then fill the form with _Ignore TLS certificate errors_ ticked. Next, go to _Backups_ tabs > _PBS_, select the PBS Server and see you have no info at all. Finally, when multiple fetch fail, we can see error in docker logs ### Expected Behavior Fetch data from PBS ### Actual Behavior Fetch Error ### ProxCenter Version latest ### Proxmox VE Version latest ### Browser Chrome ### Logs / Screenshots <img width="2473" height="733" alt="Image" src="https://github.com/user-attachments/assets/bb5ca829-1709-4c03-b065-645869f04990" /> ``` [entrypoint] Starting... ██████╗ ██╗ ██╗ ██████╗ ██╔══██╗╚██╗██╔╝██╔════╝ ██████╔╝ ╚███╔╝ ██║ ██╔═══╝ ██╔██╗ ██║ ██║ ██╔╝ ██╗╚██████╗ ╚═╝ ╚═╝ ╚═╝ ╚═════╝ ProxCenter v1.2.0-d328f2d — Community Edition Unified server on port 3000 ├─ HTTP + WebSocket http://0.0.0.0:3000 ✓ └─ Database SQLite ✓ WebSocket routes ├─ /api/internal/ws/shell Node/VM/CT shell ├─ /api/internal/ws/console/{id} VM/CT console ├─ /ws/shell (alias) └─ /ws/console/{id} (alias) [inventory] Fetched from Proxmox in 145ms [inventory] Fetched from Proxmox in 2618ms [inventory] Fetched from Proxmox in 214ms [inventory] Serving stale data, revalidating in background [inventory] Background revalidation completed in 130ms License features fetch failed: fetch failed [inventory] Serving stale data, revalidating in background [inventory] Background revalidation completed in 181ms License features fetch failed: fetch failed [inventory] Fetched from Proxmox in 135ms PBS status error: Error: self-signed certificate at ignore-listed frames { code: 'DEPTH_ZERO_SELF_SIGNED_CERT' } PBS status error: Error: self-signed certificate at ignore-listed frames { code: 'DEPTH_ZERO_SELF_SIGNED_CERT' } PBS status error: Error: self-signed certificate at ignore-listed frames { code: 'DEPTH_ZERO_SELF_SIGNED_CERT' } ```

kerem

2026-03-07 19:27:06 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-13 17:14:30 +03:00

Author

Owner

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

Hi @erwanclx, thanks for the report!

We investigated the code in depth, and the TLS handling for PBS connections uses the exact same mechanism as PVE connections — both use an undici Agent with rejectUnauthorized: false when "Ignore TLS certificate errors" is enabled.

Since the connection was successfully added (which means the validation call to PBS passed with TLS bypass), the insecureTLS flag was correctly set at creation time.

To help us investigate further, could you:

Show us a screenshot of your PBS connection settings in the Settings page (the edit dialog), so we can confirm "Ignore TLS certificate errors" is toggled ON
Check the database value by running this:
```
docker exec -it <proxcenter-container> sqlite3 /app/data/proxcenter.db "SELECT id, name, insecureTLS FROM Connection WHERE type='pbs';"
```
(Replace <proxcenter-container> with your actual container name — use docker ps to find it)

We want to confirm insecureTLS = 1 in your database.

If insecureTLS is 0, you can fix it by running:

docker exec -it <proxcenter-container> sqlite3 /app/data/proxcenter.db "UPDATE Connection SET insecureTLS=1 WHERE type='pbs';"

Then restart the container.

Thanks!

@adminsyspro commented on GitHub (Feb 26, 2026): Hi @erwanclx, thanks for the report! We investigated the code in depth, and the TLS handling for PBS connections uses the **exact same mechanism** as PVE connections — both use an `undici` Agent with `rejectUnauthorized: false` when "Ignore TLS certificate errors" is enabled. Since the connection was successfully added (which means the validation call to PBS passed with TLS bypass), the `insecureTLS` flag was correctly set at creation time. To help us investigate further, could you: 1. **Show us a screenshot of your PBS connection settings** in the Settings page (the edit dialog), so we can confirm "Ignore TLS certificate errors" is toggled ON 2. **Check the database value** by running this: ```bash docker exec -it <proxcenter-container> sqlite3 /app/data/proxcenter.db "SELECT id, name, insecureTLS FROM Connection WHERE type='pbs';" ``` (Replace `<proxcenter-container>` with your actual container name — use `docker ps` to find it) We want to confirm `insecureTLS` = `1` in your database. If `insecureTLS` is `0`, you can fix it by running: ```bash docker exec -it <proxcenter-container> sqlite3 /app/data/proxcenter.db "UPDATE Connection SET insecureTLS=1 WHERE type='pbs';" ``` Then restart the container. Thanks!

kerem commented

2026-03-13 17:14:35 +03:00

Author

Owner

@adminsyspro commented on GitHub (Mar 3, 2026):

Hi @erwanclx, just following up — we haven't heard back from you on this.

Feel free to reopen it with the requested info (screenshot of PBS connection settings + insecureTLS database value) and we'll be happy to investigate further.

Thanks!

@adminsyspro commented on GitHub (Mar 3, 2026): Hi @erwanclx, just following up — we haven't heard back from you on this. Feel free to reopen it with the requested info (screenshot of PBS connection settings + `insecureTLS` database value) and we'll be happy to investigate further. Thanks!

kerem referenced this issue

2026-03-13 17:21:24 +03:00

[PR #63] [CLOSED] build(deps): bump @mui/x-tree-view from 8.27.1 to 8.27.2 in /frontend #171