Replies: 1 comment
|
Hi @ntruhan. These are randomly auto generated at container start. Restarting the container would have solved it for you. You can optionally provide your own by setting the webhookSecret in .env. https://jamcalli.github.io/Pulsarr/docs/development/environment-variables#security--sessions |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
My webooks had been working fine for a while from Sonarr and Radarr into Pulsarr. However, recently they stopped connecting and checking the Connections within Sonarr and Radarr I was receiving:
Unable to send test message: Unable to post to webhook: HTTP request failed: [401:Unauthorized] [POST] at [http://192.168.2.207:3003/v1/notifications/webhook?instanceId=xxxx]
I couldn't figure out in Pulsarr where to get the X-Pulsarr-Secret from or how it determined what he instanceId was, so after a while I just gave up and deleted and re-created Sonarr. When I did, I saw it recreated the webhook but it had a new Secret and tested successfully.
I copied that secret from Sonarr over to the webhook in Radarr and updated it and then it started testing successfully as well.
Since I can't seem to find this elsewhere, I am requesting either something in the instance settings to refresh its webhook, which would recreate it with the latest settings, or something say under utilities, that will allow copying out the X-Pulsarr-Secret so any webhooks that rely on it can be updated.
All reactions