SPOTIFY WEB PLAYER NOT WORKING CHROME UPGRADE
SPOTIFY WEB PLAYER NOT WORKING CHROME CODE
SPOTIFY WEB PLAYER NOT WORKING CHROME FREE

I know Firefox is stricter than most browsers when it comes to HTTPS which might explain this. It works in Chromium with the pepperflash plugin but shows warnings about loading insecure resources, just as the original poster said. Ĭross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at. :132:0Ĭross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at. InvalidStateError: A mutation operation was attempted on a database that did not allow mutations. In the web console the following error messages are shown: Use of getAttributeNode() is deprecated. Spotify Web Player has been broken on debian AMD64 stable's Iceweasel/Firefox version 38.3.0 for more than a month. Search on 'Status': 0 to find 30 instances of a failed request. While it could have been caused by a number of things, an incorrectly configured CORS exchange is a popular cause of this problem in my experience.ĮDIT: I attached a HAR-encoded capture of the web session to help you troubleshoot the problem.

SPOTIFY WEB PLAYER NOT WORKING CHROME CODE

Status code 0 is a general error code, meaning an undefined error occured. Perhaps the server is not configured properly for CORS requests at the randomized URLs. These are CORS requests, and the Origin header is set properly in all requests (including the failed ones), and for all non-failing requests the server returns 'access-control-allow-origin':* to allow the request. In a given failure scenario, all requests to a certain URL with an apparently randomized string in the first segment of the URL (as in above) return status code 0 with no response header or content-just a graceful termination of the TCP connection-while all requests to other URLs return normal status codes (i.e. If there are any spotify people reading this, perhaps you can pass on the following observations to your web team. I looked at the response in the Network tab, and the server response is empty because the underlying transport carrying it is gracefully terminated as soon as the request is made. That seems to be required content, and there's nothing we can do on our clients to make it work. However, the other error I reported (ERR_CONNECTION_REFUSED) is still occuring, for URLs that look like this: I overrode this manually by right-clicking on the shield icon on the right side of the omnibar and selecting 'Load Unsafe Scripts' (do this at your own risk), and those errors now show as warnings and the insecure scritps are loaded. I mentioned above that the server was trying to load insecure content over https. If that's correct, then all the re-installing and trying different browsers on different OSs will not help. I'm pretty sure this is not a rendering issue, based on what I see in the web console.

SPOTIFY WEB PLAYER NOT WORKING CHROME UPGRADE

But I will say that I'm not inclined to upgrade to a paid account if this sort of thing is not acknowledged and eventually fixed.

SPOTIFY WEB PLAYER NOT WORKING CHROME FREE

I'm a free user, so I can't really complain. I wish spotify would at least tell us that they're working on it. So out of the blue, I cannot play any spotify music on any browser from any system. Seems like the server is failing at web hosting 101 Unencrypted content being loaded over https and some https sites returning ERR_CONNECTION_REFUSED. The fatal errors in the web console seem to be the indicator of the problem.

Cleared all browser data, launched in incognito, turned off all ad blockers, rebooted system.

And it fails from home also, so it's not a firewall issue. We don't block any sites frm our office we have a very relaxed working environment. Everyone in my office experienced the same problem beginning at the same time. It was working fine until a few days ago. It doesn't work for me in Firefox either, on CentOS or Ubuntu.

Spotify web player not working chrome