4

Fuckin damn it Google! I setup a transparent proxy and for some fucking reason Google home doesn't like that at all. I think I have a fix but it's a real fucking pain in the ass. I call your support people who I specifically tell that I'm running a fucking proxy and they tell me that I need to talk to their Google WiFi team. It has nothing Todo with my fucking wifi bitch. Its your price of shit price of crap hardware that doesn't like fucking proxies.

I'll update everyone what the fix is when I find it.

Btw, this is a HTTPS transparent proxy and HTTP transparent proxy running on my pFSense firewall box.

Comments
  • 0
    For anyone whos looking for a fix to an issue like this. You need to bypass the proxy for these destination addresses.

    (these are comma seperated in squid)

    64.18.0.0/20;64.233.160.0/19;66.102.0.0/20;66.249.80.0/20;72.14.192.0/18;74.125.0.0/16;108.177.8.0/21;173.194.0.0/16;207.126.144.0/20;209.85.128.0/17;216.58.192.0/19;216.239.32.0/19;172.217.0.0/19;108.177.96.0/19;2001:4860:4000::/36;2404:6800:4000::/36;2607:f8b0:4000::/36;2800:3f0:4000::/36;2a00:1450:4000::/36;2c0f:fb50:4000::/36;
  • 0
    Thanks for the tip.

    I have added in those ip addressed to my squid server in psfense and I have the devices showing up in spotify ect now. Only problem is I can not connect to them to cast.

    Your rant is the only post I have seen about the Google Assistant on transparent proxies.

    Have you any thoughts on how to get casting working?

    Cheers, Jeff
  • 1
    What i ended up doing was assigning static DHCP leases to all of my google home devices and bypassing the proxy for source IPs
  • 1
    Thank you for sharing your information. This is very important for me. I am constantly having problems with the proxy server. I have already decided to buy a new proxy for safe work on social networks.
Add Comment