Yo, I'm getting a no proxies warning on Ozpol using Chrome.

And no I'm not using a proxy.

Gordon wrote on Jul 24^th, 2019 at 6:33pm:

Yo, I'm getting a no proxies warning on Ozpol using Chrome. And no I'm not using a proxy.

So...what's your problem?  You are posting.

Gordon wrote on Jul 24^th, 2019 at 6:33pm:

Yo, I'm getting a no proxies warning on Ozpol using Chrome. And no I'm not using a proxy.

Can you check your settings and make sure?

https://www.quora.com/How-do-I-turn-off-proxy-settings-in-Chrome-for-Android

Is it when you are using a wifi connection or the phone's data connection?

You username has been whitelisted in case.

Setanta wrote on Jul 24^th, 2019 at 7:33pm:

Gordon wrote on Jul 24th, 2019 at 6:33pm: Yo, I'm getting a no proxies warning on Ozpol using Chrome. And no I'm not using a proxy. Can you check your settings and make sure? https://www.quora.com/How-do-I-turn-off-proxy-settings-in-Chrome-for-Android Is it when you are using a wifi connection or the phone's data connection? You username has been whitelisted in case.

It's happening for both mobile and wifi.

That guide is a few years old and there is no proxy settings inside Chrome android now.

I checked the proxy settings in both wifi/mobile and all proxy settings are nil.

All fine my wife's phone, older android and software and my PC is OK.

It just started today, weird!

I'll install firefox and see what happens.

Gordon, can you get on your phone with chrome and go to https://www.whatismyip.com/ and PM me the results?

Setanta wrote on Jul 25^th, 2019 at 10:24am:

Gordon, can you get on your phone with chrome and go to https://www.whatismyip.com/ and PM me the results?

All fixed now. I rolled chrome back to factory setting then downloaded the update again.

I wonder what got it's panties in a twist.

Gordon wrote on Jul 25^th, 2019 at 11:02am:

Setanta wrote on Jul 25th, 2019 at 10:24am: Gordon, can you get on your phone with chrome and go to https://www.whatismyip.com/ and PM me the results? All fixed now. I rolled chrome back to factory setting then downloaded the update again. I wonder what got it's panties in a twist.

I whitelisted your user name. I'll remove that and tell me how you go.

I'm on chrome on Android sometimes. Works fine for me

Spot

I've also found this google-proxy-used-for-chromes-mobile-data-compression/


Quote:

Claiming a saving on data usage of 50 percent, Google has rolled out a new data compression feature in its Chrome for Mobile app that is available for Android and iOS. To enable the new feature, all the user needs to do is head over to the Settings menu, go into the Bandwidth Management section, and select "Reduce data usage".

If your phone is blocked again after me removing your username from the whitelist it may be this. I might be able to work around it if it is.

The data saving mode is now called "Lite mode" in settings.

Problem should be solved for everyone with chrome data saving/lite mode on now.

Setanta wrote on Jul 25^th, 2019 at 3:40pm:

I've also found this google-proxy-used-for-chromes-mobile-data-compression/ Quote: Claiming a saving on data usage of 50 percent, Google has rolled out a new data compression feature in its Chrome for Mobile app that is available for Android and iOS. To enable the new feature, all the user needs to do is head over to the Settings menu, go into the Bandwidth Management section, and select "Reduce data usage". If your phone is blocked again after me removing your username from the whitelist it may be this. I might be able to work around it if it is. The data saving mode is now called "Lite mode" in settings.

Must have been a Chrome setting, because while Chrome was getting the error I tried Firefox and it was fine. After I un/reinstalled Chrome it was fine right away.

Gordon wrote on Jul 25^th, 2019 at 5:13pm:

Setanta wrote on Jul 25th, 2019 at 3:40pm: I've also found this google-proxy-used-for-chromes-mobile-data-compression/ Quote: Claiming a saving on data usage of 50 percent, Google has rolled out a new data compression feature in its Chrome for Mobile app that is available for Android and iOS. To enable the new feature, all the user needs to do is head over to the Settings menu, go into the Bandwidth Management section, and select "Reduce data usage". If your phone is blocked again after me removing your username from the whitelist it may be this. I might be able to work around it if it is. The data saving mode is now called "Lite mode" in settings. Must have been a Chrome setting, because while Chrome was getting the error I tried Firefox and it was fine. After I un/reinstalled Chrome it was fine right away.

That's because at some stage you or it turned on lite mode. Safe to turn back on now I'm pretty sure, it'll save approx 50% data on http, https is not touched.

Setanta wrote on Jul 25^th, 2019 at 5:31pm:

Gordon wrote on Jul 25th, 2019 at 5:13pm: Setanta wrote on Jul 25th, 2019 at 3:40pm: I've also found this google-proxy-used-for-chromes-mobile-data-compression/ Quote: Claiming a saving on data usage of 50 percent, Google has rolled out a new data compression feature in its Chrome for Mobile app that is available for Android and iOS. To enable the new feature, all the user needs to do is head over to the Settings menu, go into the Bandwidth Management section, and select "Reduce data usage". If your phone is blocked again after me removing your username from the whitelist it may be this. I might be able to work around it if it is. The data saving mode is now called "Lite mode" in settings. Must have been a Chrome setting, because while Chrome was getting the error I tried Firefox and it was fine. After I un/reinstalled Chrome it was fine right away. That's because at some stage you or it turned on lite mode. Safe to turn back on now I'm pretty sure, it'll save approx 50% data on http, https is not touched.

Ah. New phone too so I was wondering if it was the phone or the anti-proxy settings :)

Gordon wrote on Jul 25^th, 2019 at 5:42pm:

Setanta wrote on Jul 25th, 2019 at 5:31pm: Gordon wrote on Jul 25th, 2019 at 5:13pm: Setanta wrote on Jul 25th, 2019 at 3:40pm: I've also found this google-proxy-used-for-chromes-mobile-data-compression/ Quote: Claiming a saving on data usage of 50 percent, Google has rolled out a new data compression feature in its Chrome for Mobile app that is available for Android and iOS. To enable the new feature, all the user needs to do is head over to the Settings menu, go into the Bandwidth Management section, and select "Reduce data usage". If your phone is blocked again after me removing your username from the whitelist it may be this. I might be able to work around it if it is. The data saving mode is now called "Lite mode" in settings. Must have been a Chrome setting, because while Chrome was getting the error I tried Firefox and it was fine. After I un/reinstalled Chrome it was fine right away. That's because at some stage you or it turned on lite mode. Safe to turn back on now I'm pretty sure, it'll save approx 50% data on http, https is not touched. Ah. New phone too so I was wondering if it was the phone or the anti-proxy settings :)

all this bullshit because Aussie can't sort his poo out...

barryfromthebush wrote on Jul 25^th, 2019 at 6:54pm:

Gordon wrote on Jul 25th, 2019 at 5:42pm: Setanta wrote on Jul 25th, 2019 at 5:31pm: Gordon wrote on Jul 25th, 2019 at 5:13pm: Setanta wrote on Jul 25th, 2019 at 3:40pm: I've also found this google-proxy-used-for-chromes-mobile-data-compression/ Quote: Claiming a saving on data usage of 50 percent, Google has rolled out a new data compression feature in its Chrome for Mobile app that is available for Android and iOS. To enable the new feature, all the user needs to do is head over to the Settings menu, go into the Bandwidth Management section, and select "Reduce data usage". If your phone is blocked again after me removing your username from the whitelist it may be this. I might be able to work around it if it is. The data saving mode is now called "Lite mode" in settings. Must have been a Chrome setting, because while Chrome was getting the error I tried Firefox and it was fine. After I un/reinstalled Chrome it was fine right away. That's because at some stage you or it turned on lite mode. Safe to turn back on now I'm pretty sure, it'll save approx 50% data on http, https is not touched. Ah. New phone too so I was wondering if it was the phone or the anti-proxy settings :) all this bullshit because Aussie can't sort his poo out...

I prefer to read Aussies posts on my phone when I'm on the dunny dropping a massive turf to give me a fully immersive experience. Reading turds from a turd while smelling one  :)

barryfromthebush wrote on Jul 25^th, 2019 at 6:54pm:

Gordon wrote on Jul 25th, 2019 at 5:42pm: Setanta wrote on Jul 25th, 2019 at 5:31pm: Gordon wrote on Jul 25th, 2019 at 5:13pm: Setanta wrote on Jul 25th, 2019 at 3:40pm: I've also found this google-proxy-used-for-chromes-mobile-data-compression/ Quote: Claiming a saving on data usage of 50 percent, Google has rolled out a new data compression feature in its Chrome for Mobile app that is available for Android and iOS. To enable the new feature, all the user needs to do is head over to the Settings menu, go into the Bandwidth Management section, and select "Reduce data usage". If your phone is blocked again after me removing your username from the whitelist it may be this. I might be able to work around it if it is. The data saving mode is now called "Lite mode" in settings. Must have been a Chrome setting, because while Chrome was getting the error I tried Firefox and it was fine. After I un/reinstalled Chrome it was fine right away. That's because at some stage you or it turned on lite mode. Safe to turn back on now I'm pretty sure, it'll save approx 50% data on http, https is not touched. Ah. New phone too so I was wondering if it was the phone or the anti-proxy settings :) all this bullshit because Aussie can't sort his poo out...

There's two sides to this as far as I'm concerned. Aussie certainly makes himself unlikable to most people, he has few friends and that is IMO understandable. On the other hand just because you don't like him doesn't give you freedom to dox him and have no consequences. He's not innocent in the whole feud thing, he's done his fair share of being a dick. That does not mean he will be allowed to be doxxed, that is all on the doxxers head. It would be the same if it was vis versa. This measure is because of the doxxers and I've voiced my opinions on it, I don't like it at all. While we keep having these doxxers pissing on the forum, I'll do what I can to stop it.

Setanta wrote on Jul 25^th, 2019 at 7:46pm:

barryfromthebush wrote on Jul 25th, 2019 at 6:54pm: Gordon wrote on Jul 25th, 2019 at 5:42pm: Setanta wrote on Jul 25th, 2019 at 5:31pm: Gordon wrote on Jul 25th, 2019 at 5:13pm: Setanta wrote on Jul 25th, 2019 at 3:40pm: I've also found this google-proxy-used-for-chromes-mobile-data-compression/ Quote: Claiming a saving on data usage of 50 percent, Google has rolled out a new data compression feature in its Chrome for Mobile app that is available for Android and iOS. To enable the new feature, all the user needs to do is head over to the Settings menu, go into the Bandwidth Management section, and select "Reduce data usage". If your phone is blocked again after me removing your username from the whitelist it may be this. I might be able to work around it if it is. The data saving mode is now called "Lite mode" in settings. Must have been a Chrome setting, because while Chrome was getting the error I tried Firefox and it was fine. After I un/reinstalled Chrome it was fine right away. That's because at some stage you or it turned on lite mode. Safe to turn back on now I'm pretty sure, it'll save approx 50% data on http, https is not touched. Ah. New phone too so I was wondering if it was the phone or the anti-proxy settings :) all this bullshit because Aussie can't sort his poo out... There's two sides to this as far as I'm concerned. Aussie certainly makes himself unlikable to most people, he has few friends and that is IMO understandable. On the other hand just because you don't like him doesn't give you freedom to dox him and have no consequences. He's not innocent in the whole feud thing, he's done his fair share of being a dick. That does not mean he will be allowed to be doxxed, that is all on the doxxers head. It would be the same if it was vis versa. This measure is because of the doxxers and I've voiced my opinions on it, I don't like it at all. While we keep having these doxxers pissing on the forum, I'll do what I can to stop it.

Additional to the above, hes give us more than enough to work with, kid pinning, clit wondering,making mentally challenged strawberry pickers cry.  :)

I'm marking this issue resolved and moving it to tech speaking.