UnblockNeteaseMusic / UnblockNeteaseMusic/server
建议更新README,网易云 3.x on windows 方法1完全失效
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.8k
- Forks
- 762
- PR merge metrics
- No merged PRs in 30d
Description
Bug 描述
在 Windows 上使用 enhanced 分支运行
node app.js -a 127.0.0.1 -p 80:81 -f 103.126.92.133 -s
并且通过方法1(修改Host)指定特定域名使用解灰服务时,由于客户端只支持HTTP代理
- 3.x 客户端无法联网或无法解密 HTTPS 流量。
- 2.x 客户端正常工作。
当通过方法2,即 IE/系统代理,设置服务器提供 PAC 时,2.x 与 3.x 客户端均工作正常。
注意:
- 从方法1修改为方法2时需要删除 Host 修改,或修改 PAC 为
return 'PROXY 127.0.0.1:81' - 并且,安装证书
预期行为
No response
实际行为
No response
复现步骤
No response
启动命令及环境变量
scriptOptions: '-s -p 80:81 -a 127.0.0.1 -f 103.126.92.133',
env: [
{
name: 'ENABLE_FLAC',
value: 'true',
},
{
name: 'LOG_LEVEL',
value: 'debug',
},
{
name: 'LOG_FILE',
value: 'app.log'
},
{
name: 'HTTP_PROXY_PORT',
value: '80',
},
{
name: 'HTTPS_PROXY_PORT',
value: '81',
},
// {
// name: 'QQ_COOKIE',
],
日志内容
INFO: (app) HTTP Server running @ http://127.0.0.1:80
INFO: (app) HTTPS Server running @ http://127.0.0.1:81
网易云音乐歌曲链接
No response
网易云音乐版本号
3.18 / 2.10
操作系统
Windows 23H2
其他信息
No response
问题排查
- 我确认我使用的核心是由 UnblockNeteaseMusic 项目官方发行,不是其他任何 fork。
- 我确认我已经升级到了最新的核心版本(推荐使用最新构建而不是 release)。
- 我确认我已经启用了 HTTPS 端口。
- 我确认我已经正确设置了 EndPoint。
- 我确认我已经在对应的客户端正确安装了 CA 证书。
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the README instructions for Windows and compare the documented method 1 and method 2 flows against the reported behavior of Netease Cloud Music 3.x. Update the guidance to explain the system or IE proxy/PAC approach, removing Host modifications when switching methods and noting the required CA certificate. Done means the README accurately describes a working setup for both client versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100