Free Proxy

New SSL Proxies

 visit to my profile page to see all my blogs thanks :) http://www.blogger.com/profile/08427350034167098841

Because SSL websites are very hard to block, SSL Access to Vtunnel.com has always been popular, and now makes up about 50% of traffic to that site.

In case Vtunnel.com is blocked anyway, however, we now offer SSL access to several other web based proxies that we host:

https://www.btunnel.com

https://www.ctunnel.com

https://www.dtunnel.comhttps://www.vtunnel.com

https://www.ztunnel.com

https://www.polysolve.com

https://www.beatfiltering.com

Enjoy!

Update: All proxies now support Javascript

There were no weird problems when enabling javascript support, so I’ve decided to extend this to all the proxies hosted by freeproxies.org. Enjoy!

Vtunnel.com now supports Javascript!

It’s been a long time coming, but, now Vtunnel.com supports javascript.

As some of you may know, I’ve been at the forefront of the proxy industry, starting with a base of CGI Proxy, and working from there to add advanced features that improve the user experience. Unfortunately, some of these features have been at odds with implementing the javascript support that comes ready to go in CGI Proxy.

I have now come up with a solution that allows javascript to work, so long as html obfuscation is disabled. So, now you can enable javascripts on websites like myspace that benefit greatly from that, and, when javascripts are disabled, still enjoy the enhanced unblock protection allowed by html obfuscation.

If all goes well with javascript support in vtunnel, I will enable support on all the other proxies I host as well. Enjoy!

Dealing with a common issue in proxies: DNS resolution failure

Every now and then, I come across a person needing help with their DNS resolution for their proxy. More often than not, they don’t know that DNS is their problem, and it shows up as general poor performance, or unable to load proxied pages.

I have since resolved this on my servers, but I thought it would be useful to share that information with you. The idea behind this post came from one (of many similar) threads on the proxy.org forum:http://proxy.org/forum/1179669925.html

I run a few proxies and I see that I have a problem with the loading time. It takes around 25seconds just to load google.

I have my apache optimized and also noticed that my other website and non-proxy surfing are fast.

But the proxy surfing is very slow. The server load is fairly low at around 0.50, so I don’t think this could be due to excessive load.

In a situation like this, you should look to your DNS resolvers first.

The key points of interest are:

1.       When site finally starts loading, it does so quickly.

2.       Your site’s homepage loads very quickly, but “in proxy” pages do not.

3.       Server is not under heavy load but goes very slow.

4.       You’ve taken other appropriate steps to optimize your server.

The trick here is to look at your /etc/resolv.conf file.

This file has a list of the DNS resolvers your server will use, in order. In the situation above, chances are your first resolver is bad, and all requests have to time out on that resolver before it tries another one. Eventually it finds a working resolver, and you’re in business, but meanwhile everything goes slowly.

Your resolv.conf file should look like this:

nameserver 127.0.0.1

nameserver 66.90.68.25

nameserver 66.90.68.26

nameserver 66.90.68.15

nameserver 66.90.68.16

If there’s other stuff in there, it may be causing you problems. If you’re getting a “parse error” in your resolv.conf when you do the nslookup, see the original thread for a way to fix that.