"Something went wrong" after trying to connect Chromecast

[glimmer_kitty10]

Hi. I had my Chromecast working fine with no issues for almost a month. Yesterday I went to use it and when attempting to stream Netflix, it said "Unable to connect, try again later". I Got my friend to try and she had the same issue. So, I tried through the Google Home App, with no luck.

So, I deleted the Chromecast and factory reset it, and attempted to connect it the way I did the first time I set it up. It recognises the Chromecast, and the wifi network, but upon connecting to wifi, it says "connecting..." for a while, then goes to "connected" for about 5 seconds, and then the message "Something went wrong" pops up with the following details: 

"Your TV may be set up, but we could not communicate with it from your iPhone. Make sure that you have enabled local network access in your iPhone's privacy settings. Then try again."

I have tried factory resetting the Chromcast twice, updated the app, disconnected to wifi and reconnected, restarted my iPhone, and browsed the help page for advice.

Any advice is appreciated, thanks. 

[Leesherwin]

Same issue here

[Sandy05]

Apparently it’s an issue with google and their certificate authority. It’s a worldwide issue and they are working on fixing it

[nicolereidy]

Same here!! 

[Dominic7]

Same here in Germany

[Simon83]

Same here Australia 

[Mallah]

Same in Jordan 

[Ruud61]

Same in the Netherlands

[Pepet]

Jo tampoc puc autenticar  el meu chromecast desde Diumenge a la nit

[naniSG]

same in Singapore! I wasted so much time trying to fix it 😓  and still not working

[Jakubs]

Same in Czech. Hope, they come with some solution

[Agnieszkas]

Same here in Poland 

[genys-lowvibe]

Same here ( Berlin), started yesterday around 10PM (CET)

[Eleani]

Same in Greece

[Jildert]

In Spain too

[kbrzw]

Same in Canada, since Friday afternoon (March 8th 2025)

[Agnieszkas]

Any News when its going to be fixed?

[Sandy05]

I read it could be days possibly weeks away from being fixed

[AK406]

Same issue from past few days. Didn’t expect this from google. They are not able to fix it. 

[Jakubs]

I found some description of the issue here. There is also workaround, but i haven't tried yet.