@Daniel, what version are you using? The /etc/init.d/openvpn screen from
bionic has that same snippet you mentioned from upstream
'# Source defaults file; edit that file to configure this script.
AUTOSTART="all"
STATUSREFRESH=10'
@Paulo, from what file did you change the sh to bash and how did yo
I changed the first line of #/bin/sh -e to #/bin/bash and it worked
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771650
Title:
openvpn startup script isn't working in ubuntu 18.04
To manage notif
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771650
Title:
openvpn startup script isn't working in ubuntu 18.04
To manage notifications about this bug go to
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771650
Title:
openvpn startup script isn't working in ubuntu 18.04
To manage notifications about this bug go to:
I also came across this issue.
This is a not quite obvious thing in the default installation (I mean the
@-services).
As far as I could get it (and found in internets), the service relies on the
init-script:
/etc/init.d/openvpn
which only starts the found .conf files if the AUTOSTART var = "all
It shouldn't be necessary to do explicit "enable" calls to make this
work. The generator _should_ be finding all the .conf files
automatically:
/lib/systemd/system-generators/openvpn-generator
However, it is NOT working for me...
--
You received this bug notification because you are a member of
I was also able to fix the problem by switching from openvpn-
server@.service to openvpn@.service
#Fanar, I think that step #3 above (coupled with the reboot) is what
actually fixed your issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Also affects: openvpn
Importance: Undecided
Status: New
** Project changed: openvpn => ubuntu-release-notes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771650
Title:
openvpn startup
to fix the problem I had to do this :
1- copy my config file to /etc/openvpn directory (not under /etc/openvpn/server)
2- systemctl enable open...@server2.conf
3- systemctl enable openvpn@server2 (to be sure).
4- systemctl start openvpn-server@server2
then rebooted, all works now and starts on bo
The client/server @ units need a config file, otherwise they cannot be
activated. I'm not sure what the main openvpn.service one is for now,
though.
Ah, it does nothing apparently:
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/true
ExecReload=/bin/true
WorkingDirectory=/etc/openvpn
--
@Fanar does comment #15 solve your case? If yes, I can add a release
notes task to this bug and update
https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes mentioning this change
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
@ahasenack, thanks, I was indeed wrong with the -client/-server@ units.
It's weird they don't show up in "systemctl -a | grep openvpn" though.
The openvpn.postinst only seem to enable openvpn.service.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Assuming you have a config file called /etc/openvpn/server/myconfig, can
you try:
systemctl start openvpn-server@myconfig
That should trigger the openvpn-server@ service file, which will replace %i in
the Exec line below with what's after @ in the systemctl start command:
ExecStart=/usr/sbin/ope
This needs further investigation, because the package does ship service
files for server and client:
# dpkg -L openvpn|grep service
/lib/systemd/system/openvpn-client@.service
/lib/systemd/system/openvpn-server@.service
/lib/systemd/system/openvpn.service
/lib/systemd/system/openvpn@.service
We m
The package shipped in Bionic does create the directories
/etc/openvpn/server and /etc/openvpn/client but it only ships a systemd
unit that looks for configuration files from /etc/openvpn directly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
See this upstream change:
https://github.com/OpenVPN/openvpn/commit/28bd79ac980488dbfce2e8136287e38c6f35a043
I believe all you had to do was place the config file in
/etc/openvpn/server or /etc/openvpn/client, then the systemd units would
pick it up automatically.
Could you please verify that? If
I can see that there is new file under :
/etc/systemd/system/multi-user.target.wants/openvpn@tcp2.service
we never needed such file before to run ovpn service.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
ok it worked this time, and it is still working even after restarting
the service
/etc/init.d/openvpn restart
ifconfig tun0
tun0: flags=4305 mtu 1500
inet 10.122.11.10 netmask 255.255.255.255 destination 10.0.11.9
inet6 fe80::82bc:c88a:6a62:bc0c prefixlen 64 scopeid 0x20
Can you try to enable and start it with:
sudo systemctl enable openvpn@myconfig
sudo systemctl start openvpn@myconfig
Then collect the logs as mentioned before, please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
systemctl -a | grep openvpn
openvpn.service
loadedactive exited
OpenVPN service
2018-05-25 17:53 GMT+03:00 Simon Déziel <1771...@bugs.launchpad.net>:
> What do you get from "systemctl -a | grep openvpn"?
>
> --
> You received this bug notification becaus
What do you get from "systemctl -a | grep openvpn"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771650
Title:
openvpn startup script isn't working in ubuntu 18.04
To manage notifications about t
I still can connect if I run openvpn from command line, but init script
won't start the service, I tried also making changes to
/etc/default/openvpn with no luck.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
No results :
cat /tmp/openvpn-myconfig.log
-- Logs begin at Thu 2018-05-24 11:33:12 +03, end at Fri 2018-05-25 17:37:44
+03. --
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771650
Title:
openv
the description suggests the command line openvpn is used, not the
network-manager plugin
** Package changed: network-manager-openvpn (Ubuntu) => openvpn (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
@Fanar, could you please attach the openvpn logs of the failed service
start? You can collect them with:
journalctl -u openvpn@myconfig > /tmp/openvpn-myconfig.log
Thanks
** Changed in: openvpn (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager-openvpn (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771
I have a problem that may be related, but I haven't been able to get
OpenVPN working. https://bugs.launchpad.net/ubuntu/+source/network-
manager-openvpn/+bug/1772066
How do you start OpenVPN manually?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
27 matches
Mail list logo
