What are the steps to upgrade Dify 1.9.2 to Dify 1.15.0?

[gongchangping]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

My Dify instance was upgraded from Dify 1.0.0 to Dify 1.9.2. Now I plan to upgrade it further to Dify 1.15.0. Is this upgrade path supported? How should I perform the operation? My Dify is deployed via Docker Compose, and I need to retain all existing original data.

[dosubot[bot]]

Yes, upgrading from 1.9.2 to 1.15.0 directly is supported — Dify's Alembic-based migration system handles sequential schema changes automatically. However, there are several critical issues to be aware of since you're jumping across multiple major releases. Here's the full procedure:

Upgrade Steps (Docker Compose)

1. Back up everything first:

# Database backup
docker compose exec db pg_dump -U postgres dify > dify_backup_1.9.2.sql

# Copy your volumes directory as well
cp -r ./volumes ./volumes_backup

2. Stop services, pull new images, and update .env:

docker compose down
docker compose pull

3. Update environment variables — key changes required between 1.9.2 and 1.15.0:

• SSRF proxy policy (1.15.0 breaking change): The SSRF proxy now blocks all private/RFC-1918 IPs by default. If your workflows call internal services, add allowlist entries [1]:

  SSRF_PROXY_ALLOW_PRIVATE_DOMAINS=internal.mycompany.com
  SSRF_PROXY_ALLOW_PRIVATE_IPS=10.10.5.42,192.168.1.0/24
  

• Plugin daemon URL must use the container service name [2]:

  PLUGIN_DAEMON_URL=http://plugin_daemon:5002
  

4. Start services and run migrations:

docker compose up -d
docker compose exec api flask upgrade-db
docker compose exec api flask backfill-plugin-auto-upgrade

[3]

5. Apply the model_type enum SQL fix — this is a known issue from 1.14.x that affects upgrades. Run against your dify database [4]:

-- Run for each table: provider_models, provider_model_credentials,
-- tenant_default_models, provider_model_settings, load_balancing_model_configs
UPDATE provider_models SET model_type = 'llm' WHERE model_type = 'text-generation';
UPDATE provider_models SET model_type = 'text-embedding' WHERE model_type = 'embeddings';
UPDATE provider_models SET model_type = 'rerank' WHERE model_type = 'reranking';

UPDATE provider_model_credentials SET model_type = 'llm' WHERE model_type = 'text-generation';
UPDATE provider_model_credentials SET model_type = 'text-embedding' WHERE model_type = 'embeddings';
UPDATE provider_model_credentials SET model_type = 'rerank' WHERE model_type = 'reranking';

UPDATE tenant_default_models SET model_type = 'llm' WHERE model_type = 'text-generation';
UPDATE tenant_default_models SET model_type = 'text-embedding' WHERE model_type = 'embeddings';
UPDATE tenant_default_models SET model_type = 'rerank' WHERE model_type = 'reranking';

UPDATE provider_model_settings SET model_type = 'llm' WHERE model_type = 'text-generation';
UPDATE provider_model_settings SET model_type = 'text-embedding' WHERE model_type = 'embeddings';
UPDATE provider_model_settings SET model_type = 'rerank' WHERE model_type = 'reranking';

UPDATE load_balancing_model_configs SET model_type = 'llm' WHERE model_type = 'text-generation';
UPDATE load_balancing_model_configs SET model_type = 'text-embedding' WHERE model_type = 'embeddings';
UPDATE load_balancing_model_configs SET model_type = 'rerank' WHERE model_type = 'reranking';

Note: For tenant_default_models, if you get a duplicate key error, delete the old rows first:

DELETE FROM tenant_default_models WHERE model_type IN ('text-generation','embeddings','reranking');

6. Verify plugin daemon version — Dify 1.15.0 requires plugin daemon 0.6.3-local. Check with:

docker compose logs plugin_daemon | head -20

[2]

7. Clean up stale plugin directories once plugins are confirmed working in the UI [5].

Quick Checklist

• Database and volumes backed up
• .env updated (SSRF allowlists, plugin daemon URL)
• docker compose up -d with new images
• flask upgrade-db completed
• flask backfill-plugin-auto-upgrade completed
• model_type SQL fix applied
• Plugin daemon version verified (0.6.3-local)
• HTTP nodes / internal API calls tested
• Stale plugin directories cleaned up

All your existing data (conversations, workflows, knowledge bases, etc.) will be preserved — the migrations only add/modify schema, they don't delete user data.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.