-
Notifications
You must be signed in to change notification settings - Fork 4.5k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
How to deploy DIFY via Docker on Linux? After deployment, Windows can access the webpage #4535
Comments
To deploy DIFY via Docker on a Linux system and make it accessible from a Windows machine using an IP address, follow these steps:
This approach does not require additional Docker configuration beyond ensuring correct port binding for network accessibility. If you face any issues, please share the error messages or describe the problems for further assistance.
|
Do you want to access the page by your public IP or internal? |
I'm sorry, I don't know whether it's an internal IP or a public IP,but i want to access the page by ip,which ifconfig is belong to ens192.what’s more |
To resolve the "113: no route to host while connecting to upstream" error in your Docker logs for Nginx and ensure the webpage is accessible via the IP address 1.1.1.1 from a Windows machine, follow these steps:
By following these steps, you should be able to resolve the "113: no route to host while connecting to upstream" error and ensure that the webpage is accessible via the IP address 1.1.1.1 from a Windows machine.
|
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Self Checks
Provide a description of requested docs changes
How to deploy DIFY via Docker on Linux? After deployment, Windows can access the webpage using the IP address http://xx.xx.xx.xx:80 instead of http://localhost:80.
The text was updated successfully, but these errors were encountered: