I am new to Squid proxy, i was able to configure squid in my windows 7 and work as proxy server to talk to outside world. Now i wanted to try to use squid as cascading proxy. and use fiddler to talk to out side world. Have anyone tried this before? Any help will be very useful.
Found the solution we just need to change "cache_peer 127.0.0.1 parent 8888 0 proxy-only default" to what ever port and ip we want to forward to. and i worked like a charm
Related
Using the latest version of Testcafe...
I'm behind a corporate proxy. Using --proxy myproxy:proxyport works fine. but when I try to use localhost, it continually responds with service not available. I have now added --proxy-bypass localhost:8080. But that has the same result.
Has anyone else experienced issues with Testcafe behind a corporate proxy -- and using localhost?
It is likely that localhost:8080 is incorrect. You need to set up your own port here.
In addition, you can simply use the following record:
--proxy-bypass localhost
In this case, all localhosts will be ignored regardless of the port.
I have a corporate proxy using Squid and kerberos for authentication, the proxy is configured for standard use, I.E allow http, https, a few others and block everything else. Now, there are many applications that support basic proxy authentication, but do not support Kerberos based authentication and many others that connect directly to the internet. I used Proxifier before the upgrade to kerberos to make my applications use the proxy, but I cannot do so now. I then installed an application called PX to create a proxy that connects to kerberos, but the proxy it creates is a simple HTTP Proxy and proxifier doesn't work correctly with it. Anyone has a setup for a situation like this?. I use Windows 10 and I obviously don't have access to the server where squid is configured. The application I need to connect to the internet uses standard https ports, it's not a torrent application nor anything that uses the ports blocked by squid. Thanks in advance.
Ok, for this particular case I've found the following setup to solve 99% of my problems.
First get Px here https://github.com/genotrance/px
Next get Fiddler: http://www.getfiddler.com/dl/Fiddler4BetaSetup.exe
Configure PX with your user and your domain and run it. By default it creates a running proxy on 127.0.0.1:3128
Configure your sistem proxy to use the proxy supplied by PX.
Execute fiddler, it should create ANOTHER proxy at 127.0.0.1:8888
Use this proxy in your apps. Proxifier should work as well.
Why use fiddler and not the direct 127.0.0.1:3128?, PX creates a pure http proxy and fiddler allows to tunnel https and connect request through it.
Any requests will pass through fiddler which will redirect them to the PX proxy which will redirect them to the squid proxy (So expect very slow speeds).
In the end since you're just redirecting your apps towards your proxy, if your proxy bans using regex expressions or direct IP connections some apps will NOT work, and in these cases using TOR or a VPN is the only real solution. Hope it helps someone avoid all the headaches I went through.
We're having a weird problem at work and I'm hoping someone here can give me some ideas on how to troubleshoot it.
The problem is that I cannot make websocket connections from my Kubuntu 13.10 workstation. I've tried from both Chrome and Firefox. I'm behind a proxy and first I thought that must be the reason. However, I got some coworkers to try to connect to the same websocket echo demo and all of them were able to, except one. He was the only one running Ubuntu (same as me), the others were on Mac, Windows and even one on RedHat! Theirs all worked fine.
Ok, so now for the really weird part. I created and ran a virtual machine on my workstation (the one that couldn't connect). The VM is a Lubuntu 13.10 and what do you know, the darn thing establishes a websocket connection just fine!
So any ideas on how to troubleshoot this or even some suggestions for solutions would be very much appreciated.
Ugh... well that one was dumb.
So it turns out that in Linux you can check a checkbox in your Network Proxy settings (the system settings) that will use the same proxy for all protocols.
Yeah... don't do that!
Unless, that is, your proxy server supports SOCKS as well as HTTP/HTTPS/FTP (highly unlikely).
It turns out that if you check that checkbox, your proxy server will be registered as a SOCKS proxy and for some reason, websocket connections in both Chrome and Firefox will want to use that. So your HTTP proxy will end up getting a bunch of weird SOCKS handshakes that it doesn't understand and any websocket connection will fail.
This was tested on both Ubuntu and Kubuntu and the "problem" exists on both.
TL;DR; Don't check the "Use this proxy server for all protocols" checkbox unless your proxy server supports the SOCKS protocol. Instead, manually fill in the same server for the different protocols (http, https and ftp) but leave the socks protocol empty (or point to an actual socks proxy server).
My webhosting company serves up Control Panel on a funky port number (20000 or something). This port is blocked from work, so I cannot access Control Panel during the day (in case of emergency).
Is it possible, and is there an easy way to run a simple proxy on a VPS so I can browse to the VPS on port 80 and have it talk to the Control Panel machine on the funky port 20000?
Any suggestions are helpful!
Thanks,
Rob
Just start a SSH-forward:
ssh -L 8080:localhost:20000 user#yourhost
You can access your config interface using http://localhost:8080
You can create such a tunnel using Putty on Windows, too. http://oldsite.precedence.co.uk/nc/putty.html
I would like to set up a proxy server on Fedora Core 4. Any idea of which ones might be easy to set up? I would like to connect through that server and receive an IP address from my ISP, since I have IP-address filtering on my apache server.
Squid is an option, but I'm not sure how easy or hard it is to set up.
Thanks.
if you're familiar enough with apache it may be easier to set that up as a proxy (mod_proxy). squid is probably more robust though if you want a dedicated proxy.