Help：I want all the requests sent by the front end to have the path prefix

[faruzanCN]

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.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I deployed Dify using the official Docker image and attempted to modify all API addresses in the .env file by adding the prefix "/dify", but it didn't work. First, the frontend pages did not include the "/dify" prefix in their URLs. Second, although API requests did include the "/dify" prefix, they returned 404 errors. Why is there such a requirement? This is because certain network environments do not allow arbitrary ports to be opened. Therefore, sharing the same port with other systems via path-based routing in an Nginx reverse proxy becomes necessary. This approach also enables leveraging existing application authentication mechanisms, thereby enhancing security management.

2. Additional context or comments

and if i edit "dify/docker/nginx/conf.d/default.conf", the weibsit "http://127.0.0.1/dify" will 404

[dosubot[bot]]

Hi @faruzanCN! I'm Dosu and I’m helping the dify team.

To run Dify under a path prefix like /dify (for example, behind an Nginx reverse proxy on a shared port), you need to manually configure both the frontend and your proxy. Just changing the .env URLs is not enough and will cause 404 errors because the frontend and backend do not automatically handle subpaths.

Here’s what you need to do:

1. Frontend base path:
   Edit web/utils/var-basePath.js and web/utils/var.ts to set your desired base path (e.g., /dify).
   Update NEXT_PUBLIC_API_PREFIX and NEXT_PUBLIC_PUBLIC_API_PREFIX in web/.env to include the prefix.
   Then rebuild the frontend Docker image so it uses the new base path.
   Details & discussion | Step-by-step example

2. Nginx reverse proxy:
   Configure Nginx to strip the prefix before forwarding requests to the backend.
   Example config:

   location /dify/ {
       proxy_pass http://127.0.0.1:3000/;
       proxy_set_header Host $host;
       proxy_set_header X-Real-IP $remote_addr;
       proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
       proxy_set_header X-Forwarded-Proto $scheme;
       proxy_set_header X-Forwarded-Prefix /dify;
       rewrite ^/dify/(.*)$ /$1 break;
   }

   Reference config

3. Backend .env:
   Set RESPECT_XFORWARD_HEADERS_ENABLED=true in your backend .env file for proper URL generation.

4. Restart containers:
   After making these changes, restart all containers to apply the new settings.

Important:
There is no built-in support for subpath deployment in Dify. You must manually set the base path in the frontend source and rebuild the image for each subpath you want to use. Simply changing environment variables or Nginx configs without rebuilding the frontend will not work and will result in 404 errors.
Why this is necessary

If you follow these steps, all frontend requests will use the path prefix, and your deployment should work behind a shared port with Nginx path-based routing.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}