fiddler proxy ip doesn't work but localhost worked - fiddler

After setup my fiddler proxy,
I went to localhost:8888 and it was working fine, and it is shows
Fiddler Echo Service
But when I use IP 127.0.0.1:8888 or 127.0.0.2:8888, it doesn't work.

Use netstat -ab, find 8888 in netstat report.
May be you use ipv6 ([::1]:8888). And [::1]:8888 == localhost:8888.
What is Fiddler Echo Service?

Related

Issue getting my web server to work from external devices

I am attempting to set up an apache2 web server on my raspberry pi. I am able to connect to it by doing http://localhost:8080 (8080 because my router blocks port 80). Although when I do http://my.pub.lic.ip:8080 the connection times out. I set up port forwarding so that requests going to my router on port 8080 go to my raspberry pi on port 8080. This does not seem to work but I'm also not sure if the port forwarding is the cause or if it is something else. Any suggestions?
Is your web server configured to listen on the network interface besides localhost?
https://httpd.apache.org/docs/2.4/bind.html
For example, to make the server accept connections on both port 80 and port 8000, on all interfaces, use:
Listen 80
Listen 8000
To make the server accept connections on port 80 for one interface, and port 8000 on another, use
Listen 192.0.2.1:80
Listen 192.0.2.5:8000
You can try using nmap by finding your router's public IP and on the raspberry pi type nmap my.pub.lic.ip This will show you what services are actually being published to the world. This gives more insight to the problem.
I got the web server up and running although for some reason it appears that my isp would only allow it to be hosted securely (as an https page)(I'm not sure if that's the right way to phrase it). To achieve this for free, I used cloudflare's ssl service. A tutorial to set it up for apache2 can be found here

Redirect to url using squid and squidGaurd

Trying to redirect a url to other using squidGaurd, its not working, can anybody help me. I'm using Ubuntu 16.04
Usecase: the squid is to redirect to http://localhost:3000 for www.abc.com
and works normal for all other urls. Tried many things on internet, not working for me. can Somebody help with some good tutorial or example?
Tarun,
The squidGuard redirection URL should be a valid IP address or FQDN accessible to the clients. In your case traffic may be correctly be correctly redirected to URL http://localhost:3000, but for the clients localhost points to its loopback IP address.
In this case suppose you have opened the URL www.abc.com on your machine, after the request hits Proxy Server your browser is redirected to http://localhost:3000 so effectively to port 3000 on your machine. Since your machine is not listening on port 3000 it will look like the URL redirection is not working. Please use the IP address or FQDN of the proxy host in place of localhost and it should work.
Shahnawaz

Is there any public PeerServer over HTTPS?

I have a simple web application using peerjs here: https://github.com/chakradarraju/bingo. I was planning to use github.io to put up a demo, and github.io will be served only in HTTPS, the default PeerServer that is used by the peerjs library doesn't support HTTPS.
Is there any public HTTPS PeerServer that I can use?
The simple answer to this is no. It's unfortunate that the browsers recently disallowed http for any address except localhost.
One way to do it is set up an SSH port forward so that you can fool the browser into thinking it is talking to localhost. Ok for a demo, but not production. Here is some info (from https://www.ssh.com/ssh/tunneling/example)
In OpenSSH, remote port forwardings are specified using the -R option.
For example:
ssh -R 8080:localhost:80 public.example.com
This allows anyone on the remote server to connect to TCP port 8080 on
the remote server. The connection will then be tunneled back to the
client host, and the client then makes a TCP connection to port 80 on
localhost. Any other host name or IP address could be used instead of
localhost to specify the host to connect to.
Alternatively if you have your own web server, you can use Let's encrypt: https://letsencrypt.org/ to make it run https without needing to buy an SSL cert. Their tools are so good it's a five minute exersize to get https on your server.
Give a try to www
Is can create automatically valid certificates by using letsencrypt or self-signed.
https://go-www.com/post/how-it-works/
Usage of ./www:
-p port
Listen on port (default 8000)
-q quiet
quiet mode
-r root
Document root path (default ".")
-s your-domain.tld
https://your-domain.tld if "localhost", port can be other than 443
This issue can be resolved by setting options.secure to true as mentioned here.

All traffic forwarding using SSH tunnel in FreeBSD

I connect to my remote VPS like that:
ssh -f -C2qTnN -D 1080 username#xxx.xxx.xxx.xxx
Then setup Firefox proxy setting to SOCKS5 and 127.0.0.1:1080. That's work.
Now I try to redirect all traffic from my FreeBSD to localhost:1080, but I have no idea. Can you help?
If you want to redirect all traffic, do not use SOCKS5 proxy, but rather use -w option in ssh, which creates something like VPN connection and its own TUN device, which is more suitable for tunnelling system-wide traffic.
There are many examples on the internet, for example here. But this is really advanced use case.

Perl HTTP server message MyWebServer: you can connect to your server at http://localhos t:8080

The Perl HTTP::Server::Simple::CGI sample code prints the following message:
Perl HTTP server message MyWebServer: you can connect to your server at http:// localhos t:8080
Does this mean the http server only receive http request from localhost?
How can I make it accept http from any host?
By default it binds to all interfaces.
However if you want to see if it really is, then you can use netstat.
netstat -an | grep -i listen
will show you what ports your machine is listening to. You should see something like:
tcp4 0 0 *.8080 *.* LISTEN
(for all interfaces).
Thanks for the response. Actually the perl http service works for both in-bound and out-bound. There was no filter of (localhost). The problem was the I used a port, which is not http default 80. The port was blocked by my desktop's firewall.