We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
root@vultr:# systemctl daemon-reload root@vultr:# systemctl restart v2ray root@vultr:# systemctl restart tls-shunt-proxy root@vultr:# sudo setcap "cap_net_bind_service=+ep" /usr/local/bin/tls-shunt-proxy root@vultr:# sudo -u tls-shunt-proxy /usr/local/bin/tls-shunt-proxy -config /etc/tls-shunt-proxy/config.yaml tls-shunt-proxy version 0.7.0 2022/03/13 21:58:21 failed to listen on 0.0.0.0:443: listen tcp 0.0.0.0:443: bind: address already in use root@vultr:#
The text was updated successfully, but these errors were encountered:
我排查了很多地方始终找不到原因
Sorry, something went wrong.
No branches or pull requests
root@vultr:
# systemctl daemon-reload# systemctl restart v2rayroot@vultr:
root@vultr:
# systemctl restart tls-shunt-proxy# sudo setcap "cap_net_bind_service=+ep" /usr/local/bin/tls-shunt-proxyroot@vultr:
root@vultr:
# sudo -u tls-shunt-proxy /usr/local/bin/tls-shunt-proxy -config /etc/tls-shunt-proxy/config.yaml#tls-shunt-proxy version 0.7.0
2022/03/13 21:58:21 failed to listen on 0.0.0.0:443: listen tcp 0.0.0.0:443: bind: address already in use
root@vultr:
The text was updated successfully, but these errors were encountered: