Jukebox randomly stops playing

Rabulias said: Have you tried whitelisting fanburst.com in your adblocker, too? Good thinking, I'll do that now and post back with my results. Edit: The whitelisting of Fanbursts site made no difference and after approximately an hourish I got the following error: <a href="https://dl-a-82.fanburst.com/?f=c48112d4-4ce3-467f-8af9-432fc009fe0e.mp3&m=…9-432fc009fe0e.mp3&e=1487916391&s=3e4b8ef5c7b0bd0e5d376fc100e423b2176e2652" rel="nofollow">https://dl-a-82.fanburst.com/?f=c48112d4-4ce3-467f-8af9-432fc009fe0e.mp3&m=…9-432fc009fe0e.mp3&e=1487916391&s=3e4b8ef5c7b0bd0e5d376fc100e423b2176e2652</a> Failed to load resource: the server responded with a status of 500 (Internal Server Error)

This problem is driving me nuts. I've seen it happen, myself, but never in an environment where I'm able to dig into it. I had hoped the ad-block would be an easy fix, but that would have been too easy. I am just telling everyone this to say: I have not been able to fix it yet, but I'm still working on it and will be taking another crack at it next week if I don't manage an "epiphany moment" before the end of the day today.

Thanks for the update Phil.

Thanks for the update, do you still need/want us to post log errors from chrome here?

If you have a log that has different information than the ones that have already been posted, yes. I'll take as much information as you can give me.

I still have not been able to reproduce the error locally, where I can try to fix it. It might be because I'm not testing it during peek hours, since I work during the day and peek hours are in the evening. Also, the more I look into this, the more it looks like an issue on their end. The error "ERR_CONTENT_LENGTH_MISMATCH" is popping up directly from chrome, not from our code. It's happening because of a security measure, where any time an HTTP request is made (us asking the Fanburst API for a track) the response comes with a number that says how long the response is. It does this to make sure that nothing was lost/added in the transmission. We ask for a track, the API responds with "here is a song that is 2000 bytes long", but the song is actually 1900 bytes long, so Chrome blocks it since something went wrong. I could put in a retry in if the error pops up, but from what I have seen and what many of you have said, refreshing or trying to load the music again rarely fixes the issue. So, my guess is that trying again fractions of a second later isn't going to help either. I've emailed their team and am hoping to hear back from their devs about possibly fixing this issue from their end, or maybe they have some ideas on how to work around it on ours. I will keep you in the loop as I learn more. Sorry again for how long this is taking.

Hey Phil, I'd just like to point out that there is at least&nbsp; one report in this thread&nbsp; of it occurring unrelated to fanburst.

Scott C: While the issue has the same outcome, the music stopping, I do not think these are related. I will have to handle that one separately. As for the Content Length issue, I've been talking with one of the Fanburst devs. He believes he's identified the issue. Something about their proxy server that hosts the streams filling up faster than they can clear them, which makes for partial files being returned as the disk can't handle the load. He says he's made some changes that should fix this in the short term, with a more permanent fix planned to go out Sunday evening. So please let me know if you see this issue again so I can pass on the word.

Sounds good

Oh, that sounds promising. Thanks for the update, Phil.

If there was a short term fix, it doesn't seem to have done anything as I got the music to stop after an hour and a half. GET <a href="https://dl-a-82.fanburst.com/?f=de8c828a-97ae-49d" rel="nofollow">https://dl-a-82.fanburst.com/?f=de8c828a-97ae-49d</a>... 500 (Internal Server Error) Edit: When trying to play it again before refreshing, I get this: Uncaught (in promise) DOMException: The play() request was interrupted by a call to pause().

It looks like they were still having issues wit the temporary fix. Hopefully the full fix that went out last night did a better job. If people who were having the issue before are able to play at the same time and not see it pop up any more please let me know. Also let me know if you are still seeing issues so that I can pass the word along to the Fanburst devs.

I seem to be getting the exact same errors again. It doesn't appear that whatever has been done has fixed the issue... Edit: For clarity, I just tried it. Started music at 6 pm and it died at ~7:30 PM.

Pakki said: I seem to be getting the exact same errors again. It doesn't appear that whatever has been done has fixed the issue... Edit: For clarity, I just tried it. Started music at 6 pm and it died at ~7:30 PM. Same here. Nothing has changed. Forgot to add the error message: Uncaught (in promise) DOMException: The play() request was interrupted by a call to pause().

Still no luck. Error message: Failed to load resource: the server responded with a status of 500 (Internal Server Error) Are you sure that the Fanburst boys implemented anything?

Just to be sure, you are still receiving the ERR_CONTENT_LENGTH_MISMATCH error, specifically? If it's still pausing, but you are not getting this error it might be something else entirely. I've let them know that you all are still seeing the issue. They said that rules out what they originally though was the issue and are trying to figure out what else might be causing it. He asked for the headers from the failed request (the information from the network log that I asked for previously), as they might provide some insight on what the issue might be. It seems like this isn't just a simple fix and they are going to have to do some serious digging to figure out what's causing it.

Here's the info from my failed request (roughly two hours of continually looped track): General: Request URL: <a href="https://dl-a-82.fanburst.com/?f=229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3&m=mp3&df=229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3&e=1489175029&s=e1afbf1b57b9a5052d1c594480ff6b91eb04aacc" rel="nofollow">https://dl-a-82.fanburst.com/?f=229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3&m=mp3&df=229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3&e=1489175029&s=e1afbf1b57b9a5052d1c594480ff6b91eb04aacc</a> Request Method: GET Status Code: 500 Internal Server Error Remote Address: 206.190.136.164:443 Response Headers: Connection: keep-alive Date: Fri, 10 Mar 2017 19:46:53 GMT Server: nginx/1.9.7 Transfer-Encoding: chunked Request Headers: Accept: */* Accept-Encoding: identity;q=1, *;q=0 Accept-Language: en-US,en;q=0.8 Cache-Control: max-age=0 Connection: keep-alive Host: dl-a-82.fanburst.com If-Match: "58bb371c-3f00a7" Range: bytes=0- Referer: <a href="https://app.roll20.net/editor/" rel="nofollow">https://app.roll20.net/editor/</a> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Query String Parameters: f: 229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3 m: mp3 df: 229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3 e: 1489175029 s: e1afbf1b57b9a5052d1c594480ff6b91eb04aacc Name 0 ?f=229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3&m=mp3&df=229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3&e=1489175029&s=e1afbf1b57b9a5052d1c594480ff6b91eb04aacc ?f=229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3&m=mp3&df=229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3&e=1489175029&s=e1afbf1b57b9a5052d1c594480ff6b91eb04aacc 0 ?f=229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3&m=mp3&df=229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3&e=1489175029&s=e1afbf1b57b9a5052d1c594480ff6b91eb04aacc 0 ?f=229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3&m=mp3&df=229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3&e=1489175029&s=e1afbf1b57b9a5052d1c594480ff6b91eb04aacc 0 0 0 0 .ws?v=5&ls=snOD1pqebiJojZzxEi5CeRD1zHLxh6fV&ns=roll20-27 0 mini.jpg?1481314336 character.png 0 63 requests ❘ 49.9 MB transferred Console top AdBlock⚙ sheetsandboxworker.js Preserve log Show all messages 3 dl-a-82.fanburst.com/:1 GET <a href="https://dl-a-82.fanburst.com/?f=229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3&m=…2-c4d053d6e6f8.mp3&e=1489175029&s=e1afbf1b57b9a5052d1c594480ff6b91eb04aacc" rel="nofollow">https://dl-a-82.fanburst.com/?f=229b578b-1148-40c3-ba72-c4d053d6e6f8.mp3&m=…2-c4d053d6e6f8.mp3&e=1489175029&s=e1afbf1b57b9a5052d1c594480ff6b91eb04aacc</a> 500 (Internal Server Error) app.js?1488996874:31 Firebase Offline app.js?1488996874:35 Player -KbGy4eHkxjO9HYgAs1I is offline... app.js?1488996874:31 Firebase Online app.js?1488996874:33 Do refresh link cache! app.js?1488996874:45 Refresh Journal List! app.js?1488996874:45 Search took 12ms And a&nbsp; gist of the complete console log for the session

Sorry for the odd formatting, It comes out really weird when I copy/paste it and attempting to do anything to it just deletes it. Also, the console log is super long because I was doing script development while just running music with my computer on mute.

Phil B. said: Just to be sure, you are still receiving the ERR_CONTENT_LENGTH_MISMATCH error, specifically? If it's still pausing, but you are not getting this error it might be something else entirely. In my post, yes, that was the error I was still receiving. That error, however, seems to appear multiple times before the music stops playing. So far, whenever I went in solely to play the music on loop, it seems that the console log is identical to errors before the fix. Hopefully they can find something in scott's info -- I'll be grabbing my log when I test out later today. Edit: Tested it and grabbed the header info. Request URL: <a href="https://dl-a-82.fanburst.com/?f=bd569bc2-1158-4184" rel="nofollow">https://dl-a-82.fanburst.com/?f=bd569bc2-1158-4184</a>... Request Method: GET Status Code: 500 Internal Server Error Remote Address: 206.190.136.164:443 Response Headersview source Connection: keep-alive Date: Sat, 11 Mar 2017 03:35:15 GMT Server: nginx/1.9.7 Transfer-Encoding: chunked Request Headersview source Accept: */* Accept-Encoding: identity;q=1, *;q=0 Accept-Language: en-US,en;q=0.8 Cache-Control: max-age=0 Connection: keep-alive Cookie: ahoy_visitor=8f9a4000-eca7-49ea-98ab-e39bdea0f07e; amplitude_idfanburst.com=eyJkZXZpY2VJZCI6IjE3Y2NjYTNhLWMxMWEtNDFhZS05ZDllLTFkYzQ5NWYyM2NjN1IiLCJ1c2VySWQiOiJ5MGxnd3kiLCJvcHRPdXQiOmZhbHNlLCJzZXNzaW9uSWQiOjE0ODg1OTY4MjYwMDYsImxhc3RFdmVudFRpbWUiOjE0ODg1OTc2OTg1OTYsImV2ZW50SWQiOjExLCJpZGVudGlmeUlkIjowLCJzZXF1ZW5jZU51bWJlciI6MTF9; _ga=GA1.2.1451125878.1488004348 Host: dl-a-82.fanburst.com If-Match: "58883680-e31e93" Range: bytes=0- Referer: <a href="https://app.roll20.net/editor/" rel="nofollow">https://app.roll20.net/editor/</a> User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Query String Parametersview sourceview URL encoded I got our friend here like every few minutes: GET <a href="https://dl-a-82.fanburst.com/?f=bd569bc2-1158-418" rel="nofollow">https://dl-a-82.fanburst.com/?f=bd569bc2-1158-418</a>... net::ERR_CONTENT_LENGTH_MISMATCH and of course GET <a href="https://dl-a-82.fanburst.com/?f=bd569bc2-1158-4184-8202-4382f1bdd0c4.mp3&m=…2-4382f1bdd0c4.mp3&e=1489203193&s=a1e9aaab34a7457c5d3a3b6c01ab65d353e07a14" rel="nofollow">https://dl-a-82.fanburst.com/?f=bd569bc2-1158-4184-8202-4382f1bdd0c4.mp3&m=…2-4382f1bdd0c4.mp3&e=1489203193&s=a1e9aaab34a7457c5d3a3b6c01ab65d353e07a14</a> 500 (Internal Server Error)

Huh. I seem to be getting a new error now. Failed to load resource: the server responded with a status of 412 (Precondition Failed)

Pakki said: Huh. I seem to be getting a new error now. Failed to load resource: the server responded with a status of 412 (Precondition Failed) Still getting: Failed to load resource: the server responded with a status of 500 (Internal Server Error)

I still have the problem, same errors as when I posted two months ago (see early in this thread). I have whitelisted roll20 and fanburst in my browser's pop-up blocker (is that the same as adblocker? I don't have any extensions enabled and nothing named adblocker). I screencapped this network info&nbsp; which you can see the music stopped after 1.2 hours and the size varies with each loop of playing. And this last bit of the console log which gives constant net::ERR_CONTENT_LENGTH_MISMATCH errors ending with the 500 error;

My players and I keep getting out of sync -- I'll hear music, they won't, or they will but I won't, and refreshing can lead to weirdness like the song restarting for me but not my players.&nbsp; Opening up the Chrome Developer Tools, I notice net::ERR_CONTENT_LENGTH_MISMATCH messages. EDIT: Funny thing is, the error messages start showing up even when I'm the only one in the game at the time and the music is playing fine. EDIT2: I left for a while, and when I came back the music had stopped and I had the 500 (Internal Server Error) message, as well as several more length mismatch ones. It looks &nbsp;like those just keeping popping up, and eventually when the music actually stops you get the server error message? No idea if that's helpful and/or surprising.

I'm still working with one of the Fanburst devs, he's still digging trying to find the source of this issue. I have another question for you all: have you ever seen this issue outside of Chrome? In some of the earlier messages some of you talked about using FireFox to fix it. Have you ever seen this issue in FireFox?

Phil B. said: I'm still working with one of the Fanburst devs, he's still digging trying to find the source of this issue. I have another question for you all: have you ever seen this issue outside of Chrome? In some of the earlier messages some of you talked about using FireFox to fix it. Have you ever seen this issue in FireFox? When using FireFox I have had zero issues with music, it's only Chrome that has the problem (and not just with Fanburst, but also Incompotech, Battlebards etc.)

Some of my players have reported that the music has, in very rare occassions, stopped on firefox. I will have to catch a console log if I ever find this case on my end.

I have good news! My Fanburst contact, that has been digging through libraries and all kinds of crazy ideas, was finally able to consistently recreate the issue on his end. Once he was able to do that, he was able to quickly find what the issues was. In simple-ish terms, it was an issue specifically with validation of songs that were not cached and had to be loaded from their central storage. He has now, already, fixed it. So, if you see this (or don't see it when you used to) or any other streaming errors please let me know. If you DO get an error, please be specific about what error you get and when you get it, it might be a completely unrelated error that just happens to have the same outcome. There may still be issues on our end. I know some of you have mentioned issues with non-Fanburst tracks, and I would like to tackle those issues if I can.

Excellent news Phil.

Woot!! That's fantastic news!

Had the jukebox looping in Chrome for around 90 minutes now with dev tools open and nary an error message in sight. Seems your Fanburst contact does good work! Thanks for getting this taken care of; been kind of a marathon.

I think it's been fixed. I've had music running for more than 2 or 3 hours and no more pauses. The errors are a lot less prominent too. Great job on this! C:

Tested for 20 hours in game. No problems what so ever. Thanks a lot! :)&nbsp;

I, too, have had no problems using the same reproduction path as before. Kudos.

Dammit. Now I'm getting the Content Length Mismatch error again. I'm gonna see if restarting my computer or clearing my cache helps at all -- maybe the fix somehow didn't affect me or something? I really don't know.

I get the error too, but that doesn't seem to stop the music. I'll get it once or twice, but the music doesn't stop. My assumption is the content mismatch error is unrelated.

No, it was stopping the music for me. That said, restarting the computer and clearing the cache seems to have done it, in that it's been running error-free for the past four hours, so hopefully all's well after all.