Proxy Setup For Google

sharky8888

Newbie
Joined
Jul 31, 2013
Messages
2
Reaction score
0
Here is how I'm setting up my dedicated proxies that I get for a monthly fee:

Open Firefox, go to settings and check manual proxy configuration.
Enter my ip in the HTTP Proxy field, the enter the port.
I then clear history, close browser, re-open browser, enter user and pass,
and off I go.

Am I doing this correctly?

Can Google see through this?

Is their another choice when using my dedicated proxies?

I'm not sure what the difference is between HTTP Proxy,
and SSL proxy, or socks proxy, which is best for Google?

Thanks for any advice.
 
u are doing the right way i also do that only!
 
Why are you using them on firefox? I never use proxies for anything other than for seo tools?
 
Duude, i do same but proxy does not work for me google for some reasons see my real ip but when i go to ther sites that shows IP they see my proxy Ip. Can somebody give any tips how to fix it? I used ccleaner nothing helps, google see my real ip :(
 
Easiest way to tell what ip Google see is to literally go to google.com and type "what is my ip" and right above all the search results it'll show you the ip that is supposed to be your "public" ip. GangsterWilly, there's a couple of reasons that you could be having that problem, what kind of proxies are you using? If you're using public open proxies that you scanned then there's a good chance they were L3 transparent and therefore leaking your ip. If you're using private proxies you should probably contact whoever you bought them from and ask them if there's something you're missing that they can help you with.
 
Tutorial - How to set up a private proxy in mozilla firefox

goodle is using .sol flash cookies to trace you down, before using a proxy, you have to manually erase .sol flash cookies from macromedia folder, clear cache, history and cookies ...
 
Last edited by a moderator:
Thanks for the tutorial! I wasn't checking the box "use for all protocols"

Thanks again!
 
Try to switch to IE, sometimes the problem itself with the browser, not the proxy
 
Back
Top