Web player not working in Chrome

Reply

Web player not working in Chrome

cashmore1990
Newbie

The web player stopped working in Chrome for me today. Looks like Spotify are trying to load insecure content whilst on HTTPS so Chrome is blocking everything.

 

http://grab.by/v8FY

43 Replies

user-removed
Not applicable

Thanks for information. It will help to solve problem.

tsourapas
Newbie

Same problem, but because of doubleclick ads :

 

[blocked] The page at 'https://play.spotify.com/user/11131337430' was loaded over HTTPS, but ran insecure content from 'http://ad.doubleclick.net/adj/N2520.1804341.SPOTIFY.COM/B8039078.2;sz=800x235;ord=1395008919365?': this content should also be loaded over HTTPS.

 

el_vecino
Casual Listener

Something similar happening to me now.

 

Yesterday it worked ok but today when I try to enter to the website it shows a blank page with something similar to buttons and nothing happens.

 

Any solution?

 

spotify_error.png

el_vecino
Casual Listener

now it works again :S

javitron8
Newbie

i'm with the same problem

 

erro.png

Badawy
Newbie

Web player right now not working with me at all "This webpage is not available"

Somtime stuck at Connecting message and somtime not working at all

Peter__
Community Legend
Those errors appear to be coming from edgekey who I assume host part of the web player. Hopefully the web guys will pick up on this pretty sharpish!

Peter
Spotify Community Mentor and Troubleshooter

Spotify Last.FM Twitter LinkedIn Meet Peter Rock Star Jam 2014


If this post was helpful, please add kudos below!

immacatandafang
Casual Listener

For me, when my Spotify won't load on Chrome, it's the same problem people had with Safari. It'll load the page, but when I click play on a song, it won't play. Tried multiple songs. Help please!

immacatandafang
Casual Listener

By the way, this started when I downloaded this one song by Tryhardninja, it's strange, almost like it was a virus song.

Celtic_Monkey
Casual Listener

Guys - I have chrome Version 43.0.2357.132 (64-bit) installed on Centos 7 which itself is fully patched & up-to-date.

 

The web player seems to have stopped working over the last couple of days.

 

I can access the player and navigate, even click on the play button but it just loops back to the playlist.

 

Any help appreciated.

MidnightJava
Casual Listener

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

 

I tried all the obvious solutions. Cleared all browser data, launched in incognito, turned off all ad blockers, rebooted system. The fatal errors in the web console seem to be the indicator of the problem. Unencrypted content being loaded over https and some https sites returning ERR_CONNECTION_REFUSED. Seems like the server is failing at web hosting 101

 

So out of the blue, I cannot play any spotify music on any browser from any system. This seems to be a severe problem. I wish spotify would at least tell us that they're working on it. I'm a free user, so I can't really complain. 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.

gaufqwi
Newbie

Same issue, same time frame. Premium user, Fedora linux, Firefox and Chrome both not working. Android client on phone is fine.

lisazcollier
Newbie

Yes.  Very serious issue.

 

As of a few days ago, the web player has stopped working completely in at least Firefox and Chrome.

 

I was using at work via proxy.  Disabled proxy.  Still doesn't work.

 

I tried updating flash, taking flash back a release, etc.

 

Tried at home on both mac and pc with firefox and chrome on each.

 

Just tried creatin new account, and all same problems.

 

Will not play at all, and extrememly sluggish when all oother pages, apps on same computer are fine.

MidnightJava
Casual Listener

I'm pretty sure this is not a rendering issue, based on what I see in the web console. If that's correct, then all the re-installing and trying different browsers on different OSs will not help. I mentioned above that the server was trying to load insecure content over https. 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. 

However, the other error I reported (ERR_CONNECTION_REFUSED) is still occuring, for URLs that look like this: https://gzsrnavhli.spotilocal.com:4379/service/version.json?service=remote

 

That seems to be required content, and there's nothing we can do on our clients to make it work. 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. If there are any spotify people reading this, perhaps you can pass on the following observations to your web team.

 

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 gzsrnavhli.spotilocal.com 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. 200 or 304). 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. Perhaps the server is not configured properly for CORS requests at the randomized URLs. Status code 0 is a general error code, meaning an undefined error occured. 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.

EDIT: I attached a HAR-encoded capture of the web session to help you troubleshoot the problem. Search on "Status": 0 to find 30 instances of a failed request.

 

MidnightJava
Casual Listener

Well here's an interesting data point. It works fine on OSX, with Chrome and Firefox. I tested it on my MacBook Pro on the same network—behind the same router—as the Ubuntu system that was failing.

 

I get the same failures as described above (can't load insecure scripts and ERR_CONNECTION_REFUSED), so apparently that content is not necessary, and those failures are a red herring.

 

Maybe I was wrong about it not being a rendering issue. I have no idea why it's working in OSX

 

EDIT: I tried Firefox and Chrome in CentOS 7.1 in a VM running on my Macbook Pro, on which Chrome works when running directly. As expected, it still failed when running on CentOS in the VM. On the Mac and in the CentOS VM, Chrome version 45.0.2454-85 is running, so the OS seems to be the difference.

MidnightJava
Casual Listener

This started working for everyone in my office a few minutes ago. I assume Spotify fixed something on their site. FWIW I still get the web console errors mentioned above, with the player working properly.

blackbat24
Newbie

still not working on chromium 37.0.2062.120 + Ubuntu 12.04 (281580) (64-bit)

 

works on firefox, though

xarragon
Newbie

Spotify Web Player has been broken on debian AMD64 stable's Iceweasel/Firefox version 38.3.0 for more than a month. In the web console the following error messages are shown:

Use of getAttributeNode() is deprecated. Use getAttribute() instead. mootools-core-1.4.5.js:280:0
InvalidStateError: A mutation operation was attempted on a database that did not allow mutations. spotify.web.client.js:132:0
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://wnbcbmncyh.spotilocal.com:4370/service/version.json?service=remote. (Reason: CORS request failed). <unknown>
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://wnbcbmncyh.spotilocal.com:4371/service/version.json?service=remote. (Reason: CORS request failed). <unknown>
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://wnbcbmncyh.spotilocal.com:4372/service/version.json?service=remote. (Reason: CORS request failed). <unknown>
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://wnbcbmncyh.spotilocal.com:4373/service/version.json?service=remote. (Reason: CORS request failed). <unknown>
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://wnbcbmncyh.spotilocal.com:4374/service/version.json?service=remote. (Reason: CORS request failed). <unknown>
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://wnbcbmncyh.spotilocal.com:4375/service/version.json?service=remote. (Reason: CORS request failed). <unknown>
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://wnbcbmncyh.spotilocal.com:4376/service/version.json?service=remote. (Reason: CORS request failed). <unknown>
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://wnbcbmncyh.spotilocal.com:4377/service/version.json?service=remote. (Reason: CORS request failed). <unknown>
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://wnbcbmncyh.spotilocal.com:4378/service/version.json?service=remote. (Reason: CORS request failed). <unknown>
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://wnbcbmncyh.spotilocal.com:4379/service/version.json?service=remote. (Reason: CORS request failed).

It works in Chromium with the pepperflash plugin but shows warnings about loading insecure resources, just as the original poster said. I know Firefox is stricter than most browsers when it comes to HTTPS which might explain this. Still, make it work on all browsers, Spotify. This is not the year 2002 when it was OK to only support IE6.

boyer_moore
Newbie

Player hasn't worked at all today and worked only episodically yesterday. 

SUGGESTED POSTS