1e stack pour le torrent et le vpn services: gluetun-1: cap_add: - NET_ADMIN container_name: gluetun-1 devices: - /dev/net/tun:/dev/net/tun environment: - PUID=568 - PGID=568 - TZ=Europe/Paris - UPDATER_PERIOD=24h - PROTON_EMAIL=[mail pour maj la liste des serv protons] - PROTON_PASSWORD=xxxxxx - VPN_TYPE=wireguard - VPN_SERVICE_PROVIDER=protonvpn - PORT_FORWARD_ONLY=on - VPN_PORT_FORWARDING=on - DNS_UPSTREAM_IPV6=on - DNS_UPSTREAM_RESOLVERS=quad9 # commande sépcifiqque pour pousser le port filé par proton dans qbittorrent via son API - >- VPN_PORT_FORWARDING_UP_COMMAND=/bin/sh -c 'wget -O- --retry-connrefused --post-data "json={\"listen_port\":{{PORT}},\"current_network_interface\":\"{{VPN_INTERFACE}}\",\"random_port\":false,\"upnp\":false}" http://127.0.0.1:8090/api/v2/app/setPreferences 2>&1' - >- VPN_PORT_FORWARDING_DOWN_COMMAND=/bin/sh -c 'wget -O- --retry-connrefused --post-data "json={\"listen_port\":0,\"current_network_interface\":\"lo"}" http://127.0.0.1:8090/api/v2/app/setPreferences 2>&1' - WIREGUARD_PRIVATE_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxx= - WIREGUARD_ADDRESSES=10.2.0.2/32, 2a07:b944::2:2/128 - SERVER_COUNTRIES=Sweden - HTTPPROXY=on - SHADOWSOCKS=on - FIREWALL_OUTBOUND_SUBNETS=172.20.0.0/16,192.168.0.0/24 image: qmcgaw/gluetun ports: - 8888:8888/tcp # uniquement pour offrir un proxy - '8090:8090' restart: unless-stopped volumes: - /ouvousvoulez/qbittorrent-1/gluetun:/gluetun qbittorrent-1: container_name: qbittorrent-1 depends_on: gluetun-1: condition: service_healthy restart: True environment: - PUID=568 - PGID=568 - TZ=Europe/Paris - WEBUI_PORT=8090 image: linuxserver/qbittorrent:latest network_mode: service:gluetun-1 restart: unless-stopped volumes: - /ouvousvoulez/qbittorrent-1/config:/config - /ouvousvoulez/qbittorrent-1/gluetun:/gluetun - /ouvousvoulezdata:/data 2e stack pour les outils services: qui: image: ghcr.io/autobrr/qui:latest container_name: qui restart: unless-stopped ports: - "7476:7476" volumes: - /ouvousvoulez/qui/config:/config - /ouvousvoulezdata:/data environment: - PUID=568 - PGID=568 - TZ=Europe/Paris prowlarr: container_name: prowlarr restart: unless-stopped image: ghcr.io/hotio/prowlarr dns: - 9.9.9.9 - 9.9.9.10 - 2620:fe::9 - 2620:fe::10 ports: - "9696:9696" environment: - PUID=568 - PGID=568 - UMASK=002 - TZ=Europe/Paris - WEBUI_PORTS=9696/tcp volumes: - /ouvousvoulez/prowlarr/config:/config - /ouvousvoulezdata:/data radarr: container_name: radarr image: ghcr.io/hotio/radarr ports: - "7878:7878" environment: - PUID=568 - PGID=568 - UMASK=002 - TZ=Europe/Paris - WEBUI_PORTS=7878/tcp volumes: - /ouvousvoulez/radarr/config:/config - /ouvousvoulezdata:/data

DailyDevlog | Day 12 End of day update :) 1. Project Update > Worked on Kiroku(The one on which i am working rn) > Understood OAuth and implemented it in the project. 2. Open Source > Had a discussion with one of the maintainer of Contour about possible future feature enhancements > Started working on migration documentation from HTTPProxy to GatewayAPI > No DSA today Overall a productive day. That's it for today | gn folks

This case-study explains how a team replaced multiple Ingress resources under shared domains with a single HTTPProxy to avoid resource conflicts, simplify routing, and enforce unified TLS/timeout policies when centralizing Helm charts ➤ ku.bz/D-bzMF9lM

This week on the Learn Kubernetes Weekly: 🔥 Informers Are Easy to Misuse 🎤 Three Optimization Lessons 🛑 Graceful Shutdown 🚪 Namespaces & Multi-tenancy 🎯 Centralizing Helm with HTTPProxy ⭐️ @StormForgeIO by CloudBolt Read it now: kube.today/issues/161

This case-study explains how a team replaced multiple Ingress resources under shared domains with a single HTTPProxy to avoid resource conflicts, simplify routing, and enforce unified TLS/timeout policies when centralizing Helm charts ➜ ku.bz/D-bzMF9lM

教程：当无法直接执行 docker compose build 时 假设宿主机系统中已经有代理 http://127.0.0.1:1088 http://127.0.0.1:1088 当使用 Dockerfile docker-compose.yml 项目时，需要在 docker-compose.yml 设置代理，方法如下： Dockerfile 不用动，按正常需求编写即可，不需要加入代理参数。 在 docker-compose.yml 中添加代理相关项目： 1️⃣ 构建阶段，在 build 项目下，添加使用宿主机网络和args，如： "build: network: host args: HTTPPROXY: http://127.0.0.1:1088 HTTPSPROXY: http://127.0.0.1:1088 NOPROXY: localhost,127.0.0.1,::1" 2️⃣ 在运行阶段，在容器服务下（build同级）添加使用主机网络及代理配置： "networkmode: host environment: • HTTPPROXY=http://127.0.0.1:1088 • HTTPSPROXY=http://127.0.0.1:1088 • NOPROXY=localhost,127.0.0.1,::1 • httpproxy=http://127.0.0.1:1088 • httpsproxy=http://127.0.0.1:1088 • noproxy=localhost,127.0.0.1,::1" 3️⃣ 如果运行阶段不使用 networkmode: host，如果项目本身需要 ports 映射的，还需要重新加上 ports 映射，例如： "# 移除 networkmode: host 后： ports: • "5005:5005" extrahosts: • "host.docker.internal:host-gateway" environment: • HTTPPROXY=http://host.docker.internal:1088 • HTTPSPROXY=http://host.docker.internal:1088 • NOPROXY=localhost,127.0.0.1,::1,host.docker.internal • httpproxy=http://host.docker.internal:1088 • httpsproxy=http://host.docker.internal:1088 • noproxy=localhost,127.0.0.1,::1,host.docker.internal" 💡 变更代理配置后用: docker compose build --no-cache 再 up，避免缓存。 💡 非 host 模式时，NOPROXY 里务必包含 host.docker.internal； 💡 Linux 上需 extra_hosts: ["host.docker.internal:host-gateway"]（Docker ≥ 20.10）。 查看更多：x.afffun.com/?post=e39e4e40-…

#HTTPProxy #PrivacidadeNaInternet #AnonimatoDigital #Cibersegurança #ProxyServer #NavegaçãoSegura #ProxyVsVPN #TecnologiaExplicada #InternetSeguro #bolhasec Quer entender mais sobre este assunto? Tem vídeo no canal sobre este tema: youtu.be/BthMMd8WKAc

CVE-2025-22870: Go: proxy bypass using IPv6 zone IDs openwall.com/lists/oss-secur… Go 1.24.1, 1.23.7 fix net/http, x/net/proxy, x/net/http/httpproxy. Matching of hosts against proxy patterns could improperly treat an IPv6 zone ID as a hostname component.

リプにあった写真で解決法思いつくの書いときます。 HTTPProxyを使う。 VPNを使う。 恐らくMACアドレス管理されてるので、Macアドレスを偽装する。 くらいかな

HTTP and HTTPS proxy may be familiar to experienced online users, but newcomers might mistake them for just another URL. In this article, Proxy UK explains the differences between HTTP and HTTPS proxy proxyuk.org/http-vs-https-pr… #proxy #proxyuk #http #https #httpproxy

❗New blog post❗ Check our bumpy way of revealing the cause of a mysterious performance problem 🔍 Read the "Clever, surprised and gray-haired" article at ➡ blog.allegro.tech/2023/12/lm… #AllegroTechBlog #performance #performancetuning #nginx #httpproxy #lmdb #modsecurity

Easegress v2.6.1 is released, featuring the addition of 'egctl logs' and 'egctl create httpproxy' commands, and other enhancements and bug fixes. Check out the details in the release notes: github.com/megaease/easegres…

本日のOSS貢献です bitnamiのhelm chartでContourが同一Namespaceに2つ以上配置すると、片方が動作しなくなる問題を解決しました [bitnami/contour] Added option to set leader-election-resource-name. github.com/bitnami/charts/pu… #k8s #Kubernetes #helm #contour #ingress #httpproxy

การสร้าง Root HTTPProxy บน Contour buff.ly/414W6Jc #kubernetes #k8s #docker

Plugin #2 - HttpProxy Say goodbye to Postman curl. Just ask ChatGPT to request whatever you want!

Simple Proxy Switcher Settings on Google Chrome Browser to help you switch proxies easily yilu.us/trial #simpleproxyswitcher #proxyswither #proxyextension #yilu #911s5 #911proxy #socks5proxy #httpproxy #911realternative #yiluproxy youtu.be/CqZdZUy-KNQ

How to use Simple Proxy Switcher extension with YiLuProxy on Chrome browser? yiluproxy.org/trial #simpleproxyswitcher #proxyextension #chromeproxy #yiluproxy #yilus5 #yilu #yilusocks5proxy #httpproxy #911s5 #911proxy #911realternative youtu.be/QJT31ye62Zo

Best Japan Proxy Server | Japan Web Proxy | Cheapest Residential IPs 2023 yilu.us/trial #japanproxy #japanipproxy #japanwebproxy #yiluproxy #yilu #socks5proxy #httpproxy #911s5 #911realternative youtu.be/uoVafbAYRUw