Debug Test Workflow 'Listen for Test Event' Issue in n8n Docker On-Premise Setup

Below is one common cause and suggestion for this issue:

Check Your Port Mapping

Your provided Docker command omits a port mapping. When running n8n in Docker, you need to expose the container’s port so that incoming webhook requests (including those from the “Listen for test event” feature) are routed correctly. For example, running:

SHCopied
docker run -d --name n8n \
  -p 5678:5678 \
  -e DB_TYPE=sqlite \
  -e N8N_PORT=5678 \
  n8nio/n8n:latest

ensures that n8n is accessible on port 5678 of your host. Without the -p 5678:5678 mapping, webhook or test event requests might never reach your container—even if they are logged internally in the Executions tab.

Other Points to Verify

• Environment Variables:
  If you’re behind a reverse proxy or using a custom domain, ensure the proper WEBHOOK_URL and related environment variables are set. The test event functionality relies on n8n knowing its correct external URL.

• Persistent Data:
  Although not directly linked with test mode in your case, ensuring proper data persistence (e.g., mounting the /home/node/.n8n directory) is beneficial for overall workflow reliability.

Final Suggestion

Revise your Docker startup command to include port mapping (and any necessary environment variables for your network configuration) so that test events can reach the container:

SHCopied
docker run -d --name n8n \
  -p 5678:5678 \
  -e DB_TYPE=sqlite \
  -e N8N_PORT=5678 \
  n8nio/n8n:latest

This should allow the “Listen for test event” functionality to work as expected in the n8n Editor.

If issues persist after ensuring proper port mapping and configuration, reviewing the container logs might provide additional clues for further troubleshooting.