Regarding the issue of adjusting the default request address: http://ip:port/dify/

[Monkeywj]

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.

Content

How to adjust the request address of the dify community version, for example:
Change
difyip:port/
to
difyip:port/dify/,
automatically appending /dify/ at the end.

The main reason is that service A needs to be integrated with Chatflow released by dify.
However, users cannot access dify.
Therefore, I want to use the nginx proxy of service A to access dify, in order to solve the problem of the embedded service being inaccessible. Aip:port/dify

Previous attempts:
Attempting to adjust the URL of the web container as described on GitHub did not solve the problem.

[dosubot[bot]]

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

To run Dify at a subpath like /dify/ (so users access it via http://ip:port/dify/), you need to do more than just change the web container URL. The frontend (Next.js) must be built with the correct base path, and both environment variables and nginx must be configured to match.

Here’s what works:

1. Build the frontend with the base path:
   In the web directory, build the frontend Docker image with the base path set:

   docker build . -t dify-base-path:latest --build-arg NEXT_PUBLIC_BASE_PATH=/dify

   Use this custom image in your deployment instead of the default one.

2. Update environment variables:
   In your .env file, update all relevant URLs to include the /dify prefix, for example:

   CONSOLE_WEB_URL=http://your-domain.com/dify
   APP_WEB_URL=http://your-domain.com/dify
   CONSOLE_API_URL=http://your-domain.com/dify/api
   SERVICE_API_URL=http://your-domain.com/dify/service
   APP_API_URL=http://your-domain.com/dify/app
   

   For file uploads/downloads, set FILES_URL to your public domain (e.g., https://your-domain.com) to avoid static file path errors.

3. Configure nginx:
   Proxy the /dify/ path to the Dify frontend, set the X-Forwarded-Prefix header, and rewrite the path:

   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;
   }

   For static files (like /files), add a separate proxy location pointing to the API service.

4. Important notes:

   • Just changing environment variables is not enough; the frontend must be rebuilt with the correct base path.
   • If nginx is handling SSL or acting as a reverse proxy, set RESPECT_XFORWARD_HEADERS_ENABLED=true in your environment.

This approach is confirmed by both the codebase and community solutions for subpath deployment. For more details and examples, see this issue and this one.

To reply, just mention @dosu.

---

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

   

[Monkeywj]

I've tried it, but it didn't work.
this cmd " docker build . -t dify-base-path:latest --build-arg NEXT_PUBLIC_BASE_PATH=/dify "

code need ip:port:/dify ？

[dosubot[bot]]

The codebase supports running Dify under a subpath like /dify if you build the frontend with NEXT_PUBLIC_BASE_PATH=/dify—this sets the Next.js basePath correctly and routes the app under that subpath (source). However, there are a few important details:

• You must update all relevant environment variables (like NEXT_PUBLIC_API_PREFIX, NEXT_PUBLIC_PUBLIC_API_PREFIX, CONSOLE_WEB_URL, etc.) to include the /dify prefix, so API calls and links work under the subpath (source).
• Some assets and manifest entries (like icons, start_url, etc.) are hardcoded to / in manifest.json, so they may not work perfectly under /dify without manual adjustment or extra nginx rewrites.
• There was a recent fix to prevent double slashes in redirect URLs when using a base path (source), so make sure you’re using a recent version.
• Your nginx config must rewrite and proxy /dify/ requests to the frontend, and you may need a separate rule for static files.

If you’ve done all this and it still doesn’t work, check for 404s or incorrect API calls in your browser’s network tab—these usually indicate a missing or misconfigured environment variable or nginx rule. If you can share your nginx config or error details, I can help debug further.

To reply, just mention @dosu.

---

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