Workflow node icons return 404 (self-host, npm)

Describe the problem/error/question

All node icons in workflow editor UI return 404s after standard npm install n8n@latest -g
(.cache/n8n/public/types/nodes.json shows all icons arg at iconUrl: “icons/n8n-nodes-base/dist/nodes/example.example.svg” - but no assets created on install. did i miss a step in the process?).

Are these icon assets downloaded to the self-hosted instance only after running a build? if so, please let me know if i just needed to run $ npm run build in the project root dir to copy these assets over.

I’ve read through the previous related posts but haven’t found the solution. Also see the same issue after clearing browser cache & accessing editor UI in a private window.

I tested possible setup issues by manually creating the missing icon asset directories and a few icon files in the project root and obv get a 200 res (not 404) for those that exist on the server.

An older post on the forum mentioned a possible proxy issue blocking access to your servers, but didn’t see any url to whitelist for this solution.

Another possibility - are these files only included if the n8n-config.json file has the node in the “include” array, or are all nodes included by default? I’ve excluded a few nodes, but my “include” array is empty. All nodes themselves exist and function fine in the editor, however, just no icons.

What is the error message (if any)?

404

n8n setup

  • n8n version: 1.49.0
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm (via pm2)
  • Operating system: Apache/Debian (Cloudways)

Debug info

core

  • n8nVersion: 1.49.0
  • platform: npm (via pm2)
  • nodeJsVersion: 20.15.0
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: community
  • consumerId: unknown

storage

  • success: none
  • error: all
  • progress: false
  • manual: true
  • binaryMode: memory

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

security

  • blockFileAccessToN8nFiles: true

Hey @chase.sound,

Welcome to the community :cake:

This sounds like it is going to be the cache issue, We have seen a few of them recently. The icon assets are included in the npm package so shouldn’t be missing.

I would recommend the Docker image to see if you have the same issue with that as well.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.