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
Problem running on OpenVZ #129
Comments
Thanks for the issue. There was the same issue with Debian 9. Could you try this branch? https://github.com/Angristan/OpenVPN-install/blob/systemd-openvz-fix/openvpn-install.sh |
@angristan |
@michaelfresco Nice to hear, were you using OpenVZ? |
@angristan Yes, I was using OpenVZ. All the time I could not get traffic through openvpn, even though I did successfully connect to it. It was a major headache honestly. I tried to ping 8.8.4.4, but got no relpy. The script from the systemmd-openvz branch fixed it all though! Real magic! |
@michaelfresco Thanks for the feedback! What os are you using BTW? |
@angristan Debian GNU/Linux 8.9 (jessie). With uname -r: |
@michaelfresco ok, thanks |
just installed debian 9 on a openvz server and can confirm commenting this line out fixes this issue :) i will conect later with my client to confirm data flow and everything is corret, but atleast now the openvpn@server service started :) |
On Debian 9 the unit file openvpn-server@.service must use and modyfy for OpenVZ. The file openvpn@.service does not work.
On Debian 9 the copy of unit file `/etc/systemd/system/openvpn@.service` has no effect, see angristan#583. Same problem as angristan#129 and angristan#378, unit can not start on OpenVZ. There must execute `systemctl enable` before `systemctl restart`. So the new link to `/etc/systemd/system/openvpn@.service` was created before `systemctl restart`.
On Debian 9 the copy of unit file `/etc/systemd/system/openvpn@.service` has no effect, see #583. Same problem as #129 and #378, unit can not start on OpenVZ. It must execute `systemctl enable` before `systemctl restart`. So the new link to `/etc/systemd/system/openvpn@.service` was created before `systemctl restart`.
On Debian 9 the copy of unit file `/etc/systemd/system/openvpn@.service` has no effect, see #583. Same problem as #129 and #378, unit can not start on OpenVZ. It must execute `systemctl enable` before `systemctl restart`. So the new link to `/etc/systemd/system/openvpn@.service` was created before `systemctl restart`. Fix #583
On Debian 9 the copy of unit file `/etc/systemd/system/openvpn@.service` has no effect, see angristan#583. Same problem as angristan#129 and angristan#378, unit can not start on OpenVZ. It must execute `systemctl enable` before `systemctl restart`. So the new link to `/etc/systemd/system/openvpn@.service` was created before `systemctl restart`. Fix angristan#583
Error:
Job for openvpn@server.service failed because the control process exited with error code. See "systemctl status openvpn@server.service" and "journalctl -xe" for details.
Output of
systemctl status openvpn@server.service
:OS: Ubuntu 16.04 x64 running on OpenVZ
Workaround:
Credits:
The text was updated successfully, but these errors were encountered: