New answers tagged

0

If you do not want apt-get to use a proxy, use apt-get as: sudo apt-get -o Acquire::http::proxy=false <update/install>


0

I couldn't get the other answer to work. I have a raspberry pi in the network of a customer who blocks port 80. So I installed polipo (a socks/http proxy) on my own maschine, connect with ssh on that raspberry pi and while doing so create a tunnel to polipo-proxy. To install polipo (I use this on a Ubuntu 16.04 maschine): sudo apt install polipo This ...


1

You have not enabled SSL in your nginx server {} block. The line that needs changing: listen 3120 ; should instead be: listen 3120 ssl; This will enable SSL for that nginx server {} block, but if you have not noticed already, HTTP (non-SSL) will stop working on port 3120. You may be able to set that server {} block to listen to both HTTP and HTTPS ...


0

You can have different approaches. On is based on DNS blocking, and pi-hole, as @DopeGhoti said, is the best choice: you feed it with ad blocklists (you can find it on blocklist.site, fo example) and eventually with regular expressions. The other one is filtering traffic with an http / https proxy, such as squid cache: you can feed its block list with the ...


Top 50 recent answers are included