Announcements
The Spotify Stars Program: Celebrating Values Week!

Help Wizard

Step 1

NEXT STEP

[Windows 10] Web Player not loggin in

Solved!

[Windows 10] Web Player not loggin in

Plan

Free

Country

Italy

Device

Chrome

Operating System

WIndows 10

 

My Question or Issue

Couple of days I can't login anymore on Chrome Web Player, I get the Oops! Something went wrong, please try again or check out the help area.

 

Tried everything.

Reinstalling Chrome, Cleaning Cache, updating Chrome, reset network, change IP, no firewall, everything that you can imagine!

1.png

Reply

Accepted Solutions
Marked as solution

Hey!

Actually I understood what was the problem. Chrome updated their terms & conditions about cookies and stuff. Since I did not accept them, I think that Spotify web player felt it like an "ad blocker" and I got that message. After accepting it, it worked. Y

View solution in original post

9 Replies

Hey @Ilovetohelp234

 

Thanks for posting - we’re here to help!        
 

Could you confirm if you still experience this when opening the web player in a private/incognito window? This step makes sure you avoid issues with your browser's cache. If that doesn't do the trick try again in a different kind of browser.

 

It's also a good idea to try out the steps listed in this Spotify Answer. Give them a try and let us know the outcome. 

 

Hope this helps. Keep us posted. 

Hello!

Yeah I can confirm it doesn't work with incognito mode. 
I tried with Mozilla and Edge, and I keep on getting the same error.

I also did all the different things Spotify says, when I reset the router it works a while that get blocked again.

About the "hosts" trick, I really cannot find any address, it looks like I have the standard stuff there, this is what I find:

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost

 

Hi there @Ilovetohelp234,

 

Thank you for your reply and confirmation.

 

Do you use any VPN or secured internet connection?

We'll keep an eye out for your reply.

 

Cheers!

JeremyModerator
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Live, love, laugh and listen to music 🙂

I asked a friend of mine that is a developer to take a look at the problem, he's been playing around a bit and told me that in his opinion is server side,  screenshotted these two images for the post:

photo_2021-05-21_18-39-45.jpg

photo_2021-05-21_18-40-10.jpg

Hi again @Ilovetohelp234,

 

Thank you for your reply and for the screenshots.

 

We tried this from our end and it works as it should.

 

Can you let us confirm if you use any VPN or secured internet connection?

 

Keep us posted 🙂

Take care!

JeremyModerator
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Live, love, laugh and listen to music 🙂

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
Yeah confirmed straight line to fiber.

Hi again @Ilovetohelp234,

 

Thank you for your reply.

 

Can you try to log into the web player from a different device to see if the issue persist?

Note: The browsers currently supported are Chrome 45+, Edge 14+ Chrome 62+ and Safari 11+ on mobile.

 

We'll be on the lookout for your reply.

 

Cheers!

JeremyModerator
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Live, love, laugh and listen to music 🙂
Marked as solution

Hey!

Actually I understood what was the problem. Chrome updated their terms & conditions about cookies and stuff. Since I did not accept them, I think that Spotify web player felt it like an "ad blocker" and I got that message. After accepting it, it worked. Y

Hey @Ilovetohelp234,


Thanks for sharing what worked for you with the Community!

 

I'll mark your post as a solution so it's easier to see for other users 🙂

 

Cheers.

AlexModerator
Help others find this answer and click "Accept as Solution".
If you appreciate an answer, maybe give it a Like.
Are you new to the Community? Take a moment to introduce yourself!

Suggested posts