# CC 100 OpenVPN Configuration via SSH **URL:** \ **Category:** Hardware and Linux\ **Tags:** how-to, edge-controller, linux, cc100\ **Created:** [March 31, 2026, 1:25pm UTC](https://www.wago.community/t/cc-100-openvpn-configuration-via-ssh/2655 "2026-03-31T13:25:04Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Dr.Fix](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/dr.fix/32/498_2.png) [@Dr.Fix](https://www.wago.community/u/Dr.Fix)\ **Post date:** [March 31, 2026, 1:25pm UTC](https://www.wago.community/t/cc-100-openvpn-configuration-via-ssh/2655/1 "2026-03-31T13:25:04Z")
Hello everyone, We are already using OpenVPN with the CC100. With the additional information from this forum and the YouTube how-to video ([https://www.youtube.com/watch?v=H4c7NQiCalk](https://www.youtube.com/watch?v=H4c7NQiCalk)) regarding the extra OVPN config lines > pull-filter ignore ifconfig-ipv6 > pull-filter ignore route-ipv6 > pull-filter ignore ‘redirect-gateway ipv6’ as well as log > /var/log/openvpn.log the connection works reliably after a reboot. Our question is now the following: Is it possible to deploy the profile configuration without using the UI (WBM \> Security \> OpenVPN / IPsec), for example by copying it to the controller via SCP, and then configuring it via terminal (SSH) to 1. store the configuration, and 2. enable OpenVPN using the previously stored profile configuration? What commands would be required for this? Our goal is to perform this step without any user interaction (UI). Thank you in advance! ---
**Author:** ![WagoDamRud](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagodamrud/32/258_2.png) [@WagoDamRud](https://www.wago.community/u/WagoDamRud)\ **Post date:** [April 1, 2026, 8:18am UTC](https://www.wago.community/t/cc-100-openvpn-configuration-via-ssh/2655/2 "2026-04-01T08:18:26Z")
Everything what you can do from WBM you can do by scripts from _/etc/config-tools_ (thats how WBM works, it runs scripts using php). So there is _ **/etc/config-tools/vpncfg** _ ```auto /etc/config-tools ./vpncfg --help Usage: vpncfg -h|--help vpncfg vpn CMD vpncfg VPN CMD vpncfg crt CMD vpncfg file CMD [OPTIONS] Basic commands: -h, --help prints this help vpn - general commands: vpncfg vpn CMD --get-full-status returns all status information using json format, including the list of certificates from --get-cert-command VPN - OpenVPN/IPsec common commands: vpncfg VPN CMD executs command for a selected type of vpn framework. VPN can be set to either ipsec or ovpn and there are the following types of CMD commands: --is-enabled returns enabled|disabled if VPN is started on boot --enable enables VPN on boot --disable disables VPN on boot --is-running returns running|stopped status of the VPN --start starts VPN service --stop stops VPN service --restart restarts VPN service --reload orders VPN to reload configuration files crt - certificate commands: vpncfg crt CMD --get-list returns a list of certificates using json format key - private keys commands: vpncfg key CMD --get-list returns a list of private keys using json format file - file commands: vpncfg file CMD [OPTIONS] --store FILE SRC_FILE copies content of a file designated by SRC_FILE to its correct name. If the file already exists it will be overwritten. FILE parameter names a type of a file which might be one of: cert, key, ipsec.conf, ipsec.secrets openvpn.conf. Source files shall be stored inside /tmp/vpncfg/ directory. --read FILE drops content of a file on std out. Allowed are the following FILE values: ipsec.conf, openvpn.conf. --remove FILE [NAME] removes a file completely. In case of the FILE argument allowed are all values from --store command, but in case of the cert and key files also NAME of the file must be given. --copy FILE USER GROUP copies content of a FILE to a /tmp/vpncfg-out/FILE location. FILE values: ipsec.conf, openvpn.conf. The copied file will be owned by USER:GROUP with access rights set to 0600. Example: vpncfg ipsec --is-enabled vpncfg file --store cert user_certificate.pem The full source file path is: /tmp/vpncfg/user_certificate.pem ``` You can also edit directly OpenVPN config file: _/etc/openvpn/openvpn.conf_ and then just reload configuration and enable OpenVPN with commands ---
**Author:** ![Dr.Fix](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/dr.fix/32/498_2.png) [@Dr.Fix](https://www.wago.community/u/Dr.Fix)\ **Post date:** [April 1, 2026, 1:47pm UTC](https://www.wago.community/t/cc-100-openvpn-configuration-via-ssh/2655/3 "2026-04-01T13:47:32Z")
@WagoDamRud, thank you very much for your detailed explanation. We were aware that /etc/config-tools is used in the background; however, it only became clear through your response that _vpncfg_ is the corresponding script behind it. This clarification was particularly valuable for us. With this insight, and the additional guidance from the `--help` description, we are now able to proceed effectively.