本地部署报告两个问题 #135

Closed
opened 2026-02-21 17:26:06 -05:00 by yindo · 6 comments
Owner

Originally created by @aimdreamboy on GitHub (Jun 4, 2023).

1、本地部署版本,这个api的URL是什么?比如我测试的ip地址是192.168.1.23。访问前端是192.168.1.23,api是192.168.1.23:5001。但是当我调用api服务地址192.168.1.23:5001的时候,会提示授权问题。也就是类似调用了原来的https://udify.app/api/chat-messages。而不是api。应该如何配置呢?是否有指导文档可以看?目前部署过程比较混乱
image

2、当私有化部署之后,在提交嵌入文本的时候,进度一直是0%,看日志也不报错。请问该如何排查问题呢?

Originally created by @aimdreamboy on GitHub (Jun 4, 2023). 1、本地部署版本,这个api的URL是什么?比如我测试的ip地址是192.168.1.23。访问前端是192.168.1.23,api是192.168.1.23:5001。但是当我调用api服务地址192.168.1.23:5001的时候,会提示授权问题。也就是类似调用了原来的https://udify.app/api/chat-messages。而不是api。应该如何配置呢?是否有指导文档可以看?目前部署过程比较混乱 ![image](https://github.com/langgenius/dify/assets/40591097/70c7592c-859b-4d3c-b35f-db0b4bfb4627) 2、当私有化部署之后,在提交嵌入文本的时候,进度一直是0%,看日志也不报错。请问该如何排查问题呢?
yindo added the 📚 documentation label 2026-02-21 17:26:06 -05:00
yindo closed this issue 2026-02-21 17:26:07 -05:00
Author
Owner

@xhdou commented on GitHub (Jun 4, 2023):

同问api的url是啥,一开始以为是openai的key

@xhdou commented on GitHub (Jun 4, 2023): 同问api的url是啥,一开始以为是openai的key
Author
Owner

@takatost commented on GitHub (Jun 4, 2023):

Can you explain how you deployed it? Was it with docker-compose, from source, or something else?

@takatost commented on GitHub (Jun 4, 2023): Can you explain how you deployed it? Was it with docker-compose, from source, or something else?
Author
Owner

@xhdou commented on GitHub (Jun 4, 2023):

I use docker-compose.yml

@xhdou commented on GitHub (Jun 4, 2023): I use docker-compose.yml
Author
Owner

@takatost commented on GitHub (Jun 4, 2023):

  1. maybe this can help you:
server {
    listen 80;
    server_name _;

    # console api
    location /console/api {
      proxy_pass http://api:5001;
      include proxy.conf;
    }

    # web app api
    location /api {
      proxy_pass http://api:5001;
      include proxy.conf;
    }
    
    # service api
    location /v1 {
      proxy_pass http://api:5001;
      include proxy.conf;
    }

    # frontend
    location / {
      proxy_pass http://web:3000;
      include proxy.conf;
    }
}
  1. you could check if the worker service is up and running and if there are any errors:
docker logs -n 200 docker-worker-1
@takatost commented on GitHub (Jun 4, 2023): 1. maybe this can help you: ``` server { listen 80; server_name _; # console api location /console/api { proxy_pass http://api:5001; include proxy.conf; } # web app api location /api { proxy_pass http://api:5001; include proxy.conf; } # service api location /v1 { proxy_pass http://api:5001; include proxy.conf; } # frontend location / { proxy_pass http://web:3000; include proxy.conf; } } ``` 2. you could check if the `worker` service is up and running and if there are any errors: ``` docker logs -n 200 docker-worker-1 ```
Author
Owner

@Jackerry-H commented on GitHub (Jun 14, 2023):

问题第一点解决了吗?

@Jackerry-H commented on GitHub (Jun 14, 2023): 问题第一点解决了吗?
Author
Owner

@crazywoola commented on GitHub (Jun 19, 2023):

See https://github.com/langgenius/dify/blob/main/api/.env.example this file for details

@crazywoola commented on GitHub (Jun 19, 2023): See https://github.com/langgenius/dify/blob/main/api/.env.example this file for details
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#135