None of the created workflows are triggering on the production url. I have made the invoked workflows active. And I am trying to invoke them from third party services, but when accessing the production url, no action is triggered on that workflow.
The test URLs work, the processes start and any nodes are executing. But when I call the production URLs, I only see the process start, but I don’t get the result of executing the process that I’ve created inside. Just infinite execution.
I am running n8n on my VPS via portainer on docker compose. I have also configured proxy pass on nginx separately for https. No errors in browser console, webhook responds that the process is running.
Database: PostgresSQL
Queue: Redis
I have not configured any traefik or nginx-proxy manager.
Some details regarding my research. I’ve tried to make a workflow with schedule trigger and activated them. It starts in the intervals what I’ve set in the workflow, but isn’t going to run next node, only works first node.
My webhooks are not getting called from certain sources (404), but for some other sources and even the browser the webhooks seem to work just fine.
And then in some executions the trigger will happen but the flow wont move forward. In other executions it’ll run as expected. And the inconsitency is across executions and not across workflows which makes diagnosing it even more difficult.
I have a few questions. Do I need to configure workers if I am using redis and queue mode? And how can I configure workers if I run via docker compose?
The problem was that I had to configure a worker. Now it’s working with the same configuration. By the way N8N_HOST variable not working for service when you run as worker. Therefore I had to change n8n main service to another port, and worker is runs on the default 5678 port. But in that case the another question comes up, what if you have more then one worker?
Well. if you haven’t changed anything for the worker, than it uses the default 5678 port… that is also used by default by the main instance. You can set up as many workers as you want, but they should listen on different ports, if they are located on the same docker host.
I’ve tried already to use N8N_HOST variable in the service which I configured for the instance worker in docker compose, it starts always on 5678 whether it is defined or not.
