[Bug] Path compatibility issue on Windows systems for private key storage #15578

Closed
opened 2026-02-21 19:22:23 -05:00 by yindo · 0 comments
Owner

Originally created by @silencesdg on GitHub (Jul 22, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.6.0

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

  1. Set up Dify on a Windows machine
  2. Configure tenant-specific private keys
  3. Attempt to access the private key file at runtime
  4. Observe the file access error

✔️ Expected Behavior

The system should correctly locate and access private key files (private.pem) regardless of the operating system (Windows/Linux/macOS).

Actual Behavior

On Windows systems:

The hardcoded Linux-style path "privkeys/{tenant_id}/private.pem" fails to resolve
Results in FileNotFoundError when trying to access the key file
Prevents normal operation of key-dependent features

Originally created by @silencesdg on GitHub (Jul 22, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.6.0 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce 1. Set up Dify on a Windows machine 2. Configure tenant-specific private keys 3. Attempt to access the private key file at runtime 4. Observe the file access error ### ✔️ Expected Behavior The system should correctly locate and access private key files (private.pem) regardless of the operating system (Windows/Linux/macOS). ### ❌ Actual Behavior On Windows systems: The hardcoded Linux-style path "privkeys/{tenant_id}/private.pem" fails to resolve Results in FileNotFoundError when trying to access the key file Prevents normal operation of key-dependent features
yindo added the 🐞 bug label 2026-02-21 19:22:23 -05:00
yindo closed this issue 2026-02-21 19:22:23 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#15578