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
2022/06/22 13:08:05 --------------------Config-------------------- 2022/06/22 13:08:05 port= 5210 2022/06/22 13:08:05 tlsPort= 5211 2022/06/22 13:08:05 source= kuwo 2022/06/22 13:08:05 certFile= /usr/share/UnblockNeteaseMusic/server.crt 2022/06/22 13:08:05 keyFile= /usr/share/UnblockNeteaseMusic/server.key 2022/06/22 13:08:05 logFile= /tmp/unblockneteasemusic.log 2022/06/22 13:08:05 mode= 0 2022/06/22 13:08:05 endPoint= false 2022/06/22 13:08:05 forceBestQuality= false 2022/06/22 13:08:05 searchLimit= 0 2022/06/22 13:08:05 -------------------Init Host------------------- 2022/06/22 13:08:05 Recover panic : music.163.com ip:127.0.0.1 is error ping6 bad address,please check IPv6 DNS forwards.if IPv6 DNS forwards is enabled, please restart
直接命令行启动没有问题
The text was updated successfully, but these errors were encountered:
No branches or pull requests
2022/06/22 13:08:05 --------------------Config--------------------
2022/06/22 13:08:05 port= 5210
2022/06/22 13:08:05 tlsPort= 5211
2022/06/22 13:08:05 source= kuwo
2022/06/22 13:08:05 certFile= /usr/share/UnblockNeteaseMusic/server.crt
2022/06/22 13:08:05 keyFile= /usr/share/UnblockNeteaseMusic/server.key
2022/06/22 13:08:05 logFile= /tmp/unblockneteasemusic.log
2022/06/22 13:08:05 mode= 0
2022/06/22 13:08:05 endPoint= false
2022/06/22 13:08:05 forceBestQuality= false
2022/06/22 13:08:05 searchLimit= 0
2022/06/22 13:08:05 -------------------Init Host-------------------
2022/06/22 13:08:05 Recover panic : music.163.com ip:127.0.0.1 is error
ping6 bad address,please check IPv6 DNS forwards.if IPv6 DNS forwards is enabled, please restart
直接命令行启动没有问题
The text was updated successfully, but these errors were encountered: