Skip to content

"beatport subscription" error - win11 - traktor 4.4.1 #56

@oskri42

Description

@oskri42

Summarized from a couple of hours of troubleshooting with help of a chatbot (aalmost first time opening powershell so was a bit of a ride lol)

Environment

  • Traktor Pro 4.4.1.22 (Demo)

  • Windows 11

  • WSL2 + Docker Desktop

  • Running latest master:

    • Commit: 76f65f0ef4e830edc2a57f5527e9b85ac34d38e7
    • Commit message: Implement windows compatibility, include windows instructions and traktor patcher from @v1nc (#51)

Setup performed

Followed the Windows instructions from README:

  • Generated certificate using cert/gen-cert.sh
  • Installed server.crt into Windows Trusted Root Certification Authorities
  • Set beatport.license=windows
  • Set server.useKeystore=true
  • Rebuilt Docker image after config changes
  • Added hosts entry:
127.0.0.1 api.beatport.com
  • Patched Traktor Pro 4.exe using patch_traktor.py

Verification performed

Proxy is working

curl -k -v https://api.beatport.com/v4/auth/o/authorize/

returns:

HTTP/2 302
location: traktor://bp_oauth?code=foo

License endpoint works

https://api.beatport.com/v4/my/license/

returns valid JSON license data.

Traktor binary was actually patched

Verified that:

  • Traktor Pro 4.exe differs from Traktor Pro 4.exe.backup
  • Original Windows public key:
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAozFF...

was replaced with:

MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5otU...
  • Original Windows key no longer exists in the binary.

Current behavior

When clicking Beatport login inside Traktor:

  1. Firefox opens
  2. Browser navigates to:
https://api.beatport.com/v4/auth/o/authorize/?client_id=...
  1. Docker log shows:
302 Found: GET - /v4/auth/o/authorize/
  1. Traktor regains focus automatically (callback seems to be received)
  2. Traktor shows:
Beatport login error

Failed to login due to unknown error, please report this issue!

Please log in with an active Beatport subscription account.

Important observation

The proxy never receives any subsequent requests:

POST /v4/auth/o/token/
GET /v4/my/license/
GET /v4/my/account/

Only /v4/auth/o/authorize/ is ever called.

This suggests Traktor aborts the login flow immediately after receiving the callback and before attempting token exchange.

Additional notes

  • Clearing Traktor Beatport cache did not help.
  • Hosts redirection is confirmed working.
  • Certificate is trusted by Windows.
  • Browser redirect to traktor://bp_oauth?code=foo works.
  • The issue appears after callback handling inside Traktor.

Has anyone successfully tested PR #51 / commit 76f65f0 with Traktor Pro 4.4.1.22 specifically?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions