# \[WS\] Beatport.com by stevehero \[Release, Single Track & Artwork tagging\]

**URL:** <https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568>\
**Category:** Web Sources Scripts\
**Created:** [October 4, 2011, 9:07pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568 "2011-10-04T21:07:57Z")\
**Posts on this page:** 20\
**Page:** 62

<div class="post-metadata">

**Author:** ![stevehero](https://community.mp3tag.de/user_avatar/community.mp3tag.de/stevehero/32/337_2.png) [@stevehero](https://community.mp3tag.de/u/stevehero)\
**Post date:** [May 10, 2026, 12:41pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1244 "2026-05-10T12:41:26Z")

</div>

Using `curl -I https://www.beatport.com/` will return:

```auto
HTTP/1.1 403 Forbidden
Date: Sun, 10 May 2026 12:05:48 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 5194
Connection: close
Accept-Ch: Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model, UA-Platform-Version, UA-Platform, UA
Cf-Mitigated: challenge
Content-Security-Policy: default-src 'none'; script-src 'nonce-QxAJgJURUVrnetEKgeohDg' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare.com blob:; worker-src blob:; form-action http: https:; base-uri 'self'
Server: cloudflare
Critical-Ch: Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model, UA-Platform-Version, UA-Platform, UA
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Resource-Policy: same-origin
Origin-Agent-Cluster: ?1
Permissions-Policy: accelerometer=(),browsing-topics=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),interest-cohort=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=(self)
Referrer-Policy: same-origin
Server-Timing: chlray;desc="9f98d0752ce0be27"
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=31536000; includeSubDomains
CF-RAY: 9f98d0752ce0be27-DUB

```

So this is not a fault with my scripts. Not sure what to say to you guys.

@Florian, what do you think can be done in this case?

---

<div class="post-metadata">

**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\
**Post date:** [May 10, 2026, 1:25pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1245 "2026-05-10T13:25:46Z")

</div>

I don't think that there is something that can be done at the moment, at least I have no idea.

It looks like it's Cloudflare Turnstile requesting a browser challenge (something that requires JS), which is nothing Mp3tag can do.

> **[Cloudflare Turnstile](https://developers.cloudflare.com/turnstile/)**
>
> Verify visitors are human with a CAPTCHA-free, privacy-preserving alternative.

> Turnstile adapts the challenge outcome to the individual visitor or browser. First, we run a series of small non-interactive JavaScript challenges to gather signals about the visitor or browser environment.
> 
> These challenges include proof-of-work (computational puzzles), proof-of-space, probing for web APIs, and various other challenges for detecting browser-quirks and human behavior.

---

<div class="post-metadata">

**Author:** ![stevehero](https://community.mp3tag.de/user_avatar/community.mp3tag.de/stevehero/32/337_2.png) [@stevehero](https://community.mp3tag.de/u/stevehero)\
**Post date:** [May 10, 2026, 7:53pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1247 "2026-05-10T19:53:45Z")

</div>

Thanks for getting back to me Florian. Looks like an API key is what is needed. Don't think they hand them out too easily either.

Just checked with gemini. Things don't look so good.

 ![Screenshot2026-05-10-20-52-07-519com.google.android.googlequicksearchbox-edit](https://community.mp3tag.de/uploads/default/original/3X/6/d/6d47eeda704e348db22e3947cdc1b4a4ccb9e8d4.jpeg)

---

<div class="post-metadata">

**Author:** ![Gizzberto](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/c0e974/32.png) [@Gizzberto](https://community.mp3tag.de/u/Gizzberto)\
**Post date:** [May 11, 2026, 1:37pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1248 "2026-05-11T13:37:06Z")

</div>

Hi, I’m new to this forum, and I’ve been using MP3TAG for years, especially the Beatport feature. Thanks for that. But since yesterday afternoon, I’ve suddenly been unable to use this feature because of a 403 Forbidden error. The funny thing is that, out of the blue, I’ve also had to enter a Cloudflare code every time I visit Beatport. Even though I’ve had the website open all day. I hope a workaround is found soon, and that it gets sorted out quickly. It would be a bummer if I couldn’t use this anymore.

---

<div class="post-metadata">

**Author:** ![apare](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/c6cbf5/32.png) [@apare](https://community.mp3tag.de/u/apare)\
**Post date:** [May 11, 2026, 9:17pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1249 "2026-05-11T21:17:38Z")

</div>

It's working again; it seems Beatport has removed the Cloudflare protection, EnJoy 😉

---

<div class="post-metadata">

**Author:** ![muccy](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/ed655f/32.png) [@muccy](https://community.mp3tag.de/u/muccy)\
**Post date:** [May 12, 2026, 9:41pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1251 "2026-05-12T21:41:02Z")

</div>

if macos, here is a local proxy that bypasses the cloudflare bot protection - all claude code so dont ask me how it works, but it really does.

seems like the captcha has stopped happening for now, but this was working perfectly when it was breaking the search

> **[GitHub - muckymucky/mp3tag-beatport-proxy: Local proxy that lets MP3Tag search Beatport,...](https://github.com/muckymucky/mp3tag-beatport-proxy)**
>
> Local proxy that lets MP3Tag search Beatport, bypassing Cloudflare bot protection

---

<div class="post-metadata">

**Author:** ![apare](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/c6cbf5/32.png) [@apare](https://community.mp3tag.de/u/apare)\
**Post date:** [May 14, 2026, 6:43am UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1252 "2026-05-14T06:43:32Z")

</div>

Not working anymore, today

---

<div class="post-metadata">

**Author:** ![iamyou](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/i/c68b51/32.png) [@iamyou](https://community.mp3tag.de/u/iamyou)\
**Post date:** [May 17, 2026, 12:37pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1253 "2026-05-17T12:37:00Z")

</div>

I'm getting the "403 Error" today too (Sunday, 17 May)

---

<div class="post-metadata">

**Author:** ![ms6676749](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/b4bc9f/32.png) [@ms6676749](https://community.mp3tag.de/u/ms6676749)\
**Post date:** [May 17, 2026, 9:31pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1254 "2026-05-17T21:31:10Z")

</div>

Beatport pages are hidden behind a cloudflare javascript challenge, see stevehero's [post](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1244) from last week. Nothing mp3tag can do.

---

<div class="post-metadata">

**Author:** ![KrissO](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/k/96bed5/32.png) [@KrissO](https://community.mp3tag.de/u/KrissO)\
**Post date:** [May 17, 2026, 10:06pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1255 "2026-05-17T22:06:17Z")

</div>

Hmm so we're screwed atm

---

<div class="post-metadata">

**Author:** ![P.unkt](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/p/0ea827/32.png) [@P.unkt](https://community.mp3tag.de/u/P.unkt)\
**Post date:** [May 20, 2026, 1:36pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1257 "2026-05-20T13:36:49Z")

</div>

Wow, thank you very much for this - I will install and try this soon.

EDIT: Actually I couldn't wait 😉

Tested these scripts successfully:

_Beatport by &stevehero v6#RELEASE Direct by &BEATPORT RELEASE ID.src_

_Beatport by &stevehero v6#RELEASE Direct by &Www(URL).src_

My favorite script

_Beatport by &stevehero v6#RELEASE Search by (Album)Artist + &Release.src_

brings up the List of search results correctly, but when I mark the required release and click Next \> I'm still getting the "403 Forbidden" error.

---

<div class="post-metadata">

**Author:** ![The\_Zhu](https://community.mp3tag.de/user_avatar/community.mp3tag.de/the_zhu/32/22820_2.png) [@The\_Zhu](https://community.mp3tag.de/u/The_Zhu)\
**Post date:** [May 20, 2026, 2:36pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1258 "2026-05-20T14:36:55Z")

</div>

Thanks for the detailed report — two separate things here:

**1) Search → Next → 403:** You're right, this was a real gap. The search-result link (`%_URL%`) in the index parser still pointed at [beatport.com](http://beatport.com), so clicking "Next \>" went straight to Cloudflare. Fixed — there's now one extra one-line edit per Search `.inc` (the line marked `# _URL (REQUIRED FOR PREVIEW BUTTON TO WORK)`). I've updated `Modifications.txt` in the shared folder; please re-download it and apply that line, then fully restart Mp3tag.

**2) "Direct by BEATPORT RELEASE ID" → "URL must contain a hostname":** This one works on my end (tested release IDs 6857591 and 6866001). Since `Direct by www(URL)` works for you through the same proxy, the proxy itself is fine — so it's likely the input. Can you check:

- Does the file actually have a `BEATPORT_RELEASE_ID` tag set to a numeric id? This script reads that tag — if it's empty, the URL collapses to just the host and you'd get exactly that "must contain a hostname" error.

- Paste your exact `[SearchBy]` line from that `.src` so I can spot any typo from the edit.

---

<div class="post-metadata">

**Author:** ![P.unkt](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/p/0ea827/32.png) [@P.unkt](https://community.mp3tag.de/u/P.unkt)\
**Post date:** [May 20, 2026, 4:08pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1259 "2026-05-20T16:08:03Z")

</div>

Thanks for your reply.

For **1) Search → Next → 403:** It works now!

For **2) "Direct by BEATPORT RELEASE ID" → "URL must contain a hostname":** Sorry, my bad! Actually it works.

---

<div class="post-metadata">

**Author:** ![The\_Zhu](https://community.mp3tag.de/user_avatar/community.mp3tag.de/the_zhu/32/22820_2.png) [@The\_Zhu](https://community.mp3tag.de/u/The_Zhu)\
**Post date:** [May 20, 2026, 4:29pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1260 "2026-05-20T16:29:37Z")

</div>

Happy to hear that! 😉 👍

---

<div class="post-metadata">

**Author:** ![brandon210](https://community.mp3tag.de/user_avatar/community.mp3tag.de/brandon210/32/7232_2.png) [@brandon210](https://community.mp3tag.de/u/brandon210)\
**Post date:** [May 21, 2026, 6:55am UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1261 "2026-05-21T06:55:14Z")

</div>

Very simple to modify those INC files and it works like a charm. MANY THANKS!

What's crazy is it seems to search and run faster for me with this proxy on.

---

<div class="post-metadata">

**Author:** ![The\_Zhu](https://community.mp3tag.de/user_avatar/community.mp3tag.de/the_zhu/32/22820_2.png) [@The\_Zhu](https://community.mp3tag.de/u/The_Zhu)\
**Post date:** [May 21, 2026, 7:40am UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1262 "2026-05-21T07:40:34Z")

</div>

Glad it works! And yeah, the speed-up is real – the proxy reuses a single keep-alive connection to Beatport (curl\_cffi), so it skips re-doing the TLS handshake on every request like Mp3tag's built-in client does. Nice side effect. 🙂

---

<div class="post-metadata">

**Author:** ![brandon210](https://community.mp3tag.de/user_avatar/community.mp3tag.de/brandon210/32/7232_2.png) [@brandon210](https://community.mp3tag.de/u/brandon210)\
**Post date:** [May 21, 2026, 7:53am UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1263 "2026-05-21T07:53:37Z")

</div>

Well done, mate. I was shocked how fast these searches have been going. Beatport always was sluggish to pull up, so this saves me some time when I'm retagging several hundred files in a day.

---

<div class="post-metadata">

**Author:** ![DaveSumm](https://community.mp3tag.de/user_avatar/community.mp3tag.de/davesumm/32/7819_2.png) [@DaveSumm](https://community.mp3tag.de/u/DaveSumm)\
**Post date:** [May 21, 2026, 10:30pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1264 "2026-05-21T22:30:42Z")

</div>

Thanks for this workaround. Sadly it doesn't work for me. I get the following error regardless of which I try

 ![Screenshot 2026-05-22 063335](https://community.mp3tag.de/uploads/default/original/3X/1/a/1a42977be9a3a4f31e423d90988e45b8a96f080a.png)

---

<div class="post-metadata">

**Author:** ![The\_Zhu](https://community.mp3tag.de/user_avatar/community.mp3tag.de/the_zhu/32/22820_2.png) [@The\_Zhu](https://community.mp3tag.de/u/The_Zhu)\
**Post date:** [May 22, 2026, 10:43am UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1265 "2026-05-22T10:43:18Z")

</div>

@DaveSumm

That error is from Mp3tag parsing the script **settings** , before any network request – so it's not the proxy itself. `expected value, got 'B' (66)` means Mp3tag's settings parser hit an unexpected character.

A couple of likely causes:

- A find-and-replace that accidentally touched the `...#USER SETTINGS.settings` file or broke a line – that file should stay **unmodified** (only the `.inc` and "Direct" `.src` files need edits).

- The file got saved in the wrong encoding. Make sure edited files are saved as **UTF-8 without BOM**.

Quickest fix: re-install stevehero's original files fresh, then re-apply only the edits in `Modifications.txt` (nothing in the `.settings` file).

Could you also paste the contents of **`scripterror.log`**? It pins down the exact file and line of the syntax error.

---

<div class="post-metadata">

**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\
**Post date:** [May 22, 2026, 2:58pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/1266 "2026-05-22T14:58:51Z")

</div>

> [@DaveSumm](#):
>
> I get the following error regardless of which I try
> 
> ![Screenshot 2026-05-22 063335](https://community.mp3tag.de/uploads/default/original/3X/1/a/1a42977be9a3a4f31e423d90988e45b8a96f080a.png)

It's usually a sign that the file

`Beatport by &stevehero v6#USER SETTIN&GS.settings`

is missing.

[Previous page](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568.md?page=61)

[Next page](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568.md?page=63)