Critical Bug: n8n latest (v1.109.2) on Docker silently FAILS to load any custom nodes on Hostinger VPS

[ibonazkoitia]

Hello,

I have a custom n8n on a Hostinger VPS and cannot load any custom nodes. The node simply does not appear in the UI, and there are no errors in the n8n logs, even with N8N_LOG_LEVEL=debug set.

The debug logs show that n8n is not even attempting to scan for custom node directories. It completely skips the step.

Environment:

• Provider: Hostinger VPS

• Setup: Official docker-compose.yml with Traefik

• n8n Version: 1.109.2 (latest)

We have exhaustively debugged every possible cause, and the issue persists even with the official n8n-nodes-starter example.

Troubleshooting performed:

• Confirmed correct file paths and permissions (owner 1000:1000, verified with ls -ln inside the container).

• Fixed all potential case-sensitivity issues in package.json and filenames.

• Discovered and disabled the docker-default AppArmor profile for the container using security_opt: ["apparmor=unconfined"].

• Attempted both installation methods: volume mounting and building a custom Docker image with the nodes baked in. Both methods fail in the same silent way.

• Explicitly set the N8N_CUSTOM_EXTENSIONS_DIR environment variable.

Any idea what else could I do?

PD: In a local installation, the node works fine. We sent it to production via GitHub and the ‘npm run build’ works fine without errors.

Thank you very much,
Ibon.