Install(signup) page redirected to signin page after changing the default nginx port

[niuguy]

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.11.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1. update the .env file under docker folder , change EXPOSE_NGINX_PORT=80 to EXPOSE_NGINX_PORT=1880
2. Run docker compose up
3. visit http://localhost:1880/install page but got redirected to http://localhost:1880/signin

It's OK if I use the default port

✔️ Expected Behavior

It should allow me to finish signing up on installation page

❌ Actual Behavior

it got redirected automatically before I can do anything

[dosubot[bot]]

Hey there, @niuguy! 👋 I'm here to help you with bug fixes, answer your questions, and guide you on how to contribute. Let's squash those bugs together!

I found a similar discussion where changing the Nginx port caused issues with accessing the "run" page ^[1]. Additionally, there was a closed issue where users experienced continuous spinning on the installation page after deploying Docker locally. The solution involved addressing potential CORS errors by updating configuration items in the docker-compose.yml file to reflect the correct domain ^[2].

To resolve your issue, ensure that the following configuration items in your docker-compose.yml are correctly set to match your domain and port changes:

• CONSOLE_API_URL
• CONSOLE_WEB_URL
• SERVICE_API_URL
• APP_API_URL
• APP_WEB_URL

Also, verify that the CORS settings (CONSOLE_CORS_ALLOW_ORIGINS and WEB_API_CORS_ALLOW_ORIGINS) are configured to allow access from the necessary domains. By default, they should be set to *, which allows access from all domains. This should help prevent the redirection issue you're experiencing.

To continue talking to Dosu, mention @dosu.

[niuguy]

@dosu what's the recommended steps to change the default nginx port

[dosubot[bot]]

To change the default Nginx port, follow these steps:

1. Update the .env File: Modify the EXPOSE_NGINX_PORT variable in your .env file to the desired port number, e.g., EXPOSE_NGINX_PORT=1880.

2. Modify docker-compose.yml: Ensure that all relevant URLs in your docker-compose.yml file reflect the new port. Update the following configuration items:

   • CONSOLE_API_URL
   • CONSOLE_WEB_URL
   • SERVICE_API_URL
   • APP_API_URL
   • APP_WEB_URL

3. Check CORS Settings: Verify that the CORS settings (CONSOLE_CORS_ALLOW_ORIGINS and WEB_API_CORS_ALLOW_ORIGINS) are set to allow access from the necessary domains. Setting them to * allows access from all domains.

4. Restart Docker Containers: Run docker-compose down followed by docker-compose up to apply the changes.

These steps should help you change the Nginx port without encountering redirection issues.

To continue talking to Dosu, mention @dosu.

[niuguy]

OK tried setting up

CONSOLE_API_URL=http://localhost:1880
CONSOLE_WEB_URL=http://localhost:1880
SERVICE_API_URL=http://localhost:1880
APP_API_URL=http://localhost:1880
APP_WEB_URL=http://localhost:1880
FILES_URL=http://localhost:1880
also cors with *
restarted docker-compose but still got the issue. @dosu

[dosubot[bot]]

Ensure that the URLs and CORS settings are correctly configured, and also check the following:

1. Verify Nginx Configuration: Make sure the Nginx configuration in your docker-compose.yml or any related Nginx configuration files are updated to listen on the new port (1880).

2. Check for Hardcoded URLs: Look through your application code and configuration files for any hardcoded URLs or ports that might still be pointing to the default port (80).

3. Database and Cache: Clear any caches or session data that might be storing old URLs or ports. This can sometimes cause redirection issues if the application is using cached data.

4. Logs and Errors: Check the application logs for any errors or warnings that might give more insight into why the redirection is occurring. Look for any specific error messages related to OAuth or URL handling.

5. Network and Firewall: Ensure that there are no network or firewall rules blocking access to the new port.

If these steps don't resolve the issue, consider checking the OAuth callback URLs and any related settings that might be causing the redirection ^[1].

To continue talking to Dosu, mention @dosu.

[crazywoola]

From the information you provided in the description. Step 3 seems to be an expected behavior when you have had setup an account already, the question is, did you setup an account before changing the port, if so and you want to have a fresh install please remove things under docker/volumnns and start the project again.