-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After deploying the non-80 port, publish the application and jump to the new web page to carry the port. #4449
Comments
To address the "404 Not Found" error when accessing your application on port 3000, ensure the following:
In your Dify uses the By following these steps and ensuring correct configuration and environment setup, you should be able to resolve the "404 Not Found" error and access your web page on port 3000.
|
I don't really get the issue here. Have you change something in docker-compose file? |
So you should access the web on that port http://localhost:10034 |
I used a reverse proxy tool to proxy http://localhost:10034/ to the public network. Then when I used "publish", the port would disappear when jumping. __ |
may be web should add nginx expose-port config, rather than always use 80 |
docker-compose.yml,needs to modify Api: environment variables, APP_WEB_URL,SERVICE_API_URL,fill in 'http://ip:nginx expose-port' |
Yes my problem is solved now__ |
Self Checks
Dify version
latest
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
✔️ Expected Behavior
You should also need to carry port 3000 before you can use it after the jump__
❌ Actual Behavior
After deploying the non-80 port, publish the application and jump to the new web page to carry the port.
The text was updated successfully, but these errors were encountered: