N8n Blocks Workflow Renaming

Other Questions N8n
1

Using Docker Compose, n8n works for creating, executing, and deleting workflows—but renaming is disabled. See the revised configuration below:

version: '3.8'
services:
  workflow_app:
    image: n8nio/n8n:stable
    ports:
      - "8080:5678"
    environment:
      - ENC_KEY=abc123xyz
      - COOKIE_SECURE=false
      - AUTH_ON=true
      - USER_NAME=wf_user
      - USER_PASS=secret
      - APP_PROTO=https
      - HOOK_ADDR=https://example
      - DB_KIND=pgdb
      - PG_DB=sample_db
      - PG_HOST=pg_server
      - PG_PORT=5432
      - PG_USER=wf_user
      - PG_SCHEMA=public
      - PG_PASS=sample
    volumes:
      - data_vol:/home/node/data
    depends_on:
      - pg_server
  pg_server:
    image: postgres:14
    environment:
      - POSTGRES_DB=sample_db
      - POSTGRES_USER=wf_user
      - POSTGRES_PASS=sample
    volumes:
      - pg_data:/var/lib/postgresql/data
volumes:
  data_vol:
  pg_data:
2

Based on my experience managing similar setups, I encountered a situation where workflow renaming was disabled due to an interdependency between certain environment variables and the reverse proxy settings. I noticed that if APP_PROTO and HOOK_ADDR are not perfectly synchronized with your external HTTPS endpoints, it might inadvertently lock certain features like renaming. I resolved this issue by double-checking the consistency of these values and ensuring the containers were restarted to reflect the changes. Additionally, reviewing the DB schema configuration helped me pinpoint the source of the problem.