in the meantime I figured out my problem. My let’s encrypt certificate was not valid anymore - well to be precise: it was successfully renewed and it was actually valid. I did quickly check using
openssl x509 -text -in -noout certname.pem on my server - The thing was that my webserver (nginx) didn’t realize the renewal and only after I restarted nginx it started using the renewed cert.
Anyway, it would have helped a lot with debugging when the Pipedrive UI just would have stated that the cert’s date is not valid anymore. I think this is not to much to ask from a developer friendly interface. Any browser can do it, any programming library can easily find out that a cert’s date is due. I think it’s not too much to ask to implement this feature.
But just stating the word Error is not helpful at all. Thanks a lot for considering on improving this feature!
Regarding your quote of the docs, I have to be honest with you: What it states is either just not true or the quality of your support is lacking drastically:
If you encounter this error, you can contact our support team, who can further inquire into the logs of these requests.
In my case when I asked support what Error means and why there is no proper error message pointing to the source of the problem I got exactly this answer:
But as I’ve mentioned, here on support we will not be able to provide you technical support about webhooks and our developers do not provide support to users
And to be precise, the sending of a log file was definitely suggested in my messages:
My question is if you
could tell me how to debug issues with webhooks without having a log
Sending a log file for analysis was never suggested by the support agent…
So, well I have to be honest with you: This was the worst support experience I had in quite some time. There is lots of room for inprovement.