NGINX_HTTPS_ENABLED is set to false, but it still try to open 0.0.0.0 443

[cpjcore]

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

1.3.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

NGINX_HTTPS_ENABLED is set to false, in .env, in docker-compose.yaml and anywhere I can find
NGINX_HTTPS_ENABLED=false
It still tried to open 443 port

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot[bot]]

Hello @cpjcore! I'm Dosu, a friendly bot here to help you with bugs, answer questions, and assist you in becoming a contributor. I'm here while you wait for a human maintainer. Let's tackle this issue together!

I found similar threads discussing issues with NGINX port configurations:

1. How to change the default ports of nginx 80 and 443 - This thread is open and discusses changing default NGINX ports ^[1].
2. Why is my modification of nginx port invalid? - This thread is open and addresses issues with port modifications not taking effect ^[2].
3. How can I use the docker setup behind an nginx proxy? I already have nginx on my host system and docker seems to want to install its own which conflicts with port 80 - This thread is open and discusses port conflicts with existing NGINX installations ^[3].

Regarding your issue, even when NGINX_HTTPS_ENABLED is set to false, the default behavior is to use HTTP on port 80, and SSL settings should not be applied ^[4]. However, if port 443 is still being used, it might be due to a configuration override or a conflict with another service.

To resolve the port conflict, you can:

1. Check if another service is using port 443:

   sudo netstat -tuln | grep :443

2. Stop any service using port 443:

   sudo service nginx stop

3. Modify the EXPOSE_NGINX_SSL_PORT variable in your .env file to a different port, such as EXPOSE_NGINX_SSL_PORT=8443, and restart your Docker services:

   docker compose down
   docker compose up -d

These steps should help resolve the port conflict ^[5][1].

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}

[cpjcore]

@dosu I know that I can avoid conflicts by changing the SSL port number. However, the problem is that when the NGINX_HTTPS_ENABLED is set to false, Dify should not attempt to open the SSL port. The configuration of NGINX_HTTPS_ENABLED doesn't work. Isn't this a bug?