Tag Info

New answers tagged

0

Alright, so here's the solution I ended up going with, which works nicely. For the sake of a thorough answer, I will recap some quick details. Servers: ServerA - ubuntu 12.04 - internal static ip of 192.168.1.230 ServerB - ubuntu 14.04 - internal static ip of 192.168.1.235 I have a website on each server, one on 12.04 (with an older php install) that i ...


0

according to the ssh man page, ProxyCommand is the correct method the syntax being: ProxyCommand ssh -W %h:%p user@jumphost 2> /dev/null


0

You can use HAproxy to send requests to different backends based on the hostname using ACLs: https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#acl Example: acl is_host1 hdr(host) -i host1.example.com acl is_host2 hdr(host) -i host2.example.com use backend host1_backend if is_host1 use backend host2_backend if is_host2 That's just a ...


0

I believe this is the command you are looking for: netsh interface portproxy add v4tov4 listenport=5555 listenaddress=192.168.0.1 connectport=3389 connectaddress=192.168.0.2 To view the result: netsh interface portproxy show all


0

I think you location is incorrect, use location /api/ { proxy_pass http://127.0.0.1:4567; } Add slash in the end of your location.


0

Found the solution. Instead of adding this configuration to nginx.conf, I added it to /etc/nginx/sites-enabled/default and it seems to have done the trick.


0

My question is, how can this actually be? Because they designed it at such. Who is crazy enough to request 2 ports to be wide open... Apparently this vendor is. Seriously, though, this is something you need to work through with the vendor. They should have provided you a requirements list before purchasing the product, which would have included ...


0

Got it to work: qemu-system-i386 -net nic,model=rtl8139 -net user,hostfwd=tcp::3389-:3389 -redir tcp:443::443 -redir tcp:992::992 -redir tcp:1194::1194 -redir tcp:5555::5555 -redir udp:1194::1194 -redir udp:500::500 -redir udp:4500::4500 -m 512M -localtime -cpu core2duo,+nx -smp 2 -usbdevice tablet -k en-us -hda win.img -nographic


-2

Take a look on this apache documentation: mod_proxy You may found useful the first topic "Forward Proxies and Reverse Proxies/Gateways" and it's examples (maybe you'll need to dig a little bit more in examples in order to get it working) Some times you will have to add some rewrite rules for urls, but will do the trick Anyway, I will follow the ...


2

You can maybe use stunnel in addition with sslh : http://www.rutschle.net/tech/sslh.shtml sslh is a little program that analyse the protocol and redirect the package according to the protocol. According to the man page: Probes for HTTP, SSL, SSH, OpenVPN, tinc, XMPP are implemented, and any other protocol that can be tested using a regular ...


0

I think the issue may be related to the interface. You should mention the physical interface, not the bridge. for example, i would replace routed0 by eth0 Then i am a bit uncomfortable with -d xxx.xxx.xxx.xxx. Usually we don't need to mention the destination ip, because we already know it is your public ip. if you don't put you public ip it may not work. i ...


0

There is a sysctl setting preventing dnat to loopback. replace eth0 below with your external interface traffic is coming in on. To allow it sysctl -w net.ipv4.conf.eth0.route_localnet=1 or echo 1 > /proc/sys/net/ipv4/conf/eth0/route_localnet and to check the setting. cat /proc/sys/net/ipv4/conf/eth0/route_localnet now you can dnat to 127.0.0.1


0

There is a sysctl setting preventing dnat to loopback. replace eth0 below with your external interface traffic is coming in on. To allow it sysctl -w net.ipv4.conf.eth0.route_localnet=1 and to check the setting. cat /proc/sys/net/ipv4/conf/eth0/route_localnet Now your dnat to 127.0.0.1 will work.



Top 50 recent answers are included