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
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
I have mqtt broker by ip
mqtt://xxx.xxx.xxx.xxx:8888/
I have a web site
http://mywebsite.com/
Now, I want to make like this
mqtt://mywebsite.com:8888/
If it would be like this still can:
mqtt://iot.publicwebsite.com:8888/ FORWARDFROM-> http://localhost:8888/
OR
mqtt://iot.publicwebsite.com:8888/ FORWARDFROM-> http://xxx.xxx.xxx.xxx:8888/
Depending on if you are using Native MQTT or MQTT over Websockers you have 2 choices
Set up port forwarding on your public facing machine. This means configuring the firewall to take any traffic that arrives on port 8888 and forwarding it to the broker machine and doing the reverse with any response traffic. Assuming you are on Windows then you would use the netsh command. See this question for details. This should work for both Native MQTT and MQTT over Websockets. If you are already using port forwarding from your router to the machine running ISS then you need to set up the port forwarding to the broker in the router, not the Windows machine.
If you are using MQTT over Websockets then you can configure ISS to act as a reverse proxy. This question explains how to do that.
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
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.
I would like to be able to use my web server as a Usenet 'proxy', how would I configure iptables to forward the packets correctly?
My Usenet client will connect to my web server and the web server would make the connection to usenet.
Thanks,
Luke.
I think what you really should be using is an ssh tunnel, not a proxy. It will do what you want (bounce traffic between your webserver when you want to connect to an nntp server) without installing any special software on your webserver. Iptables isn't really going to help you here.
http://www.rzg.mpg.de/networkservices/ssh-tunnelling-port-forwarding