Can't connect to Musicbrainz.org website and Picard doesn't check music on home network

Hello,

I think I’m facing the same situation. My IP adress is 82.64.77.95.
Possible to check if not blaclisted ?

Thank you in advance.

This IP isn’t blocked on our side. Does the problem persist?

A little internet research and it appears that the offending QNAS app is “Music Station”.

I have no idea which version the fix was provided in, but here is the change log: Music Station - Release Notes for Apps - QNAP

The change log has loads of fixes for security vulnerabilities listed, so QNAP security definitely seems to be an issue.

Also, this Music Station app appears to be:
a. Installed by default
b. Enabled by default
c. Have musicbrainz lookups enabled by default
c. Sharing personal data (details of music files) with a 3rd party (musicbrainz) without having gained user permission to do so.
d. Making calls to Musicbrainz despite the user not actually using Music Station streaming or having explicitly stored files for Music Station’s use.
e. Making commercial use of Musicbrainz without being willing to support Metabrainz foundation with a (relatively cheap) support contract: Support - MetaBrainz Foundation
f. Apparently being too stupid to realise that with a partnership with Metabrainz they could deliver a better customer experience, quicker and without drama (i.e. without their customers having their IP addresses banned).

2 Likes

Can’t check at the moment but I’ll let you know soon.

Unfortunately, musicbrainz.org domain/IP is still unreachable…

Are you sure the IP you gave is the IP you have as seen from the internet? Can you check?

Yes, I can confirm you that my IP is 82.64.77.95

So your IP isn’t blocked on our side, the issue is elsewhere.

  • Does musicbrainz.org correctly resolved to 138.201.203.25?
  • Can you ping musicbrainz.org?
  • Can you provide a traceroute from 82.64.77.95 to 138.201.203.25?

Yes for sure !

Traceroute:
tracert musicbrainz.org

Détermination de l?itinéraire vers musicbrainz.org [138.201.227.205]
avec un maximum de 30 sauts :

1 2 ms <1 ms <1 ms FREEBOX_SERVER [192.168.0.254]
2 * * * Délai d?attente de la demande dépassé.
3 * * * Délai d?attente de la demande dépassé.
4 12 ms 11 ms * decix-gw.hetzner.com [80.81.192.164]
5 46 ms 21 ms 16 ms core23.fsn1.hetzner.com [213.239.252.38]
6 17 ms 16 ms 15 ms ex9k3.dc8.fsn1.hetzner.com [213.239.229.138]
7 * * * Délai d?attente de la demande dépassé.
8 * * * Délai d?attente de la demande dépassé.
9 * * * Délai d?attente de la demande dépassé.
10 * * * Délai d?attente de la demande dépassé.
11 * * * Délai d?attente de la demande dépassé.
12 * * * Délai d?attente de la demande dépassé.
13 * * * Délai d?attente de la demande dépassé.
14 * * * Délai d?attente de la demande dépassé.
15 * * * Délai d?attente de la demande dépassé.
16 * * * Délai d?attente de la demande dépassé.
17 * * * Délai d?attente de la demande dépassé.
18 * * * Délai d?attente de la demande dépassé.
19 * * * Délai d?attente de la demande dépassé.
20 * * * Délai d?attente de la demande dépassé.
21 * * * Délai d?attente de la demande dépassé.
22 * * * Délai d?attente de la demande dépassé.
23 * * * Délai d?attente de la demande dépassé.
24 * * * Délai d?attente de la demande dépassé.
25 * * * Délai d?attente de la demande dépassé.
26 * * * Délai d?attente de la demande dépassé.
27 * * * Délai d?attente de la demande dépassé.
28 * * * Délai d?attente de la demande dépassé.
29 * * * Délai d?attente de la demande dépassé.
30 * * * Délai d?attente de la demande dépassé.

Itinéraire déterminé.

Ping result:
ping musicbrainz.org

Envoi d?une requête ‘ping’ sur musicbrainz.org [138.201.227.205] avec 32 octets de données :
Délai d?attente de la demande dépassé.
Délai d?attente de la demande dépassé.
Délai d?attente de la demande dépassé.
Délai d?attente de la demande dépassé.

Statistiques Ping pour 138.201.227.205:
Paquets : envoyés = 4, reçus = 0, perdus = 4 (perte 100%),

Weird, it might be an issue between your provider (Free) and Hetzner.

I can ask Hetzner to check but they need output of a bidirectional mtr

https://docs.hetzner.com/robot/dedicated-server/troubleshooting/network-diagnosis-and-report-to-hetzner/

mtr -s 1000 -r -c 1000 138.201.203.25

It takes some time to complete.

I’m an Arch Linux user, will definitely make the test and post output here if you want

[guillaume@guillaume-ux305ca ~]$ mtr -s 1000 -r -c 1000 138.201.203.25
Start: 2022-10-05T16:10:47+0200
HOST: guillaume-ux305ca           Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- _gateway                   7.7%  1000    6.1   4.4   0.9 582.2  22.0
  2.|-- 194.149.169.89            83.1%  1000    4.4   9.7   3.2 646.7  50.5
  3.|-- decix.proxad.net          88.8%  1000   12.5  20.0  11.8 619.6  57.9
  4.|-- decix-gw.hetzner.com       1.4%  1000   33.0  16.3  11.2 570.0  24.3
  5.|-- core23.fsn1.hetzner.com    0.8%  1000   28.5  24.9  15.9 525.6  24.6
  6.|-- ex9k3.dc8.fsn1.hetzner.co  0.0%  1000   19.2  20.9  15.8 483.2  21.0
  7.|-- ???                       100.0  1000    0.0   0.0   0.0   0.0   0.0

I did ask to Hetzner about this.
You should also ask your provider I think.

Here is the reverse mtr:

zas@kiki:~$ mtr -s 1000 -r -c 1000 82.64.77.95
Start: Wed Oct  5 11:44:47 2022
HOST: kiki                        Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- ???                       100.0  1000    0.0   0.0   0.0   0.0   0.0
  2.|-- core24.fsn1.hetzner.com    0.0%  1000    0.4   7.9   0.3  73.2  11.6
  3.|-- core0.fra.hetzner.com      0.0%  1000    9.5   8.3   4.9  54.5   6.5
  4.|-- decix.proxad.net           0.1%  1000    5.5   5.4   5.4   7.6   0.1
  5.|-- ???                       100.0  1000    0.0   0.0   0.0   0.0   0.0

Thank you Zas for this precious information. Just forwarded these outputs to my ISP.

1 Like

Actually, I found the issue, and that’s on our side.
It happens your IP was banned by another tool running on our gateway.
The thing is it was somehow hidden, as the tool (crowdsec) wasn’t displaying your IP as banned, but it was still appearing in an ipset.
So basically, your IP was blocked on our side but I missed that.

It is now solved (please confirm), welcome back to MusicBrainz services.
Very sorry for the inconvenience.

3 Likes

Thank you ! I can confirm that I can connect now to musicbrainz.org :wink:

4 Likes

Hi Zas, me again :wink:
I’m having issue connecting to other domain (My corporate VPN) from my ISP and wondering if the issue could be related with my banned IP. Is crowdsec banned IP list centralized with other apps using this service ? Or is it only related with musicbrainz.org domain ?
Thank you in advance for your reply :wink:

1 Like

You can ask them a removal to Remove an IP from CrowdSec's blocklist - The open-source & collaborative IPS

3 Likes

Hi Zas. Can you check IP 94.31.86.180.

I think it is banned. Thx for your time.

Kind regards Nexus

It should be solved now, sorry for the inconvenience.

1 Like