Setting up a new N8N but has to be behind Nginx (personal instance, cant afford another server for N8N). The setup with Nginx works except for the Webhooks.
I setup a simple workflow (as below), “Test Workflow”, then the WebHook starts listening. I take the Webhook Test URL in Postman (GET + URL) and send the request.
Response:
Status: 200 OK
Payload:
HTML Page Source Code with title “n8n.io - Workflow Automation” and body that says:
<noscript>
<strong
>We're sorry but the n8n Editor-UI doesn't work properly without JavaScript enabled. Please
enable it to continue.</strong
>
</noscript>
NOTE: The workflow does not trigger, does not timeout and I cannot stop the execution.
New Note 1 : Everytime I execute a workflow I see the following line in the log:
pf_n8n | The session “XXXXXXXXX” is not registered.
New Note 2 : I cannot even execute a Workflow with Manual Trigger. This makes me think on why the I would get the specific message in Postman. May be the Workflow is not actually getting triggered and hence there is no Webhook to call?
Hi @sg_tech! Thanks for reaching out! I appreciate you sharing the incremental steps you’ve taken to resolving the issues you’re seeing.
From your latest message it sounds like you’re now able to trigger the workflow, stop the workflow, but you are trying to access the editor via Postman and hence seeing the noscript message, correct? Have you tried to access the editor from your browser?
Ah thank you for the clarity there. Yes, the webhook url would not be accessible from the browser as that should just be the destination for the request. From Postman you would normally expect the output from successfully calling a webhook to be {"message":"Workflow was started"}%
Is the response the same if you activate the workflow and use the non-test webhook url?
Additionally, here are some resources that might be useful:
Ok, I’ve spent about 3 additional hours trying to solve this but nothing seems to work.
Tried several ways to remove the Webhook issue but no luck.
I have set up n8n for a POC on my company network on the root nginx path i.e. /, so now I exposed it via an additional nginx server block with a sub-domain but no luck again.
Tomorrow I am going to try and run it with nginx → npm and see if it works. I hope it does.
If not, then I will not be able to have a dedicated VM in my company cloud just for n8n.
We will have to drop plans for self-hosted pro/ent package and try and find some other alternative