Possible package configuration issue with bounce processing webhook endpoint
-
Hi,
according to the official Listmonk docs, there is an API endpoint for recording bounces.
See: Webhook APIBut the response is 405 Not Allowed (nginx) – anonymized:
curl -X POST -k -u "admin:password" https://sub.domain.tld/webhooks/bounce \ -H "Content-Type: application/json" \ --data '{"email": "eample@listmonk.app", "campaign_uuid": "e8ad4fdb-52e3-4907-b6a3-1c89c7dcb67f", "source": "api_test", "type": "hard", "meta": "{\"additional\": \"info\"}}' <html> <head><title>405 Not Allowed</title></head> <body> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx</center> </body> </html>
You might notice that I had to use the -k flag to ignore SSL issues since that was the first response without ignoring SSL issues:
curl: (60) SSL certificate problem: self signed certificate More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above.
Anyone experiencing same issue?
-
@dev-cb said in Possible package configuration issue with bounce processing webhook endpoint:
You might notice that I had to use the -k flag to ignore SSL issues since that was the first response without ignoring SSL issues
I think you have to start here first. Are you able to visit Listmonnk on your browser without any certificate issue ? If so,
curl https://sub.domain.tld
should work. Does that work ? -
@girish said in Possible package configuration issue with bounce processing webhook endpoint:
If so, curl https://sub.domain.tld should work. Does that work ?
Correct – works as expected.
@girish said in Possible package configuration issue with bounce processing webhook endpoint:
I somehow suspect the request is going to another app or something else. Listmonk doesn't use nginx, so I am not sure why you get a response from nginx...
Nevermind. In the meantime, I found the issue.. Wrong TLD.