Failed to set up HTTPS

[zhz-we]

Self Checks

• 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 (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Dify version

0.15.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Failed to set up HTTPS. After I modified the 【default.conf】 file, stopped the container, and then started it again using docker compose up -d, the 【default.conf】 file was initialized back to its default state, and the port changed from 443 to 80.

the modified

The file modified at 17:00 is initialized to the default state at 17:03 after executing docker compose up -d

✔️ Expected Behavior

set up HTTPS

❌ Actual Behavior

Failed to modify default.conf

[dosubot[bot]]

@zhz-we Hello! I'm here to help you with bug reports, answer questions, and guide you on how to become a contributor.

There are similar discussions related to setting up HTTPS in a self-hosted Docker environment for Dify:

1. How Get SSL - Docker self Hosted - This discussion is still open and might provide insights into SSL setup issues.
2. Help setting up https/SSL with Docker Compose setup - Another open discussion that could be relevant to your problem.
3. How to configurate SSL when Start with Local Source Code - This is also an open discussion that might be helpful ^[1][2][3].

Regarding your issue with the default.conf file being reset, this behavior is likely due to the way Docker handles configuration files. In Dify's Docker setup, configuration files are often mounted as volumes, which means changes made directly inside the container might not persist if the container is restarted. To persist changes, you should modify the configuration files on the host machine where they are mounted from.

For NGINX configurations, ensure that you are editing the correct file on the host machine, such as ./nginx/conf.d/default.conf, and that this file is correctly mounted in your Docker setup. After making changes, restart the Docker containers using the following commands to ensure the changes are applied:

1. Stop the containers:

   docker compose down

2. Rebuild the images if necessary:

   docker compose build

3. Start the services:

   docker compose up -d

Make sure your .env file is up-to-date with any necessary environment variable changes for HTTPS setup ^[4][5].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}