Why is my modification of nginx port invalid?

[bbhxwl]

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

docker-compose.yaml
I modified the port, why can't it take effect?

[dosubot[bot]]

I found 9 similar discussions and issues that might be helpful:

• Node.js Error: "PORT is already in use" - This thread discusses how to resolve port conflicts by killing the process using the port or changing to a different port, which is relevant to your issue with NGINX.

• How to change the default ports of nginx 80 and 443 - This discussion explores changing default NGINX ports but does not provide a solution.

• General Discussion - A general discussion thread without a specific solution.

• General Discussion - Another general discussion thread without a specific solution.

• Invalid docker-compose.yaml file change - This issue provides a solution for ensuring that port changes in docker-compose.yaml take effect, which may help you resolve your NGINX port issue.

• API url error if the port is modified to other ports in the nginx part in docker-compose.yaml - This issue suggests updating environment variables in the api and web services to reflect new ports, which is directly related to your problem.

• Nginx is listening on port 80 instead of the value of ${NGINX_PORT} that I set in the .env file. - This issue was resolved by a pull request, indicating a fix for similar problems with NGINX port settings.

• App port no change after change the EXPOSE_NGINX_PORT - This closed issue provides a solution for ensuring the app URL reflects the custom port specified in the .env file.

• Not effective after modifying the value of EXPOSE_NGINX_PORT in the .env file - This issue discusses ensuring that Docker containers are restarted after modifying the .env file, which is crucial for your situation.

• Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use - This issue was resolved by stopping another service using the port, which is relevant to your NGINX port conflict.