How to use UnblockNeteaseMusic: run the proxy and set hosts or system proxy

What UnblockNeteaseMusic does and who it suits

Netease Cloud Music sometimes marks songs as unavailable, often because of licensing or region. UnblockNeteaseMusic runs a local proxy server that redirects those song requests to matching tracks from other platforms, and it can also act as a full HTTP/HTTPS system proxy.

The project is a fit for people who use the Netease Cloud Music desktop or mobile client and hit greyed-out tracks, and who are comfortable editing a hosts file or setting a system proxy. It is not an official service: the README calls it a reverse-engineering workaround and says there is no public demo.

Install UnblockNeteaseMusic with npx or Docker

The README gives two quick ways to start the program. You need Node.js for the npx route; the README excerpt does not state a required Node.js version. Docker is an optional alternative.

• Run with npx (Node.js required)
• Run with Docker

Choose a method to route the client through the proxy

Method 1 edits your hosts file so that music.163.com and interface.music.163.com point to your server IP. The README says this method requires listening on port 80, so you must start the server with -p 80. If you run the program on the same machine, you must also set the Netease server IP with -f or use an upstream proxy with -u, otherwise requests can loop. The README notes that hosts editing does not work directly on the Android client.

Method 2 sets a proxy instead. Use the PAC script at http://<Server Name:PORT>/proxy.pac, or enter the server address and port as a global proxy. The README lists where to find this setting on Windows, UWP, Linux, macOS, Android and iOS.

• Hosts file: add the two lines music.163.com and interface.music.163.com pointing to <Server IP>, with the server on port 80
• System proxy: use the PAC address or the server address and port in your OS network settings

Use the command-line options

The program accepts flags that control the port, address, upstream proxy, forced Netease IP, source priority, authentication and strict mode. Run the help flag to see the full list on your installed version.

• -p port: server port
• -a address: server host
• -u url: request through an upstream proxy
• -f host: force the Netease server IP
• -o source: set priority of music sources
• -t token: proxy authentication (the README says it does not currently work)
• -e url: replace the virtual endpoint with a public host
• -s: strict mode, which only allows Netease domains

Secure the proxy before exposing it

Do not run the proxy on the public internet without protection. The README strongly recommends strict mode (-s), which only passes requests for Netease domains, and says this needs PAC or hosts. The README also says the password option does not currently work on the Windows client or macOS system settings, so do not rely on it.

Do not use public proxy services run by other people, because the README warns of security risks.

Use it as a Node.js library

Developers can install the package with npm and call the matching function directly. The function takes a Netease song ID and an optional list of sources, and returns a promise. The README example shows optional global proxy and hosts settings.