-
-
Notifications
You must be signed in to change notification settings - Fork 326
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: cannot use custom provider with PIA port forwarding code #2147
Comments
I also encountered this issue today. I similarly am using docker compose, Private Internet Access and running the latest version. |
- fix PIA port forwarding code usage - refers to #2147
Yep I didn't foresee this usage. I pushed 72e2e4b where now the server name required for port forwarding (for TLS name verification of PIA's API web server) is set from the first value of |
Is this urgent?
No
Host OS
Ubuntu Jammy
CPU arch
x86_64
VPN service provider
Private Internet Access
What are you using to run the container
Portainer
What is the version of Gluetun
Running version latest built on 2024-03-07T12:32:25.391Z (commit 3254fc8)
What's the problem 🤔
As Wireguard isn't officially supported for PIA, I was able to run my PIA wireguard configuration via custom service provider which works great.
I was trying to add port forwarding by setting VPN_PORT_FORWARDING_PROVIDER to private internet access as written in the wiki here that states: Choose the custom port forwarding code to use. This is useful when using the custom provider with Wireguard.
When I do I get error "panic: server name cannot be empty" (see logs below)
When I try to add the server name, it seems like it is not an accepted parameter under custom provider: "VPN settings: provider settings: server selection: for VPN service provider custom: the server name specified is not valid: one or more values is set but there is no possible value available"
Would you know what I am doing wrong?
Thank you for the help! Love your work on gluetun, this service is awesome
Share your logs (at least 10 lines)
Share your configuration
The text was updated successfully, but these errors were encountered: