{"id":23023,"date":"2025-12-20T15:23:22","date_gmt":"2025-12-20T14:23:22","guid":{"rendered":"http:\/\/blog.wenzlaff.de\/?p=23023"},"modified":"2025-12-20T19:07:42","modified_gmt":"2025-12-20T18:07:42","slug":"n8n-update-auf-v2-0-3-mit-breaking-change","status":"publish","type":"post","link":"http:\/\/blog.wenzlaff.de\/?p=23023","title":{"rendered":"n8n Update auf v2.0.3 mit breaking change"},"content":{"rendered":"

Dann mal auf die neue v2.0.3 umgestellt. Das ging schon mal schnell (docker compose pull, down und up -d).<\/p>\n

\"n8n<\/p>\n

Leider lief der Backup Workflow nicht mehr. Da hat der breaking change<\/a> zugeschlagen. <\/p>\n

\r\n\r\nSet default value for N8N_RESTRICT_FILE_ACCESS_TO#\r\n\r\nn8n will set a default value for N8N_RESTRICT_FILE_ACCESS_TO to control where file operations can occur. \r\nThis affects the ReadWriteFile and ReadBinaryFiles nodes. By default, these nodes can only access files in the ~\/.n8n-files directory.\r\n\r\nMigration path: Review your workflows that use file nodes and make sure they only access files in the allowed directory. \r\nIf you need to allow access to other directories, set the N8N_RESTRICT_FILE_ACCESS_TO environment variable to your desired path.\r\n\r\n<\/pre>\n
Nach der Erg\u00e4nzung in der docker-compose.yml von N8N_RESTRICT_FILE_ACCESS_TO=\/files und reboot lief es auch wieder.<\/p>\n
Mein Workflow, der \u00fcber ping Server \u00fcberpr\u00fcft, l\u00e4uft auch nicht mehr. Da kommt: Install this node to use it
\nThis node is not currently installed. It is either from a newer version of n8n, a custom node, or has an invalid structure.<\/p>\n
Da muss ein neue Node installiert werden, denn habe ich erst mal deaktiviert.<\/p>\n
Meine KI-Workflows <\/strong>sind leider auch nicht mehr lauff\u00e4hig, das sind aber meine kostenplichtigen API Keys abgelaufen, hat also nichts mit der neuen Version zu tun.<\/p>\n
Gui ist auch etwas neu. Und den migrations Tool<\/a> habe ich auch erst nach dem Update entdeckt und zwar hier:<\/p>\n
\"\"<\/p>\n
Mal sehen was noch alles nicht l\u00e4uft oder anders ist … <\/p>\n","protected":false},"excerpt":{"rendered":"
Dann mal auf die neue v2.0.3 umgestellt. Das ging schon mal schnell (docker compose pull, down und up -d). Leider lief der Backup Workflow nicht mehr. Da hat der breaking change zugeschlagen.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[220,6267],"tags":[6278,2502,6255,5550],"class_list":["post-23023","post","type-post","status-publish","format-standard","hentry","category-anleitung","category-n8n","tag-breaking-change","tag-docker","tag-n8n","tag-workflow"],"_links":{"self":[{"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=\/wp\/v2\/posts\/23023","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=23023"}],"version-history":[{"count":0,"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=\/wp\/v2\/posts\/23023\/revisions"}],"wp:attachment":[{"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=23023"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=23023"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=23023"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}