Skip to content
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: Openvpn host URL not resolved (using custom provider) #1094

Closed
sa6kad opened this issue Aug 4, 2022 · 1 comment
Closed

Bug: Openvpn host URL not resolved (using custom provider) #1094

sa6kad opened this issue Aug 4, 2022 · 1 comment

Comments

@sa6kad
Copy link

sa6kad commented Aug 4, 2022

Is this urgent?

No response

Host OS

Debian, Ubuntu

CPU arch

x86_64

VPN service provider

Custom

What are you using to run the container

docker-compose

What is the version of Gluetun

latest

What's the problem 🤔

First of all, thanks for a cool container!

I am using custom provider in order to connect to Ivacy VPN. Conf .conf files usually containd URLs of the VPN servers.

I tried to nslookup the IP address and substitute the URL and everything seem to work.
Other containers, such as dperson's do not have this issue.

Share your logs

` 2022-08-04T09:53:14Z ERROR VPN settings: OpenVPN settings: custom configuration file: failed extracting information from custom configuration file: cannot extract connection from file: on line 4: failed extracting from remote line: host is not an an IP address: pl2-auto-udp.ptoserver.com`

Share your configuration

---
version: "3"

networks:
  infra_out:
    driver: bridge
    external: true

services:
  vpn_gw_ru:
    image: qmcgaw/gluetun
    container_name: vpn_gw
    cap_add:
      - NET_ADMIN
    volumes:
      - ~/docker_volumes/vpn_gw/client.conf:/gluetun/custom.conf:ro
    environment:
      - VPN_SERVICE_PROVIDER=custom
      - VPN_TYPE=openvpn
      - OPENVPN_CUSTOM_CONFIG=/gluetun/custom.conf
      - OPENVPN_USER=myusername
      - OPENVPN_PASSWORD=mypass
    networks:
      infra_out
@qdm12
Copy link
Owner

qdm12 commented Aug 4, 2022

It's explained in the wiki faq why that is, it's to avoid leaking anything before connection. So it's more by design than a bug, but I'm working on making this optional, subscribe to #788 for it.

@qdm12 qdm12 closed this as completed Aug 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants