Mp3tag Proxy v2.3.0 is out 
port=<number> in proxy.cfg, no rebuild needed)Thanks to everyone who reported issues, several of these came straight from your feedback. 
The_Zhu, I just tested your latest release, Mp3tag Proxy v2.3.1. It works perfectly. However, in my setup it still uses Microsoft Edge (my primary browsers are Chrome and Firefox). I'm not sure under what circumstances it would use those other browsers to complete the challenge.
What I'd like to know is: in my current configuration, will it continue to use Edge and the associated cf_clearance cookie?
Correct. As long as Edge is installed (it ships with Windows), it'll keep using Edge for this, regardless of what your primary browser is. The detection order is Edge, then Chrome, and it stops at the first one it finds, so Edge always wins if present. Chrome is just a fallback for machines where Edge is missing or too old (pre Chromium). Firefox isn't supported at all, since the solver needs a Chromium based browser.
As for resources, no need to worry. Edge isn't running all the time, only when a challenge actually needs solving, or when the previous session's clearance cookie has expired, and that's typically 5 to 10 seconds. It's a real browser process, so there's a short CPU/RAM bump while it launches, but it's a one time spike, not a background drain. It also uses a separate throwaway profile in a temp folder, so it never touches your real Edge profile, bookmarks, or history, and it's closed and cleaned up automatically right after. GPU acceleration and account sync are disabled on launch too, to keep it lighter. Once it gets the clearance cookie, that's cached, so it doesn't relaunch on every request either.
So yes, in your setup it'll keep using Edge, briefly and on demand, and the cf_clearance cookie tied to it. 
The_Zhu, I'm tempted to uninstall Edge 150 (which I absolutely hate).
You mentioned that if your proxy detects an unsupported or outdated Edge browser version, it automatically falls back to Chrome to solve the challenge.
So, by uninstalling Edge, I'd end up with the original 2018 version of Edge that came with my Windows 10 installation. However, since everything is working perfectly right now, I'm very hesitant to try this. What do you think? Should I just leave everything as it is, since it's working flawlessly?
If it's working flawlessly, I'd leave it as is. No need to fix what isn't broken. And just so you know: even if you did uninstall Edge and ended up back on the old 2018 EdgeHTML version, the proxy would notice it can't drive that one and fall back to Chrome automatically, so you wouldn't lose functionality either way. But there's no upside to switching right now, so I'd just keep things as they are.
The_Zhu, I've decided to leave everything as it is for now, since it's working. But do you think the settings I use to launch Chrome could interfere with your proxy (if i unistall Edge)?
--disk-cache-dir="F:\chrome" --disk-cache-size=104857600 --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled
No, they don't. The proxy launches its own separate, temporary Chrome instance just to solve the challenge, your normal Chrome flags never apply to it.
Update: Found the proxy! Incredible work thank you!
Hi! Is this script working currently? I get this error:
