forked from clowwindy/shadowsocks-libev
-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
无法启动服务 #1183
Comments
@rule2c I wonder maybe it's same issue as resolved in #1166 (comment) |
在4d6a230之前是好的,更新到f64177a,就无法启动了。 |
setcap cap_net_bind_service+ep /usr/bin/ss-server之后解决了。谢谢 @rogers0 |
是我把端口号改成443 引起的。谢谢 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please answer these questions before submitting your issue. Thanks!
What version of shadowsocks-libev are you using?
3.0
What operating system are you using?
Debian 8
What did you do?
启动服务
What did you expect to see?
成功启动
What did you see instead?
Feb 3 21:18:14 BossySalty-VM ss-server[469]: 2017-02-03 21:18:14 ERROR: bind: Permission denied
Feb 3 21:18:14 BossySalty-VM ss-server[469]: 2017-02-03 21:18:14 ERROR: Could not bind
Feb 3 21:18:14 BossySalty-VM ss-server[469]: 2017-02-03 21:18:14 ERROR: bind() error
Feb 3 21:18:14 BossySalty-VM systemd[1]: shadowsocks-libev.service: main process exited, code=exited, status=255/n/a
Feb 3 21:18:14 BossySalty-VM systemd[1]: Unit shadowsocks-libev.service entered failed state.
What is your config in detail (with all sensitive info masked)?
{
"server":"0.0.0.0",
"server_port":443,
"local_port":1080,
"password":"XXXXXXXX",
"timeout":600,
"method":"chacha20"
}
The text was updated successfully, but these errors were encountered: