How can I set up dify server behind a nginx reverse proxy?

[wxup]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Provide a description of requested docs changes

I need to deploy dify behind a nginx, and under the prefix /apps/dify/. I searched through the documentation, it seems there are not enough information in the documentation to help me achieve this. Anyone can help?

[dosubot[bot]]

Hi @wxup! I'm here to help you with any bugs, questions, or contributions. I'll do my best to assist you while we wait for a human maintainer.

To set up the Dify server behind an Nginx reverse proxy and under the prefix /apps/dify/, you can use the following Nginx configuration:

server {
    listen 80;
    server_name your_domain.com;

    location /apps/dify/ {
        proxy_pass http://localhost:your_dify_port/;
        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 /apps/dify;
        rewrite ^/apps/dify/(.*)$ /$1 break;
    }
}

Replace your_domain.com with your actual domain and your_dify_port with the port on which your Dify server is running. This configuration will forward requests from http://your_domain.com/apps/dify/ to your Dify server.

Additionally, ensure that the following environment variables in your docker-compose.yml are set to match the new domain and URL:

CONSOLE_API_URL: http://your_domain.com/apps/dify/api
CONSOLE_WEB_URL: http://your_domain.com/apps/dify
SERVICE_API_URL: http://your_domain.com/apps/dify/service
APP_API_URL: http://your_domain.com/apps/dify/app
APP_WEB_URL: http://your_domain.com/apps/dify

This will help avoid CORS issues and ensure that the front-end and back-end communicate correctly ^[1][2].

To continue talking to Dosu, mention @dosu.

[wxup]

I tested your conifg but it doesn't work.
I think you add rewrite rule to remove the prefix /apps/dify/, but you use it in the environment variables, That's contradictory.
Can you fix your solution? @dosu

[chun8933]

Same request here, please help follow up.

I am new to dev🙏🏻, After a lot of try and errors, i successfully add prefix /xxx/dify to the url.. however, even i did that process, my niginx still cant work well with dify container.

Here are some findings:

1. To make the proxy work, rewrite and also reform of url are required.
   Make sure you are passing the path without prefix to dify, And make sure to add prefix back when responsing to client.
2. I have read a lot on the web about the env variables, but still no hope. No matter what i put to those urls, it didnt change anythings.
3. The frontend will redirect to /apps. As mentioned, i handled to response url to client, but i am stopped here, dont know why there are 404 on those static res from the nextjs app...

[chun8933]

And yes, it works with asset paths.
However, there are lot of predefined paths like /app, /dataset, /tools, /explore and logo might need modification...

[chun8933]

It also works well with nginx location / configured to redirect all traffics to /prefix/$1, but it will affect the other existing rules. Mean if the nginx only serve a single site than fine.

Will try to modify all predefine paths by inserting the prefix in front.

Is there any better way??

[kevinl1210]

Hi, i recently encounter similar requirements, i am using the docker deployment and i want to access the dify webpage at http://xxx/dify, and all its api endpoint should also change to e.g. http://xxx/dify/api accordingly, may I know how did you update the config files to make it work? What files did you change.

Appreciate it if you would share with us please.

[chun8933]

hows your webserver config? if your web server only serve dify, than is easy. however, if there is more than 1 service managing by the web server, you may config nginx location block and re-build the frontend of dify, as mentioned, you may add basePath and assetPrefix to the nextjs config file and the env var with your needs.

[qogris]

Hi, i recently encounter similar requirements, i am using the docker deployment and i want to access the dify webpage at http://xxx/dify, and all its api endpoint should also change to e.g. http://xxx/dify/api accordingly, may I know how did you update the config files to make it work? What files did you change.

Appreciate it if you would share with us please.

no updates for a long time ...

[sweetkey]

Hi, the setting in the nginx works for us which point the xyz.com/dify to dify service, while xyz.com points to other site.

Server {
               Proxy configurations…
                root /www/home;  #your file for the root domain
 
                location / {
                        try_files $uri $uri/ index.html @proxy;
                }
 
                location = /dify {
                        return 301 https://$host/apps/;
                }
 
                location @proxy {
                        proxy_pass http://127.0.0.1: port/; # port should match the port setting in the .env of the dify
                }

[QWQyyy]

我也遇到了这个问题，我的服务器只有80端口可用，于是我想把Dify用nginx映射到80端口上的/dify路径下，实现路径复用，但是似乎上面讨论的配置不起作用