Cannot get OpenVPN-as to run correctly after installing Openvpn-as via Portainer on OMV 5.2.5-1

    I tried installing Openvpn-as via Portainer on OMV 5.2.5-1, container seems to be created correctly but when Openvpn-as starts I receive the following error in the logs in Portainer: ./run: line 3: /usr/local/openvpn_as/scripts/openvpnas: Permission denied will receive this error forever until I stop the container.


    I can see the scripts/openvpnas folder under the Docker folder, do I have to give exclusive rights to root, or some other user? I have several other Docker containers up and running via Portainer with no issues.


    Any assistance is appreciated. Thanks in advance.

    Trying to do the same thing, following technodad video (https://www.youtube.com/watch?v=nMthOobE-8g) but with the following changes for OMV.


    Edit this file /etc/openmediavault/config.xml Removing noexec from mntent

    omv-salt deploy run fstab <-  Instead of omv-mkconf fstab  (as per https://forum.openmediavault.org/index.php?thread/28623-with-omv-mkconf-missing-omv-fstab-mntops-ext4-variable-deprecated-how-can-one-mo/)


    But the GUI is not available for me. The error I'm seeing is as follows:-


    Initializing OpenVPN...

    Removing Cluster Admin user login...

    userdel "admin_c"

    Adding new user login...

    useradd -s /sbin/nologin "openvpn"

    Writing as configuration file...

    Perform sa init...

    Wiping any previous userdb...

    Creating default profile...

    Modifying default profile...

    Adding new user to userdb...

    Modifying new user as superuser in userdb...

    Getting hostname...

    Hostname: 361f6853d334

    Preparing web certificates...

    Getting web user account...

    Adding web group account...

    Adding web user account...

    Adding web group...

    Adjusting license directory ownership...

    Initializing confdb...

    Generating PAM config...

    Enabling service

    Error: Could not execute 'systemctl enable openvpnas' to enable startup/shutdown scripts


    Any suggestions appreciated

    Did you eventually find the problem?
    I have the same problem right now.


    EDIT:
    I found the problem, the interface was set to eth0 by default.
    But my interface is apparently eno1.

    It started working a few minutes after I deleted my container and made a new one with this change.


    The error is still there BTW so that is something else entirely.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden