Closed rnr18 closed 8 years ago
Hi,
Your issue has nothing to do with the notice xo:perf blocked
. The error is here:
[Warn] Web server could not listen on http://localhost:80
[Warn] Access denied.
[Warn] Ports < 1024 are often reserved to privileges users.
You configured xo-server
to start with a non-privileged user on a port <1024, which is forbidden.
Solutions:
with root privileges I get the same output
root@xenorchestra:/home/xenorchestra/xo-server# npm start
xo-server@4.7.0 start /home/xenorchestra/xo-server node bin/xo-server
app-conf /home/xenorchestra/xo-server/.xo-server.yaml +0ms xo:main Configuration loaded. +17ms xo:main Web server listening on http://[::]:80 +17ms xo:perf blocked for 35ms +64ms xo:perf blocked for 162ms +263ms
How do I change the port for server to listen?
No, you don't get the same output: this time, the service is started (Web server listening
). Now it's listening to the port 80 and it works.
Now, you have another problem: is your config file have the correct path to the dist
folder of xo-web
? Is there a dist
folder in xo-web
?
edit: you can change the port in the config file. But everything is described in the documentation, take time to read it: https://github.com/vatesfr/xo/blob/master/doc/installation/manual_installation.md
Thanks Olivier. I was editing the sample config file instead of the hidden .xo-server.yaml file. XOA works perfectly fine. Thanks once again
You are welcome :) Enjoy XO!
Hello, please help me out with this issue: After installing xo-server, I get this output
:~/xo-server$ node bin/xo-server
app-conf /home/xenorchestra/xo-server/.xo-server.yaml +0ms
xo:main Configuration loaded. +16ms
[Warn] Web server could not listen on http://localhost:80
[Warn] Access denied.
[Warn] Ports < 1024 are often reserved to privileges users.
xo:perf blocked for 30ms +76ms
xo:perf blocked for 188ms +288ms
xo:perf blocked for 12ms +20m
I used sudo before npm start so its permitted to listen on port 80. I'm not a linux expert.
on my browser, after login it displays "cannot GET \"