I need to debug an issue on a remote computer on LAN. In past I have used fiddler to debug issues on IIS installed on local machine, wondering if Fiddler can be configured to act as a proxy to remote machine ?
Yes, fiddler proxies all requests by default when you turn it on. It don't care if you are going to localhost or farhost.com.
Fiddler hosts a proxy to monitor requests, just set the proxy on the remote server to point to the proxy listening settings from Fiddler's about box.
Related
I have a VPN that only connect through HTTPS on my browser with its extension. I'm using Windows 10 and I'm looking for a solution like Tor Browser that have a SOCKS5 proxy (127.0.0.1:9150) and other apps can use it to bypass censorship.
Is there any solution for Firefox, Chrome or any other browser that after connecting to VPN extension, other apps can use a SOCKS5 or HTTP proxy to connect through it?
I tried Proxifier and similar apps on Windows 10 and no luck. But official VPN browser extension and FoxyProxy work.
I tried different ISPs and I know my firewall is not the problem and VPN is connected on other ISPs.
VPN name: TorGuard
The best solution I found so far is to use v2rayA (https://v2raya.org/en/).
First you connect to your HTTPS proxy through this app and then you can use HTTP or SOCKS5 proxy that it gives you to connect other apps or use Proxifier (https://www.proxifier.com/download/) to tunnel all traffic.
P.S. The default address and port of v2rayA are:
HTTP 127.0.0.1:20171
SOCKS5 127.0.0.1:20170
On my machine, im hosting a node server that is listening on port 5000. Before setting up a forward proxy (squid), i was able to perform a GET on https://localhost:<port>. However, after setting up a forward proxy and setting the environmental variable http_proxy=<ip addr:port>, this GET request no longer works.
The error that shows up is: tunnelling socket could not be established, statusCode=503
Some additional information:
The proxy server works as I am able to connect to the internet via it.
Performing curl instead, on the https:localhost:5000/api works.
Am using request.js for the requests, using agentOptions to specify TLS protocols & ca cert.
I am hoping to understand how the traffic is now different after i add in a proxy. From my understanding, now we have to go through a sort of TLS CONNECT / tunnelling since to the proxy first, since its a HTTPS request, before coming back to my localhost. But in the case without the proxy, how is it that its working?
Any help would be greatly appreciated. Thanks!
you must add
export no_proxy='localhost,127.0.0.1'
the https work because you don't use proxy for https , you must set https_proxy='<tour_proxy>'
I am trying to configure a reverse proxy with IIS. HTTP/HTTPS connections are working. However I'm unable to set up a SSH connection.
I've already tried a port forwarding:
netsh interface portproxy add v4tov4 listenport=7999 connectaddress=Server.
It appears that Microsoft IIS does not support any form of SSH redirection/reverse proxying.
Do you have any idea how to establish a SSH connection with a Reverse Proxy?
ARR only support HTTP/HTTPS protocol it does not support any other protocol like SSH.
You could check Application Request Routing article for more detail.
Regards,
Jalpa
I have one windows server already running sharepoint on 80/443 and the site works correctly.
We're trying to add more functionality by installing NodeJS and Apache
I've set apache to listen on 8080 and the default website comes up.
Node is running on 3000 and I can access the explorer that way as well.
My questions come from this. The server has a complete certificate chain installed on it and https://:8080 comes up correctly, but I can't get the node stuff to work on https: Secondly it appears while I have proxy pass set up correctly within my httpd.conf, either something is wrong within that as if I goto the https://:8080 /api/and anything beyond that, I get 503 errors and the page can't be displayed.
I'm unsure what I'm doing incorrectly here as from reading the documentation on proxy module, it seems that everything is setup and configured correctly.
Netstat shows listening on 3000 and 8080 and 80/443 for my SharePoint farm.
I had to configure the ssl settings for the proxypass to use the IP address of the local machine. After doing that I was able to connect correctly.
This allowed for connecting on :3000 via telnet to the localmachine and allowed for explorer to be viewed with https://:8080 the correct way enforcing our certificates.
Is there way to set Proxy settings (route via proxy Server) for HazelcastClient to connect to remote cache server (which is behind a firwall)
Thanks
No since Hazelcast clients use an internally developed (even though open source), plain TCP protocol, there is no real proxy support. You might be able to use a SOCKS proxy though but this is not supported.
There's also a prototype to tunnel the protocol through a HTTPS session but same thing, not officially supported: https://github.com/noctarius/https-tunnel-openshift-hazelcast