Dify企业版,从3.5.6升级到3.6.0,之后,所有的接口请求都是401 Unauthorized了,{"code":"unauthorized","message":"CSRF token is missing or invalid.","status":401}

enterprise:
  enabled: true
  image:
    # g-hsod9681-docker.pkg.coding.net/dify-artifact/dify/dify-enterprise
    repository: langgenius/dify-enterprise
    tag: "0.12.5"
  replicas: 1
  resources: {}
  nodeSelector: {}
  affinity: {}
  tolerations: []
  readinessProbe:
    failureThreshold: 3
    httpGet:
      path: /v1/healthz
      port: 8082
      scheme: HTTP
    initialDelaySeconds: 30
    periodSeconds: 10
    successThreshold: 1
    timeoutSeconds: 3
  livenessProbe:
    failureThreshold: 3
    httpGet:
      path: /v1/healthz
      port: 8082
      scheme: HTTP
    initialDelaySeconds: 20
    periodSeconds: 10
    successThreshold: 1
    timeoutSeconds: 3
  extraEnv:
  # Apply your own Environment Variables if necessary. Below is demo.
  # extraEnv:
  #   - name: ENV_FROM_COMMUNITY1
  #     value: env123
  #   - name: ENV_FROM_COMMUNITY2
  #     value: env123
  appSecretKey: "#REPLACE_ME#"
  adminAPIsSecretKeySalt: "#REPLACE_ME#"
  innerApi:
    enabled: true
  corsOrigins: "所有组件的域名,这里不列出了"

这个是3.5.6部署的时候,配置的跨域的方式,是生效的。

但是到了3.6.0之后,就没有这个参数了,然后再gateway会多出一个

gateway:
  replicas: 1
  image:
    # g-hsod9681-docker.pkg.coding.net/dify-artifact/dify/enterprise_gateway
    repository: langgenius/enterprise_gateway
    tag: 0.13.0
  resources: {}
  nodeSelector: {}
  affinity: {}
  tolerations: []

  # additional origins to allow CORS requests from
  # if left empty, only dify domains will be allowed
  allowOrigins:
    - 所有组件的域名,这里不列出了
    - 所有组件的域名,这里不列出了
    - 所有组件的域名,这里不列出了

然后我也配置了,结果,helm upgrade之后,

页面很多链接全是401了

就算把之前3.5.6的参数也一起加上,一样没效果,现在整个环境直接就不可用了,回滚到3.5.6,api组件的pod也起不起来,直接启动不起来,
日志提示这个

/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
/entrypoint.sh: line 7: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Running migrations
2025-12-12 09:28:01,267.267 INFO [MainThread] [utils.py:164] - NumExpr defaulting to 16 threads.
2025-12-12 09:28:06,241.241 INFO [MainThread] [aws_s3_storage.py:27] - Using ak and sk for S3
Preparing database migration…
Starting database migration.
INFO [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO [alembic.runtime.migration] Will assume transactional DDL.
ERROR [flask_migrate] Error: Can’t locate revision identified by ‘03f8dcbc611e’

现在相当于,回滚也不能回滚,升级了请求都是401,整个环境直接没用了