Lot of nodes not recognized anymore after reinstalling Docker official image

Worked on a workflow, everything working fine, then i had to reinstall the docker image from start and import the json workflow again.
Even after installing the latest version of n8n, many nodes, including Gemini and Puppeteer, are not visible, even if installed via “Community nodes.” Even basic nodes like the Form trigger are unrecognized. My exported working flow shows for example unrecognized trigger form node at version 2.3, while newly added node show version 2. It seems workflows were created in a version that had updated nodes, which are now not compatible with n8n 1.110.1.

#Dockerfile

FROM n8nio/n8n:latest

USER root

RUN apk add --no-cache \
    chromium \
    nss \
    freetype \
    harfbuzz \
    ttf-freefont \
    ghostscript \
    && rm -rf /var/cache/apk/*

USER node

ENV PUPPETEER_EXECUTABLE_PATH="/usr/bin/chromium"

docker-compose.yaml

services:
  n8n:
    build: .
    container_name: n8n_container
    user: root
    environment:
      - NODE_OPTIONS=--max_old_space_size=4096
      - N8N_SECURE_COOKIE=false
      - N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true
      - N8N_PORT=5678
      - N8N_DEFAULT_BINARY_DATA_MODE=filesystem
      - PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium
      - N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=false
    ports:
      - "5678:5678"
    volumes:
      - ./n8n_data:/home/node/.n8n
      - /tmp:/tmp
      - ./entrypoint.sh:/entrypoint.sh
    entrypoint: ["/entrypoint.sh"]

#entrypoint.sh

#!/bin/sh
# entrypoint.sh

apk add --no-cache chromium nss freetype harfbuzz ttf-freefont ghostscript

su node -c "n8n start"

#[details=“instance information”]

Debug info

core

  • n8nVersion: 1.110.1
  • platform: docker (self-hosted)
  • nodeJsVersion: 22.19.0
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: community

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

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

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/139.0.0.0 safari/537.36
  • isTouchDevice: false

security

  • secureCookie: false

Generated at: 2025-09-08T18:50:51.249Z}
[/details]

This is a node i added yesterday:

{
      "parameters": {},
      "type": "n8n-nodes-base.formTrigger",
      "typeVersion": 2.3,
      "position": [
        352,
        -32
      ],
      "id": "172d955e-4add-4dee-aadb-5e4ea8f5bcfb",
      "name": "On form submission",
      "webhook
Id": "98057bbb-13a2-40d9-81b5-4bbd83be4354"
    }

Then i messed up stuff on docker and decided to start fresh, now the same working node it’s not being recognized anymore, can’t find gemini in the node list and can’t see puppeteer node after installing it anymore

If i add the same node now it’s like this

{
      "parameters": {
        "path": "8d213ec6-cca4-4d1a-8ff7-0d0e4f9f9f89",
        "formFields": {
          "values": [
            {}
          ]
        },
        "options": {}
      },
      "type": "n8n-nodes-base.formTrigger",
      "typeVersion": 2,
      "position": [
        352,
        128
      ],
      "id": "5fdb9eed-e850-440a-807a-00483d296f49",
      "name": "n8n Form Trigger",
      "webhookId": "8d213ec6-cca4-4d1a-8ff7-0d0e4f9f9f89"
    }

this is the same for basically all the nodes except gmail send, there’s something with typeVersion, i guess…
to be clear: everything was working fine yesterday, zero problems

It sounds crazy, but it was the ADGUARD extension for Chrome. I’m at a loss for words. Disabled, refreshed, workflow restored.

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