[Question]: Ragflow is deployed on a remote server, but the access from the local machine fails.

[liyubo-debug]

Describe your problem

Ragflow is deployed on the server, but when I try to access it remotely from my local machine, the URLs http://server IP:10080 or 19380 cannot be opened. I have made the following modifications, and the service is started normally. This problem has been bothering me all day. I would appreciate it if you could give me some guidance.

If the product interface can't be opened, is it possible to call the locally deployed large model via vLLM? I'm currently stuck at the point where I can't open the product interface and am unable to move on to the next step. Therefore, I'd like to inquire about how to call the locally deployed large model to provide services without using the product interface.

[KevinHuSh]

Do not alter service_conf.yaml.template which is all about configuration within the docker network envirement.
10080 should work if the IP is right and accessible, and RAGFlow is healthy.

[liyubo-debug]

Do not alter service_conf.yaml.template which is all about configuration within the docker network envirement. 10080 should work if the IP is right and accessible, and RAGFlow is healthy.

Thank you for your tip. I haven't modified the service_conf.yaml.template file for now. The IP address of the remote server is correct because I can access other services on the server from my local machine. When I execute "curl http://localhost:10080/" on the server, it can return the information of the front-end interface. However, I still can't open the product interface from my local machine.

[liyubo-debug]

The corrected configuration is correct. It turned out to be a network issue, and the interface can be accessed now.