I have same problem as here: https://community.n8n.io/t/aws-sns-cant-confirm-the-subscription/30555 and I saw on github similar which has never solved.
Webhook as same as AWS SNS doesn’t work properly. In this case I have Pending confirmation the only way and only sometimes it works when I reset n8n and quickly run: send an event. I can send event once time. This is work also with Webhook I can receive an event once time.
Hi @GGG1998 thanks for reaching out and joining the community!
I see the article you’ve referenced. @barn4k I know the article referenced is a bit old but do you recall if you were ever able to resolve your AWS SNS issues?
Some additional resources that might be helpful before I also try to replicate this:
SNS works fine with python or CLI. The problem is with subscriber n8n.
Create new credentials
Test with python, test with cli
I’ve never touch the limit
What happens when I create a tunnel with your server? How long is it alive? What are the rules for incoming request? Diverging a bit from SNS and little focus on your server hook. I’ve mentioned about it because node that need receive data from hook doesn’t work. For example, Node webhook returns 408 code
Actually, I don’t remember, but I suppose there was an issue with the proper fqdn names for internal n8n address and the one used for the webhooks (we have different fqdns for internal/external traffic)
