Which response exactly are you seeing in Postman? Were you perhaps simply not manually executing the workflow (when using the test URL) or didn’t activate your workflow (when using the production URL)?
My worry here is going to be if you are not sure what is happening in that repo will you be able to manage, configure and update the n8n instance on your own moving forwards?
I have not used Ansible for a few years now but it does look like the instance is using nginx as a reverse proxy but it doesn’t look to be blocking the head request, It could be worth checking the nginx logs to see if they show anything. Are you also using anything like Cloudflare?
It is a bit misleading I think having that deploy to digital ocean in the readme with all the ansible instructions.
The one-click install is unrelated to ansible. It’s a “one-click” install app that gets deployed to the digital ocean as an app. The app is built off of the docker image.
I am using cloudflare but the cname is not being proxied.
That is indeed very misleading, when you use the button it then uses this repo to deploy…
There could be more to that, can you check if nginx or anything else is running? It might be worth testing with the ip directly to see if that has the same issue.
Have you added it now? As a test have you tried accessing n8n without going through the proxy or checking the proxy logs that should help show if this is something in n8n or a proxy configuration issue.
Would you not expect to see head in the allowed methods list then? It has already been confirmed as working just over a week ago.
I would start by removing nginx to confirm if the issue is there or not which I suspect it is unless the webhook is not configured for the head method.