New answers tagged

0

Between making modifications based on this post: http://serverfault.com/questions/598202/make-nginx-to-pass-hostname-of-the-upstream-when-reverseproxying and re-reading my configuration I managed to get it working.


0

While nginx supports wildcards and regular expression in server_name, you still have to specify the subdomain while proxying. This can be done using the $host variable: server { server_name .mydomain.com; listen 80; location / { proxy_pass http://$host; } access_log /var/log/nginx/$host-access.log; error_log ...


0

Edit your .ovpn file and put your tcp connection line under connection tag and define all needy_proxy there. <connection> remote vpn_ip_here vpn_port tcp http-proxy y.y.y.y 8080 (replaced actual IP here) http-proxy-retry </connection>


0

OP's answer I found the problem, it was really related to the proxy-server but with a different background. Our server uses authentication which was not set up here. After disabling it, the problem went away. The strange think is the misleading error message. So hopefully this will read somebody in the future with the same problem.


0

I think your best bet in this case would be to use the DNAT target of iptables. This rule assumes that your box has a route in its kernel to the 10.0.0.0/x network (x being your subnet). Using your remote address of 10.0.0.44, we run: iptables -t nat -I PREROUTING 1 -i eth0:0 -d 192.168.0.10 -j DNAT --to 10.0.0.44 For good measure, run this one too if you ...


1

If you want to block porn on a single computer, PeerGuardian should suit your needs. Just install the software, and add the Porn blocklist. Installation: http://sourceforge.net/p/peerguardian/wiki/pgl-Install-DebianUbuntu/ Blocklists: https://www.iblocklist.com/lists


0

this works for me with socks/socks5 on google-chrome : ssh -D 8080 -C -N user@remote.host.domain google-chrome --proxy-server="socks://localhost:8080" google-chrome --proxy-server="socks5://localhost:8080"


0

Perhaps this is not the answer you're looking for, but if you still have on your home in the U.S. a computer turned on and connected to the Internet, you could use software such as TeamViewer or RDP to connect from your current location to the computer in the U.S.


1

I made a tool to simplify the entire task. You can download it from this link. Also, you can have a look at the code if you are more interested to know the backend functioning. Download the zip file,extract them, go to the location of extracted files in terminal and following commands would help you: * bash main.sh : to set and unset proxy. * bash ...


0

You can set up automatic authentication by going to to your System Settings -> Network Then change manual to automatic and set your proxys etc.


2

Proxy parameters File /etc/bash.bashrc: export http_proxy=http://username:password@proxyserver.net:port/ export https_proxy=http://username:password@proxyserver.net:port/ export ftp_proxy=http://username:password@proxyserver.net:port/ File /etc/environment: http_proxy=http://username:password@proxyserver.net:port/ ...



Top 50 recent answers are included