docs
gluetun
docs | gluetun | |
---|---|---|
103 | 374 | |
180 | 6,138 | |
2.2% | - | |
7.7 | 9.2 | |
6 days ago | 5 days ago | |
HTML | Go | |
Creative Commons Attribution Share Alike 4.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docs
-
Blocky – a DNS proxy and ad-blocker for the local network
It's a DNS proxy, like pi-hole, but it seems a lot more powerful than Pi-hole that is basically just a configured dnsmasq server to be user-friendly.
https://docs.pi-hole.net/
-
Pi hole set up for total beginner
I highly recommend the documentation or this video (which also has a blog) that I followed.
- Any help?? Gravity isn't updating :(
- TV's are becoming intrusive and abusive; what to do about it?
-
Vizio apparently doesn't like cord cutters
Protip: Setup a DNS Sinkhole on your network and you can easily block Vizio and other devices from calling home to update. https://docs.pi-hole.net/
- Will i be able to setup pihole with this settings on my router?
-
No internet access for containers co-hosted with pihole
version: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ networks: dns_net: driver: bridge ipam: config: - subnet: 10.2.0.0/24 services: pihole: depends_on: [unbound] container_name: pihole image: pihole/pihole:latest hostname: pihole networks: dns_net: ipv4_address: 10.2.0.100 ports: - "5335:53/tcp" - "5335:53/udp" - "7000:80/tcp" environment: TZ: ${TZ} WEBPASSWORD: ${PWD} FTLCONF_LOCAL_IPV4: ${HOST_IP} # Set to server's LAN IP, used by web block modes. PIHOLE_DNS_: 10.2.0.200 # Upstream DNS server(s) for Pi-hole to forward queries to, separated by a semicolon DNSMASQ_LISTENING: all # "Listen on all interfaces, permit all origins" # Volumes store your data between container upgrades volumes: - /var/lib/docker/volumes/pihole/etc-pihole:/etc/pihole - /var/lib/docker/volumes/pihole/etc-dnsmasq.d:/etc/dnsmasq.d healthcheck: disable: true restart: unless-stopped unbound: # https://github.com/MatthewVance/unbound-docker container_name: unbound image: mvance/unbound:latest hostname: unbound networks: dns_net: ipv4_address: 10.2.0.200 ports: - "${HOST_IP}:53:53/udp" - "${HOST_IP}:53:53/tcp" healthcheck: disable: true restart: unless-stopped
- 2023 May 8 Stickied -FAQ- & -HELPDESK- thread - Boot problems? Power supply problems? Display problems? Networking problems? Need ideas? Get help with these and other questions!
-
What product was better 10 yrs ago than it is today?
Absolutely. Check out the Pi-Hole documentation here: https://docs.pi-hole.net/
-
Software to monitor Wi-Fi traffic?
See https://docs.pi-hole.net/
gluetun
-
Custom command on docker startup after watchtower update
healthcheck: # https://github.com/qdm12/gluetun/issues/641#issuecomment-933856220 test: "curl -sf https://example.com || exit 1" interval: 1m timeout: 10s retries: 2
-
Communicating with another docker container that is networked through a VPN container
I have containers a,b,c. Container C is running Gluetun (https://github.com/qdm12/gluetun) which is a VPN container.
- Restart vpn connection (new ip) from inside the container?
-
It's this time of the year again... which open-source project are you donating to?
The last couple of years I have been donating to Gluetun.
-
How to host a docker based proxy for selected containers
One option I could find is Gluetun, which looks very popular and actively maintained. In this case we have one single point of contact with VPN provider. The other containers should be run with network_mode: service:gluetun. If I understand correctly, those container will use VPN for every network operation, even for inter-container communication. Would they be visible for the containers not attached to gluetun (e.g. the SWAG reverse proxy)?
-
Express vpn container
Try setting it up. https://github.com/qdm12/gluetun See if it works for your needs.
-
Easy port-forwarding on linux
After some digging around, I found this project, which I think should get a lot more light on itself. It allows to setup port-forwarding on linux very easily, together with a lot of other things !
-
running a docker with a torrent client and vpn INSIDE the container... bad idea?
I setup Gluetun with qbittorrent in docker. Gluetun connects to the nord via manual login and I get to choose the specific servers I want it to you in its environment variables.
-
Gluetun killswitch
Hi guys, I have a dumb question: according to their github page, one of the features is the killswitch. It is not clear to me whether this would shutdown other containers (connected to it) when vpn drops, or only when the whole internet connection goes down
-
NordVPN - AUTH_FAILED Your credentials might be wrong
# See https://github.com/qdm12/gluetun/wiki
What are some alternatives?
mkdocs-material - Documentation that simply works
docker-wireguard-pia - A Docker container for using Wireguard with PIA.
docker-pi-hole - Pi-hole in a docker container
openvpn-client
mike - Manage multiple versions of your MkDocs-powered documentation via Git
docker-transmission-openvpn - Docker container running Transmission torrent client with WebUI over an OpenVPN tunnel
mkdocstrings - :blue_book: Automatic documentation from sources, for MkDocs.
nordlynx
fastapi - FastAPI framework, high performance, easy to learn, fast to code, ready for production
nordvpn - NordVpn Docker Client
nextdns - NextDNS CLI client (DoH Proxy)
docker-qBittorrentvpn - Docker container which runs a headless qBittorrent client with WebUI and optional OpenVPN