Beatport by &stevehero v6_Release Direct.inc
[Name]=beatport.com [v6.004 by stevehero™] (◣_◢)
[MinAppVersionMac]=1.8.4
[MinAppVersionWin]=3.22
[Settings]=Beatport by &stevehero v6#USER SETTIN&GS.settings
[AlbumUrl]=
[BasedOn]=http://127.0.0.1:8787/
[IndexUrl]=http://127.0.0.1:8787/
Beatport by &stevehero v6#RELEASE Direct by &Www(URL).src
SearchBy]=RELEASE Direct by www(URL)||$trim($lower($regexp($regexp(%www%,(?i)^www,https://www),\bhttp\b,https,classic.beatport),www.beatport,https://pro.beatport,https://www.beatport))||http://127.0.0.1:8787/%s
[Include]=Beatport by &stevehero v6_Release Direct.inc
Your file's WWW tag still has an old proxy link in it, so the proxy address ends up doubled and that breaks it. Just set the WWW tag back to a normal Beatport link:
https://www.beatport.com/release/lara/6932610
Then run it again.
(Tip: "RELEASE Direct by ID" — where you just paste the number 6932610 — doesn't use the WWW tag at all, so it avoids this completely.)
Cloudflare, to access (https://www.beatport.com/) even in the Chrome browser, asked me today to verify that I was human by completing a challenge (Firefox too ask me the same)
Chrome Version 150.0.7871.47 (Official Build) (64-bit)
Firefox 151.0.4 (64-bit)
I changed several IP addresses, but I got the same result
@Florian It would be great if Mp3tag could detect when a website is protected by Cloudflare and automatically open an embedded browser (such as WebView2). The user could complete the normal "Verify you are human" challenge, after which Mp3tag would reuse the authenticated session to continue accessing the site. This would allow legitimate access to Cloudflare-protected websites without requiring manual workarounds.
For anyone hitting 403 Forbidden on Beatport or Traxsource — I've moved the fix into its own topic so it's easier to find and follow: Mp3tag Proxy, a small free Windows tool that works around the Cloudflare block so your tag-source scripts work again.
I haven't changed anything in any file. Just like two days ago, everything is still working perfectly with the original proxy_beatport. It also starts up in just a few seconds, whereas the new one takes much longer to initialize.
That said, I really appreciate the work and effort you've put into the new version. It looks like a great improvement, but for my current setup I don't need it at the moment since the original proxy is still working flawlessly for me.
From what I've read on a few developer forums, Cloudflare seems to have rolled back some of the recent changes because the latest Bot Detector update ended up breaking quite a few things. So, as far as I understand, they reverted to an earlier implementation.
You're right -- maybe a second slower on startup. That's the only difference.
The new version is universal. When Beatport uses the simple check (like right now), it takes the same fast path as the original, no browser involved. It only switches to the heavier path if Beatport brings the JavaScript challenge back -- which already happened once this week.
So you never have to think about which version to run: fast path by default, and if Cloudflare tightens again, v2.1.1 deals with it automatically.
Keep the old one if you're happy with it, but v2.1.1 has you covered either way.
