-
-
Notifications
You must be signed in to change notification settings - Fork 396
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: "the hostname specified is not valid" when using custom wireguard vpn. #2042
Comments
I am also facing the same problem and can't use the hostname (like engage.cloudflareclient.com). The custom mode seems to only accept IP addresses and with WARP, it doesn't work. |
True, this is still an issue as of July 2024, the only option is to manually update the IP once in a while when it stops working or a little script that could probably update the docker compose in a scheduled manner. |
Duplicate of #788 - please subscribe to that one. This is by design, see https://github.com/qdm12/gluetun-wiki/blob/main/faq/others.md#server-information |
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
TrueNAS
CPU arch
x86_64
VPN service provider
Custom
What are you using to run the container
Kubernetes
What is the version of Gluetun
Running version v3.36.0 built on 2023-10-31T13:10:39.622Z (commit 1c43a1d)
What's the problem 🤔
It seems that there is no way to use an hostname when setting up a custom wireguard config, I'm forced to enter an IP.
The docs on custom wireguard config doesn't show a way to setup up an hostname endpoint either.
Share your logs (at least 10 lines)
The text was updated successfully, but these errors were encountered: