Open Stylback opened 1 year ago
Same issue there.
I'm also observing this issue.
Same here
version: "3"
services:
gluetun:
image: qmcgaw/gluetun:latest
container_name: gluetun_usa
cap_add:
- NET_ADMIN
network_mode: bridge
ports:
- 30000:8888/tcp # HTTP proxy
- 30001:8388/tcp # Shadowsocks
- 30001:8388/udp # Shadowsocks
volumes:
- /home/david/gluetun/usa/data:/gluetun
environment:
- OPENVPN_USER=redacted
- OPENVPN_PASSWORD=redacted
- VPNSP=private internet access
- REGION=usa
- TZ=Europe/Madrid
- HTTPPROXY=on
- HTTPPROXY_LOG=off
- HTTPPROXY_PORT=8888
- HTTPPROXY_USER=daviid
- HTTPPROXY_PASSWORD=redacted
- HTTPPROXY_STEALTH=on
- SHADOWSOCKS=on
restart: always
I am seeing the same thing on my end. Services can connect to the proxy just fine but my logs are littered with these messages. Is this a configuration error on my part?
Is this urgent?
No
Host OS
Ubuntu Server 22.04 LTS
CPU arch
x86_64
VPN service provider
Mullvad
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version latest built on 2022-12-31T17:50:58.654Z (commit ea40b84)
What's the problem 🤔
Hi! I've been spending the last few evenings testing out Gluetun. I have a media stack (qbittorrent, *arr, jellyfin) where each service have their own docker container. My goal have been to have a Gluetun container with Mullvad which I then could use as a proxy for other containers.
I noticed that if I have the
HTTPPROXY_USER
andHTTPPROXY_PASSWORD
environment variables enabled, each service that connect to Gluetun's HTTP proxy with the given credentials will produce a log entry claiming the incoming request lacks aProxy-Authorization header
. The service will however still be able to complete its requests without issue.This behaviour seems contradictory. I don't know if this is an inteded behaviour (did not see another issue on this) or if there is a missconfiguration on my end. Either way it is currently flooding my logs and I hope there is a way to resolve this without disabling proxy authentication.
Share your logs
Share your configuration