You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
1. Is this request related to a challenge you're experiencing? Tell me about your story.
I've successfully deployed Dify on a virtual machine within the intranet at 192.168.1.37 and can access it normally through port 80. However, I now need to provide external access via port 81 on this machine. Since other applications also share port 81, I've configured a reverse proxy (192.168.1.37:81/th-dify) for user access to Dify.
I found an solution(#7457) that suggests modifying the Nginx configuration and the .env file, which I've done as follows:
When accessing the webpage at http://192.168.1.37:81/th-dify, it automatically redirects to http://192.168.1.37:81/apps, and I see a 404 error in the browser's F12 debugging tools. Here's a screenshot:
Direct access to http://192.168.1.37/th-dify also results in a 404 error:
Accessing http://192.168.1.37/ redirects to http://192.168.1.37:81/apps, and the F12 debugging tools show a 404 error for the backend request address:
Is there any configuration I might have missed? Could you please assist me in resolving this issue? I would greatly appreciate your help.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
I've successfully deployed Dify on a virtual machine within the intranet at 192.168.1.37 and can access it normally through port 80. However, I now need to provide external access via port 81 on this machine. Since other applications also share port 81, I've configured a reverse proxy (192.168.1.37:81/th-dify) for user access to Dify.





I found an solution(#7457) that suggests modifying the Nginx configuration and the .env file, which I've done as follows:
When accessing the webpage at http://192.168.1.37:81/th-dify, it automatically redirects to http://192.168.1.37:81/apps, and I see a 404 error in the browser's F12 debugging tools. Here's a screenshot:
Direct access to http://192.168.1.37/th-dify also results in a 404 error:
Accessing http://192.168.1.37/ redirects to http://192.168.1.37:81/apps, and the F12 debugging tools show a 404 error for the backend request address:
Is there any configuration I might have missed? Could you please assist me in resolving this issue? I would greatly appreciate your help.
2. Additional context or comments
No response
Beta Was this translation helpful? Give feedback.
All reactions