# Can not reach musicbrainz.org with WSS

**URL:** https://community.mp3tag.de/t/can-not-reach-musicbrainz-org-with-wss/66972
**Category:** Support
**Created:** [December 27, 2024, 7:02pm UTC](https://community.mp3tag.de/t/can-not-reach-musicbrainz-org-with-wss/66972 "2024-12-27T19:02:01Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![Volans](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/v/ecc23a/32.png) [@Volans](https://community.mp3tag.de/u/Volans)
#### Post date: [December 27, 2024, 7:02pm UTC](https://community.mp3tag.de/t/can-not-reach-musicbrainz-org-with-wss/66972/1 "2024-12-27T19:02:01Z")

</div>

Hi everyone! 🙂

I just started to use custom WSS. It would be great to get meta data from MusicBrainz, but unfortunately the built in MusicBrainz WSS and this expanded one only give me this error when I try to search for something:

 ![grafik](https://community.mp3tag.de/uploads/default/original/3X/d/a/da7e91459a2a83358873bbd9e978017318f40f04.png)

---

<div class="post-metadata">

### Author: ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [December 27, 2024, 7:34pm UTC](https://community.mp3tag.de/t/can-not-reach-musicbrainz-org-with-wss/66972/2 "2024-12-27T19:34:47Z")

</div>

Both scripts (the built-in and my "expanded" one) work fine here on my PC.

Do you use any firewall?  
Can you call this example URL directly in your browser?  
[https://musicbrainz.org/ws/2/release/e42c3d5d-6e61-4554-88f3-0146165ac950](https://musicbrainz.org/ws/2/release/e42c3d5d-6e61-4554-88f3-0146165ac950)

You should get this result:

```auto
<metadata xmlns="http://musicbrainz.org/ns/mmd-2.0#">
<release id="e42c3d5d-6e61-4554-88f3-0146165ac950">
<title>Wow! (Live At The Childe Harold)</title>
<quality>normal</quality>
<date>2024-12-06</date>
<release-event-list count="1">
<release-event>
<date>2024-12-06</date>
</release-event>
</release-event-list>
<barcode>617270123171</barcode>
<cover-art-archive>
<artwork>true</artwork>
<count>1</count>
<front>true</front>
<back>false</back>
</cover-art-archive>
</release>
</metadata>

```

---

<div class="post-metadata">

### Author: ![Volans](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/v/ecc23a/32.png) [@Volans](https://community.mp3tag.de/u/Volans)
#### Post date: [December 27, 2024, 8:37pm UTC](https://community.mp3tag.de/t/can-not-reach-musicbrainz-org-with-wss/66972/3 "2024-12-27T20:37:23Z")

</div>

Thank you for this hint! I'm using a PPPoE connection over optical fibre to my ISP. My WAN MTU was 1480 by default. I changed it to 1400, now it works. I have no idea why. Never had any problems connectin to websites.

 ![grafik](https://community.mp3tag.de/uploads/default/original/3X/d/5/d55c02da8e9017f170aeaa4b496f867fbd5668fc.png)

---

<div class="post-metadata">

### Author: ![poster](https://community.mp3tag.de/user_avatar/community.mp3tag.de/poster/32/4881_2.png) [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [December 28, 2024, 7:39am UTC](https://community.mp3tag.de/t/can-not-reach-musicbrainz-org-with-wss/66972/4 "2024-12-28T07:39:18Z")

</div>

Does your equipment not support MSS Clamping?

---

<div class="post-metadata">

### Author: ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [December 28, 2024, 10:31am UTC](https://community.mp3tag.de/t/can-not-reach-musicbrainz-org-with-wss/66972/5 "2024-12-28T10:31:08Z")

</div>

For those interested in the details about MTU ( **M** aximum **T** ransmission **U** nit) and MSS ( **M** aximum **S** egment **S** ize) clamping you can find very detailed explanations here:

[https://lostintransit.se/2024/09/05/mss-mss-clamping-pmtud-and-mtu/](https://lostintransit.se/2024/09/05/mss-mss-clamping-pmtud-and-mtu/)

On Windows, you can find your current MTU size with these 2 steps:  
a) Open a CMD window  
b) Enter `netsh interface ipv4 show interfaces`  
Then you see the MTU size for every network interface in your device like in this example in the 3rd column of the output (for Windows usually _1500_)

```auto
Idx Met MTU State Name
--- ---------- ---------- ------------ ---------------------------
  1 75 4294967295 connected Loopback Pseudo-Interface 1
  3 65 1500 disconnected Bluetooth-Netzwerkverbindung
  4 35 1500 connected VMware Network Adapter VMnet1
 15 35 1500 connected VMware Network Adapter VMnet8
 11 5 1500 disconnected Ethernet 1Gbit
  6 15 9000 connected Ethernet 10Gbit

```

If you have multiple interfaces in your device, you can also see which interface status is currently _connected_ or _disconnected_.

Warning: Only change this MTU size permanently if you are absolutely sure what you are doing!

---

<div class="post-metadata">

### Author: ![Volans](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/v/ecc23a/32.png) [@Volans](https://community.mp3tag.de/u/Volans)
#### Post date: [December 28, 2024, 10:48am UTC](https://community.mp3tag.de/t/can-not-reach-musicbrainz-org-with-wss/66972/6 "2024-12-28T10:48:25Z")

</div>

But I think the best idea would be to setup MSS clamping on the router, like @poster said. You don't need MSS clamping on your LAN, an MTU of 1500 works fine there most of the time.

I was able to set the MTU back to 1492 on my PPPoE WAN connection and setup MSS clamping on my RouterOS, like here: [Fixing Website Access Issues with Mikrotik MSS Clamping - David Stein](https://davidstein.cz/2024/10/17/fixing-website-access-issues-with-mikrotik-mss-clamping/)

Now [musicbrainz.org](http://musicbrainz.org) works perfect! 🙂

---

<div class="post-metadata">

### Author: ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [December 28, 2024, 11:05am UTC](https://community.mp3tag.de/t/can-not-reach-musicbrainz-org-with-wss/66972/7 "2024-12-28T11:05:24Z")

</div>

Just for the record:

Your difference in the MTU 1500 - 1492 = [**8 bytes**](https://en.wikipedia.org/wiki/Point-to-Point_Protocol_over_Ethernet#MTU/MRU) is caused by using a PPPoE interface where the PPPoE header uses additional 6 bytes and the PPP protocol ID uses additional 2 bytes, correct?

---

<div class="post-metadata">

### Author: ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)
#### Post date: [January 27, 2025, 11:05am UTC](https://community.mp3tag.de/t/can-not-reach-musicbrainz-org-with-wss/66972/8 "2025-01-27T11:05:43Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
