Unable to start container with TORGUARD

[ramimasri79]

I've been having issues starting the container with torguard for at least about a week.

I'm looking at the logs and it keeps on throwing the following error then restarting.
Options error: Unrecognized option or missing or extra parameter(s) in /etc/openvpn/torguard/Canada.Toronto.ovpn:16: ncp-disable (2.6.19)

I'm assuming this is something that's build into the container? Otherwise, not sure where else it could be set.

My compose file looks something like this

transmission-vpn:
container_name: transmission-vpn
image: haugene/transmission-openvpn
cap_add:
- NET_ADMIN
restart: always
ports:
- "9091:9091"
dns:
- 8.8.8.8
- 8.8.4.4
volumes:
- /home/docker/transmission-vpn:/data
- /home/docker/shared:/shared
- /home/docker/Downloads:/data/watch
- /home/docker/Downloads/Completed:/downloads
- /home/docker/Downloads/Incomplete:/data/incomplete
- /etc/localtime:/etc/localtime:ro
environment:
- OPENVPN_PROVIDER=TORGUARD
- OPENVPN_CONFIG=Canada.Toronto
- .....

[tzacher16]

Been having the same exact issue. A few weeks ago I was able to comment out the ncp-disable line in the ovpn files and it worked, but this week they all reset and I'm experiencing the same thing again. I try to comment out again, save, and then when the container relaunches the file has been reset to uncomment the ncp-disable.

[laneoneil96]

Having the same issue. Commenting out or deleting the ncp-disable line and restarting the container only resets the default.ovpn file to include the ncp-disable line again.

[laneoneil96]

Worked with Claude to fix this. Sounds like the vpn configs need updated to fix this issue. The image pulls the TorGuard configs from the vpn-configs-contrib github repo that still has the ncp-disable flag in it. From Claude:

"The haugene/transmission-openvpn image pulls TorGuard's configs from the vpn-configs-contrib GitHub repo, and that repo still had ncp-disable in the TorGuard config files even though OpenVPN 2.6 removed support for it. So when the image updated its base OpenVPN version to 2.6, it broke because the config files weren't updated to match.
It's a classic case of two moving parts not being kept in sync — the OpenVPN binary moved forward but the config templates didn't follow. The vpn-configs-contrib repo is community maintained, so fixes depend on someone noticing and submitting a PR.
You could actually contribute the fix back to the repo if you wanted — removing ncp-disable from the TorGuard configs would save anyone else who hits this same issue."

EDIT: My actual fix with Claude was to stop pulling the config from the repo and use a local copy of the config that I removed the ncp-disable flag from. Mount the local config file into the container and use "-e VPN_CONFIG_SOURCE=local" in your docker compose or docker run command to stop the image from pulling from the repo.

I assume once the configs are fixed on the repo, you can remove the container, remove the "-e VPN_CONFIG_SOURCE=local" variable from docker compose or rerun the docker run command without that variable and it will go back to pulling configs from the repo.

[itzyoungen]

Got this issue as well..I'll try the local files tonight.