Port problem, in the log: listening 172.0.0.1:23333 means that the listening port is 23333. You need to access port 23333 to display it. Accessing port 5000 will definitely have no content.
Maybe I read it wrong upstairs, 127.0.0.1:23333 is the port for scheduler communication; port 5000 is where webui displays the front-end control page. The log on my machine:
[I 170328 08:51:16 scheduler:683] scheduler.xmlrpc listening on 127.0.0.1:23333
[I 170328 08:51:16 scheduler:68] project test updated, status:RUNNING, paused:False, 0 tasks
[I 170328 08:51:16 app:76] webui running on 0.0.0.0:5000
Looking at the question log, it should be a taskdb and projectdb configuration issue. It is recommended to remove the Chinese characters in the path and try again
Also: Why don’t you use the admin account when running on C drive? This time it’s typical: Microsoft teaches you how to be a good person
I have also encountered this problem, because the 5000 port is not open, iptables -I INPUT -p tcp --dport 5000 -j ACCEPT service iptables save service iptables restart That’s it
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
localhost:23333, see the output
The log shows the listening port 23333. Why did you access port 5000?
Port problem, in the log: listening 172.0.0.1:23333 means that the listening port is 23333. You need to access port 23333 to display it. Accessing port 5000 will definitely have no content.
Maybe I read it wrong upstairs, 127.0.0.1:23333 is the port for scheduler communication; port 5000 is where webui displays the front-end control page.
The log on my machine:
Looking at the question log, it should be a taskdb and projectdb configuration issue. It is recommended to remove the Chinese characters in the path and try again
Also: Why don’t you use the admin account when running on C drive? This time it’s typical: Microsoft teaches you how to be a good person
I have also encountered this problem, because the 5000 port is not open,
iptables -I INPUT -p tcp --dport 5000 -j ACCEPT
service iptables save
service iptables restart
That’s it
Has the poster’s problem been solved? I encountered it too