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

expressvpn connection #2709

Closed
7 of 8 tasks
azchoi opened this issue Sep 6, 2023 · 2 comments
Closed
7 of 8 tasks

expressvpn connection #2709

azchoi opened this issue Sep 6, 2023 · 2 comments

Comments

@azchoi
Copy link

azchoi commented Sep 6, 2023

Is there a pinned issue for this?

  • I have read the pinned issues and could not find my issue

Is there an existing or similar issue/discussion for this?

  • I have searched the existing issues
  • I have searched the existing discussions

Is there any comment in the documentation for this?

  • I have read the documentation, especially the FAQ and Troubleshooting parts

Is this related to a provider?

  • I have checked the provider repo for issues
  • My issue is NOT related to a provider

Are you using the latest release?

  • I am using the latest release

Have you tried using the dev branch latest?

  • I have tried using dev branch

Docker run config used

version: '3.3'
services:
transmission-openvpn:
restart: always
cap_add:
- NET_ADMIN
volumes:
- '/volume2/Transmission/:/data'
- '/volume2/Transmission/:/config'
environment:
- OPENVPN_PROVIDER=EXPRESSVPN
- OPENVPN_USERNAME=*******
- OPENVPN_PASSWORD=*******
- OPENVPN_CONFIG=*******
- OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60
- LOCAL_NETWORK=192.168.1.0/24
- TZ=*******
- HEALTH_CHECK_HOST=google.com
- TRANSMISSION_WEB_UI=flood-for-transmission
- TRANSMISSION_RPC_AUTHENTICATION_REQUIRED=true
- TRANSMISSION_RPC_HOST_WHITELIST="127.0.0.1,192.168.1.,172.17.0."
- TRANSMISSION_RPC_HOST_WHITELIST_ENABLED=true
- TRANSMISSION_RPC_PASSWORD=*******
- TRANSMISSION_RPC_USERNAME=*******
- TRANSMISSION_SCRAPE_PAUSED_TORRENTS_ENABLED=false
- TRANSMISSION_WATCH_DIR_ENABLED=true
- TRANSMISSION_WATCH_DIR=/data/torrentfile
logging:
driver: json-file
options:
max-size: 10m
ports:
- '9091:9091'
dns:
- 1.1.1.1
- 1.0.0.1
image: haugene/transmission-openvpn

Current Behavior

Now I'm using expressVPN and Docker cannot start and restart continuously after v5.2.0 update.

Expected Behavior

It seems docker cannot connect to vpn server.
Please see this log message.
"No bundled config script found for EXPRESSVPN."

How have you tried to solve the problem?

I tried to chage "OPENVPN_CONFIG" location but failed.

Log output

Please commit your changes or stash them before you merge.
Aborting
Updating ca833e094..45cc9b305
Starting container with revision: b33d0fe
TRANSMISSION_HOME is currently set to: /config/transmission-home
WARNING: Deprecated. Found old default transmission-home folder at /data/transmission-home, setting this as TRANSMISSION_HOME. This might break in future versions.
We will fallback to this directory as long as the folder exists. Please consider moving it to /config/transmission-home
Creating TUN device /dev/net/tun
Using OpenVPN provider: EXPRESSVPN
Running with VPN_CONFIG_SOURCE auto
No bundled config script found for EXPRESSVPN. Defaulting to external config
Will get configs from https://github.com/haugene/vpn-configs-contrib.git
Repository is already cloned, checking for update
error: Your local changes to the following files would be overwritten by merge:
openvpn/nordvpn/configure-openvpn.sh
Please commit your changes or stash them before you merge.
Aborting
Updating ca833e094..45cc9b305

HW/SW Environment

- OS:synology dsm 7.2
- Docker: v5.2.0 (latest)

Anything else?

No response

@petebanham
Copy link

Have deleted my last comment so as not to confuse things as my issue was not related to 5.2.0 it was the Dev build 5.1.1 that I was having a problem with

@pkishino
Copy link
Collaborator

pkishino commented Sep 6, 2023

This is not an issue with the container, this is an issue with your setup.. you are trying to run this inside a local git repo folder..
Remove your changes

@pkishino pkishino closed this as not planned Won't fix, can't repro, duplicate, stale Sep 6, 2023
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

3 participants