Unable to config gotify for notifications

skal

New Member
Aug 18, 2023
3
0
1
Hi all,
today I've tried for the first time to use gotify as notifications system.
the problem is that everytime I try to register the server I get the following error
Code:
unknown permission test at /usr/share/perl5/PVE/RPCEnvironment.pm line 536. (500)
Does anyone know how to fix it?
tnx for your support :-)
 
hi,
can you give a screenshot/more detailed description of what you're trying to configure?

also the exact versions of the pve server would be interesting (pveversion -v)
 
I'm getting the same problem when configuring a webhook (pve 8.3.0) @dcsapak

Datacenter > Notifications > Add webhook > add secret > set key and value > press "Add". I get the above error at that moment

This is the request / response coming off the browser:

YAML:
url: https://vault:8006/api2/extjs/cluster/notifications/endpoints/webhook
post_data: |
  name=Telegram
  method=post
  url=https://api.telegram.org/bot${api_key}/sendMessage
  secret=name=api_key,value=MY_B64_SECRET
req_headers: |
  POST /api2/extjs/cluster/notifications/endpoints/webhook HTTP/1.1
  Host: vault:8006
  User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:132.0) Gecko/20100101 Firefox/132.0
  Accept: */*
  Accept-Language: en-GB,en;q=0.5
  Accept-Encoding: gzip, deflate, br, zstd
  CSRFPreventionToken: YOLO
  Content-Type: application/x-www-form-urlencoded; charset=UTF-8
  X-Requested-With: XMLHttpRequest
  Content-Length: 197
  Origin: https://vault:8006
  DNT: 1
  Connection: keep-alive
  Referer: https://vault:8006/
  Cookie: PVEAuthCookie=XXXXXXX
  Sec-Fetch-Dest: empty
  Sec-Fetch-Mode: cors
  Sec-Fetch-Site: same-origin
  Priority: u=0
  Pragma: no-cache
  Cache-Control: no-cache
resp_headers: |
  HTTP/1.1 200 OK
  Cache-Control: max-age=0
  Connection: Keep-Alive
  Date: Wed, 27 Nov 2024 14:31:32 GMT
  Pragma: no-cache
  Server: pve-api-daemon/3.0
  Content-Length: 128
  Content-Type: application/json;charset=UTF-8
  Expires: Wed, 27 Nov 2024 14:31:32 GMT
resp_body: {"status":500,"message":"unknown permission test at /usr/share/perl5/PVE/RPCEnvironment.pm line 536.\n","success":0,"data":null}

1732718132309.png

Code:
~ pveversion --verbose
proxmox-ve: 8.3.0 (running kernel: 6.8.12-4-pve)
pve-manager: 8.3.0 (running version: 8.3.0/c1689ccb1065a83b)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-4
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
proxmox-kernel-6.8.12-2-pve-signed: 6.8.12-2
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.0
libpve-storage-perl: 8.2.9
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.2.9-1
proxmox-backup-file-restore: 3.2.9-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.1
pve-cluster: 8.0.10
pve-container: 5.2.2
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-1
pve-ha-manager: 4.0.6
pve-i18n: 3.3.1
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.0
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1
 
Last edited:
  • Like
Reactions: constvoidptr
I can confirm that I am experiencing the exact same behavior as of Proxmox VE 8.3.0 with any type of notification. Same server response, same error message in the same script at the same line.

Code:
proxmox-ve: 8.3.0 (running kernel: 6.11.0-1-pve)
pve-manager: 8.3.0 (running version: 8.3.0/c1689ccb1065a83b)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.11.0-1-pve-signed: 6.11.0-1
proxmox-kernel-6.11: 6.11.0-1
proxmox-kernel-6.8: 6.8.12-4
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
proxmox-kernel-6.8.12-2-pve-signed: 6.8.12-2
proxmox-kernel-6.8.12-1-pve-signed: 6.8.12-1
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.1
libpve-storage-perl: 8.2.9
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.0-1
proxmox-backup-file-restore: 3.3.0-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.3
pve-cluster: 8.0.10
pve-container: 5.2.2
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-1
pve-ha-manager: 4.0.6
pve-i18n: 3.3.2
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.0
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1
 
I'm getting the same problem when configuring a webhook (pve 8.3.0) @dcsapak

Datacenter > Notifications > Add webhook > add secret > set key and value > press "Add". I get the above error at that moment

This is the request / response coming off the browser:

YAML:
url: https://vault:8006/api2/extjs/cluster/notifications/endpoints/webhook
post_data: |
  name=Telegram
  method=post
  url=https://api.telegram.org/bot${api_key}/sendMessage

[/QUOTE]
Oh, and by the way, the syntax for accessing secrets is {{ secrets.api_key }} - these are Handlebars template strings and all secrets are available in a 'secrets' namespace :)
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!