infiniflow
[Question]: How to login RAGFlow from another system.
Self Checks
- [x] I have searched for existing issues search for existing issues, including closed ones.
- [x] I confirm that I am using English to submit this report (Language Policy).
- [x] Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
- [x] Please do not modify this template :) and fill in all the required fields.
Describe your problem
RAGFlow services started successfully and login it from the local system successfully, but how to login it from another system?
local system logs:
test@test-test-Product:~/ragflow/docker$ docker logs -f ragflow-server
Starting nginx...
Starting ragflow_server...
Starting 1 task executor(s) on host '0b7116e22504'...
2025-05-21 09:43:56,073 INFO 15 ragflow_server log path: /ragflow/logs/ragflow_server.log, log levels: {'peewee': 'WARNING', 'pdfminer': 'WARNING', 'root': 'INFO'}
2025-05-21 09:43:56,650 INFO 15 can't import package 'torch'
2025-05-21 09:44:00,297 INFO 15 init database on cluster mode successfully
2025-05-21 09:44:02,848 INFO 15 load_model /ragflow/rag/res/deepdoc/det.onnx uses CPU
2025-05-21 09:44:02,920 INFO 15 load_model /ragflow/rag/res/deepdoc/rec.onnx uses CPU
2025-05-21 09:44:07,934 INFO 15
____ ___ ______ ______ __
/ __ \ / | / ____// ____// /____ _ __
/ /_/ // /| | / / __ / /_ / // __ \| | /| / /
/ _, _// ___ |/ /_/ // __/ / // /_/ /| |/ |/ /
/_/ |_|/_/ |_|\____//_/ /_/ \____/ |__/|__/
2025-05-21 09:44:07,934 INFO 15 RAGFlow version: v0.18.0 slim
2025-05-21 09:44:07,935 INFO 15 project base: /ragflow
2025-05-21 09:44:07,935 INFO 15 Current configs, from /ragflow/conf/service_conf.yaml:
ragflow: {'host': '0.0.0.0', 'http_port': 9380}
mysql: {'name': 'rag_flow', 'user': 'root', 'password': '********', 'host': 'mysql', 'port': 3306, 'max_connections': 100, 'stale_timeout': 30}
minio: {'user': 'rag_flow', 'password': '********', 'host': 'minio:9000'}
es: {'hosts': 'http://es01:9200', 'username': 'elastic', 'password': '********'}
infinity: {'uri': 'infinity:23817', 'db_name': 'default_db'}
redis: {'db': 1, 'password': '********', 'host': 'redis:6379'}
2025-05-21 09:44:07,935 INFO 15 Use Elasticsearch http://es01:9200 as the doc engine.
2025-05-21 09:44:08,018 INFO 15 GET http://es01:9200/ [status:200 duration:0.082s]
2025-05-21 09:44:08,022 INFO 15 HEAD http://es01:9200/ [status:200 duration:0.003s]
2025-05-21 09:44:08,022 INFO 15 Elasticsearch http://es01:9200 is healthy.
2025-05-21 09:44:08,027 WARNING 15 Load term.freq FAIL!
2025-05-21 09:44:08,029 WARNING 15 Realtime synonym is disabled, since no redis connection.
2025-05-21 09:44:08,031 WARNING 15 Load term.freq FAIL!
2025-05-21 09:44:08,034 WARNING 15 Realtime synonym is disabled, since no redis connection.
2025-05-21 09:44:08,034 INFO 15 MAX_CONTENT_LENGTH: 134217728
2025-05-21 09:44:08,034 INFO 15 MAX_FILE_COUNT_PER_USER: 0
2025-05-21 09:44:08,879 INFO 15 init web data success:0.7857134342193604
2025-05-21 09:44:08,881 INFO 15 update_progress lock_value: e1d8814c-d9ed-4864-ab87-511f1e31ffdc
2025-05-21 09:44:08,881 INFO 15 RAGFlow HTTP server start...
2025-05-21 09:44:08,882 INFO 15 WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
* Running on all addresses (0.0.0.0)
* Running on http://127.0.0.1:9380
* Running on http://172.18.0.6:9380
2025-05-21 09:44:08,882 INFO 15 Press CTRL+C to quit
2025-05-21 09:44:15,184 INFO 31 task_executor_0b7116e22504_0 log path: /ragflow/logs/task_executor_0b7116e22504_0.log, log levels: {'peewee': 'WARNING', 'pdfminer': 'WARNING', 'root': 'INFO'}
2025-05-21 09:44:15,184 INFO 31
______ __ ______ __
/_ __/___ ______/ /__ / ____/ _____ _______ __/ /_____ _____
/ / / __ `/ ___/ //_/ / __/ | |/_/ _ \/ ___/ / / / __/ __ \/ ___/
/ / / /_/ (__ ) ,< / /____> </ __/ /__/ /_/ / /_/ /_/ / /
/_/ \__,_/____/_/|_| /_____/_/|_|\___/\___/\__,_/\__/\____/_/
2025-05-21 09:44:15,185 INFO 31 TaskExecutor: RAGFlow version: v0.18.0 slim
2025-05-21 09:44:15,185 INFO 31 Use Elasticsearch http://es01:9200 as the doc engine.
2025-05-21 09:44:15,196 INFO 31 GET http://es01:9200/ [status:200 duration:0.010s]
2025-05-21 09:44:15,199 INFO 31 HEAD http://es01:9200/ [status:200 duration:0.002s]
2025-05-21 09:44:15,199 INFO 31 Elasticsearch http://es01:9200 is healthy.
2025-05-21 09:44:15,203 WARNING 31 Load term.freq FAIL!
2025-05-21 09:44:15,206 WARNING 31 Realtime synonym is disabled, since no redis connection.
2025-05-21 09:44:15,210 WARNING 31 Load term.freq FAIL!
2025-05-21 09:44:15,213 WARNING 31 Realtime synonym is disabled, since no redis connection.
2025-05-21 09:44:15,213 INFO 31 MAX_CONTENT_LENGTH: 134217728
2025-05-21 09:44:15,213 INFO 31 MAX_FILE_COUNT_PER_USER: 0
2025-05-21 09:44:15,219 INFO 31 task_executor_0b7116e22504_0 reported heartbeat: {"name": "task_executor_0b7116e22504_0", "now": "2025-05-21T09:44:15.218+08:00", "boot_at": "2025-05-21T09:44:15.183+08:00", "pending": 0, "lag": 0, "done": 0, "failed": 0, "current": {}}
2025-05-21 09:44:15,220 INFO 31 task_executor_5895627f6965_0 expired, removed
local system ifconfig output:
test@test-test-Product:~/ragflow/docker$ ifconfig
br-58af26eb4c8f: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
inet6 fe80::42:29ff:fe9c:4651 prefixlen 64 scopeid 0x20<link>
ether 02:42:29:9c:46:51 txqueuelen 0 (Ethernet)
RX packets 43 bytes 3249 (3.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 138 bytes 25774 (25.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:e4:36:e0:39 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eno2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether f4:6b:8c:8d:f0:51 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 546053380 bytes 41043432504 (41.0 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 546053380 bytes 41043432504 (41.0 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth1a134ec: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::30ce:cff:fe19:2e4b prefixlen 64 scopeid 0x20<link>
ether 32:ce:0c:19:2e:4b txqueuelen 0 (Ethernet)
RX packets 10091 bytes 3035846 (3.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 15182 bytes 1593994 (1.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth6680e22: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::5804:29ff:fe83:8ab4 prefixlen 64 scopeid 0x20<link>
ether 5a:04:29:83:8a:b4 txqueuelen 0 (Ethernet)
RX packets 13572 bytes 1415547 (1.4 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8440 bytes 1356041 (1.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth746de6e: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::8ca4:83ff:fe57:9851 prefixlen 64 scopeid 0x20<link>
ether 8e:a4:83:57:98:51 txqueuelen 0 (Ethernet)
RX packets 1571 bytes 172790 (172.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1702 bytes 1684767 (1.6 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth96306fb: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::a445:31ff:fe87:8512 prefixlen 64 scopeid 0x20<link>
ether a6:45:31:87:85:12 txqueuelen 0 (Ethernet)
RX packets 38 bytes 3641 (3.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 64 bytes 16521 (16.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vethe55ea48: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::1c7d:2fff:fee1:7208 prefixlen 64 scopeid 0x20<link>
ether 1e:7d:2f:e1:72:08 txqueuelen 0 (Ethernet)
RX packets 11 bytes 2326 (2.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 46 bytes 5809 (5.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wls1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.103.162.176 netmask 255.255.254.0 broadcast 10.103.163.255
inet6 fe80::aac2:2af3:fd06:6095 prefixlen 64 scopeid 0x20<link>
ether 54:14:f3:c2:3a:3a txqueuelen 1000 (Ethernet)
RX packets 50554633 bytes 7803146918 (7.8 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 50546209 bytes 4907462432 (4.9 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
test@test-test-Product:~/ragflow/docker$
To log in to RAGFlow from another system, follow these steps:
-
Ensure Server Initialization: First, make sure that the RAGFlow server is fully initialized. You can verify this by checking the server logs with the command
docker logs -f ragflow-server. Look for the message indicating that the server is running on all addresses (0.0.0.0). -
Access RAGFlow: Once the server is confirmed to be running, you can access RAGFlow from another system by entering the IP address of your server in a web browser. Use the URL
http://IP_OF_YOUR_MACHINEwithout specifying a port number, as the default HTTP serving port is 80 [1][2]. -
Firewall and Network Configuration: Ensure that there are no firewall rules blocking access to the server's IP address and port 80. Verify network connectivity between the remote system and the server [3].
By following these steps, you should be able to log in to RAGFlow from another system successfully.
To continue talking to Dosu, mention @dosu.
Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other
![dosubot[bot] avatar](https://avatars.githubusercontent.com/in/324583?v=4 "Published by a pub.dev verified publisher"){kind=small}
@dosu
From the logs I pasted as above, please tell me which IP I can use to login RAGFlow from a remote system with the network connection available to RAGFlow server.
You can use the IP address 172.18.0.6 to log in to RAGFlow from another system. Since RAGFlow is configured to listen on 0.0.0.0 and the HTTP port is set to 9380, you should be able to access it using the URL http://172.18.0.6:9380 [1][2].
To continue talking to Dosu, mention @dosu.
Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other
@dosu
Fail to access the RAGFlow using the URL http://172.18.0.6:9380 in the Firefox from the remote system and also fail to "ping 172.18.0.6" from the remote system.
I can get reply if I ping 10.103.162.176 from the remote system but fail to ccess the RAGFlow using the URL http://10.103.162.176:9380. 10.103.162.176 is the wifi IP of the RAGFlow server in the logs I pasted as above.
So, for my current RAGFlow server, is 172.18.0.6:9380 the only choice for remote access? if yes, how can I debug for 172.18.0.6:9380 to see whether the issue is on my RAGFlow server or on the network limitation between the RAGFlow server and the remote system?
The IP address 172.18.0.6 is likely a Docker internal IP, which is not accessible from external networks. Instead, you should use the server's external IP, 10.103.162.176, for remote access. Since you can ping 10.103.162.176 but cannot access RAGFlow, the issue might be related to port accessibility or firewall settings.
Here are steps to debug the issue:
-
Check Port Accessibility: Ensure that port
9380is open and accessible on the server. You can use tools likenmaportelnetto check if the port is open from the remote system. -
Firewall Settings: Verify that there are no firewall rules blocking access to port
9380. You may need to adjust firewall settings to allow traffic on this port. -
Docker Configuration: Confirm that the Docker container is correctly configured to expose port
9380. Check thedocker-compose.ymlor Docker run command to ensure port mapping is set up correctly. -
Network Configuration: Ensure that the network configuration allows traffic between the remote system and the server. This includes checking any network security groups or routing rules.
By following these steps, you should be able to identify whether the issue is with the server configuration or network limitations [1].
To continue talking to Dosu, mention @dosu.
Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other
@Bob123Yang It appears your server hasn't been assigned any IP address. You'll need to contact your IT administrator to obtain a network address assignment.
As shown in the screenshot below, any device on my local network can access my RAGFlow service via http://192.168.200.234/
Thanks @asiroliu
My RAGFlow server got the IP assigned to the WIFI card as 10.103.162.176 showed in the below picture that is the output of the command "ifconfig" running on the RAGFlow server:
But fail to access http://10.103.162.176 (ping 10.103.162.176 successfully) from the web browser of the remote system which is in the same local network with the RAGFlow.