Instagram images are not loading when connected to the WiFi

[plums]

Recently I have not been able to use Instagram while connected to our Nest WiFi. Images, videos, and message data just doesn't load at all. The issue is resolved when turning off WiFi or connecting to another type of router. 

We are also having an issue with our Google Nest Hub and Google Nest Mini during the same time frame - all the devices say "Sorry, something went wrong" after every command.

Everything was working fine until a few weeks ago - some suggested to turn off IPv6 but it has been on for almost 2 years now without an issue.

[Jeff]

Hi, plums.

Sorry for the issues you're having. That all looks to be quite frustrating to deal with. Let's work this out and get you back to 100% functionality.

The IPv6 suggestion is a good one. You don't actually need to totally disable it, just try toggling it off, and re-enabling it. We have actually seen that simple step work out for lots of users. As for the Assistant issues, that was identified as a known bug and a fix should be hitting soon for that.

In addition to the IPv6 step, have you also tried using Google's DNS servers? Let me know about that and if the IPv6 toggle works.

Thanks.

[Jeff]

Hi, plums.
I just wanted to check in real fast to see if you saw my reply and to find out if you still needed any help on this. If you're still needing assistance, please just let me know and I'll be happy to continue helping.
Thanks.

[plums]

Earlier this week I turned off IPv6 and turned it back on (after several minutes) and since then everything has been working fine. I'll give it a few more days, but so far so good. 

[Jeff]

That's great, plums. Let's give it a little more time to see if it remains stable. If anything changes, let me know.

Thanks.

[Jeff]

Hi again, plums.

I just wanted to follow up real fast to see if things were still running smoothly for you or to see if you've had any issues.

Thanks,

- Jeff

[plums]

Hey Jeff,

Everything seemed to be going well until a few days ago - Twitter wasn't loading any images and some other apps weren't functioning correctly while connected to WiFi. I had to power cycle my Google Nest as well as turn off/on IPv6 again.

It's working fine now, but I never had to do this until recently (same device and settings for over a year) so it's frustrating. 

[Jeff]

Thanks for letting me know, plums. That's definitely frustrating and confusing. We'll keep looking into the IPv6 stuff on our end. I'm happy you have a workaround for the time being, but we'll work on a permanent fix for this.

Thanks,

- Jeff

[Jeff]

Hi again, plums.

I'm just letting you know I haven't forgotten about this, I just still don't have any answers about the IPv6 issues. I'm hoping to learn more soon. Have you noticed any changes in your end or any new patterns with the issue?

Thanks,

- Jeff

[plums]

Hey Jeff,

Everything is pretty much the same since I first opened the issue. I went through a multi-week stretch without any issues, but just a couple days ago I was having issues seeing images on both Instagram and Twitter, while the "Sorry, something went wrong." issue reappeared on my Nest devices. It seems when the Nest devices start having issues, they impact the rest of the WiFi network which causes images on my apps to stop loading. Really strange.

I went ahead and toggled IPv6 on/off again as well as running a network restart on my Nest WiFi. Everything works again after that. 

[Jeff]

Thanks for updating me, plums.

As I work with our teams on this, your info is quite helpful to help paint that picture. Hopefully I can find more soon on this.

Thanks,

- Jeff

[Jeff]

I'm happy you got that worked out, pwilson. Also, I appreciate you letting us know what worked of you. Hopefully that helps others as well.

Thanks,

- Jeff

[Jeff]

Hi all,

As a quick follow up, I wanted to see if anyone was still struggling with this. pwilson shared a process that worked for them, so hopefully it was successful for others too. If you're still seeing this issue, please let me know.

Thanks,

Jeff

[plums]

Hey Jeff, thanks for staying in active in this thread. I had the issue happen once again on Saturday (3 days ago). I was in a rush so didn't do the hard reset fix - but I will do it next time this happens (or I may do it manually before it happens). I will follow up whenever that happens!

[Jeff]

Thanks for checking in, plums.

Let's keep working on it. Apologies if I already asked, but did we rule out the possibility of a VPN or a traffic filter being in place? Do you use either of those types of services?

Thanks,

Jeff

[plums]

Nope - I am not using a VPN or a traffic filter. 

The Nest's WiFi single hardwire port is going to a switch which then handles a few of my hard connections (PC, Samsung SmartThings, Hue, and Chromecast). The issue only impacts WiFi devices (mobile phones - only my Android phone, not our iPhone) and our Nest devices (display hub and mini).

[Jeff]

Thanks for clarifying, plums. Also, with that info I think we can definitely narrow it down to being a WiFi traffic issue. I'll need to continue looking into this, but I appreciate the extra info.

Thanks,

Jeff

[Princesss]

Hi everyone,

We just want to check if you have seen our response on the previous post? Let us know if you have additional questions, otherwise we'll be locking the thread.
 

Best,

Princess

[Princesss]

Hi everyone,

Due to inactivity, I'll go ahead and lock this thread in 24 hours. Feel free to start a new thread if you need assistance with your Google speakers and we'd be glad to assist you further.

Best,

Princess

[pwilson]

I had the same issue - photos wouldn't load in apps, videos wouldn't load on peloton, nest/chromecast devices would be flakey. Restarting the network fixed everything for about 30 minutes. Very frustrating.

I tried changing the ISP settings but that didn't help.

I fixed this by doing a factory reset (from inside the home app which resets the router and the points) and then re-setting up the router and each of the wifi-points. So far it seems to be fixed.

My guess is Google released an update for this and some existing settings or metadata are incompatible with the updated software.

I hope this works for you.