-
-
Notifications
You must be signed in to change notification settings - Fork 406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: No forwarded port being fetched (using PIA) #2710
Comments
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
|
try: |
You're a wizard Harry! It's always the simplest things that slip through the cracks. Thank you! |
Closed issues are NOT monitored, so commenting here is likely to be not seen. This is an automated comment setup because @qdm12 is the sole maintainer of this project |
Is this urgent?
No
Host OS
Synology DSM 6.2.4-25556 Update 8
CPU arch
x86_64
VPN service provider
Private Internet Access
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version latest built on 2025-01-22T08:30:14.628Z (commit 13532c8)
What's the problem 🤔
No forwarded port is being grabbed by gluetun. There's no mention of a forwarded port being obtained in the logs, and no port is written to
/tmp/gluetun/forwarded_port
.Running
ls /tmp/gluetun/
shows theip
file is there, but no other file.cat /tmp/gluetun/ip
confirms the IP written toip
is correct.Since there's no error message in the gluetun logs I'm guessing the error is with gluetun rather than PIA.
I tried explicitly settings
VPN_PORT_FORWARDING_STATUS_FILE
to both the default directory and to a different directory, but neither produced a file.Share your logs (at least 10 lines)
Share your configuration
The text was updated successfully, but these errors were encountered: