UnblockNeteaseMusic / UnblockNeteaseMusic/server

MacOS客户端无法使用,win客户端和网页能够正常使用

Open
#1,588 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
7.8k
Forks
762
PR merge metrics
No merged PRs in 30d

Description

Bug 描述

启动命令:node app.js -s -p 16163:17173 -o kuwo qq migu -e https://music.163.com
已正常信任证书
MacOS网页访问是正常的,有代理到
INFO: (app) HTTP Server running @ http://0.0.0.0:16163
INFO: (app) HTTPS Server running @ http://0.0.0.0:17173
INFO: (provider/match) Replaced: [1962165898] 最伟大的作品
audioId: 1962165898
songName: "最伟大的作品"
url: "http://lv.sycdn.kuwo.cn/35170274b807cb34dd6bbae691cc44f4/681b12d0/resource/30106/trackmedia/M500001yeNa60aLoOu.mp3?bitrate"

通过MacOS客户端访问,没有任何日志输出。2.3.21版本和3.0.13都不能正常使用。请问MacOS客户端使用哪个版本的能够正常使用

Image

预期行为

MacOS客户端能够正常使用

实际行为

No response

复现步骤

No response

启动命令及环境变量

aliyun centOS 7 Node.js v16.20.2.

node app.js -s -p 16163:17173 -o kuwo qq migu -e https://music.163.com

日志内容

MacOS网页访问是正常的,有代理到
INFO: (app) HTTP Server running @ http://0.0.0.0:16163
INFO: (app) HTTPS Server running @ http://0.0.0.0:17173
INFO: (provider/match) Replaced: [1962165898] 最伟大的作品
audioId: 1962165898
songName: "最伟大的作品"
url: "http://lv.sycdn.kuwo.cn/35170274b807cb34dd6bbae691cc44f4/681b12d0/resource/30106/trackmedia/M500001yeNa60aLoOu.mp3?bitrate"

通过MacOS客户端访问,没有任何日志输出。2.3.21版本和3.0.13都不能正常使用。

网易云音乐歌曲链接

No response

网易云音乐版本号

2.3.21版本和3.0.13都不能正常使用

操作系统

Apple M1 Pro MacOS 15.3.2

其他信息

No response

问题排查
  • 我确认我使用的核心是由 UnblockNeteaseMusic 项目官方发行,不是其他任何 fork。
  • 我确认我已经升级到了最新的核心版本(推荐使用最新构建而不是 release)。
  • 我确认我已经启用了 HTTPS 端口。
  • 我确认我已经正确设置了 EndPoint。
  • 我确认我已经在对应的客户端正确安装了 CA 证书。

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with app.js and reproduce the reported setup using Node.js v16.20.2 and the provided command, while comparing MacOS client access with web and Windows access. Check whether the MacOS client produces any corresponding server activity or logs; done means the client connects and works without regressing the confirmed web behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.