at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76, line 2.)ĭebconf: falling back to frontend: Readlineĭebconf: unable to initialize frontend: Readlineĭebconf: (Can't locate Term/ReadLine.pm in (you may need to install the Term::ReadLine module) contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 /usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7, line 2.)ĭebconf: falling back to frontend: Teletypeĭpkg-preconfigure: unable to re-open stdin: Get:2 bionic/main amd64 openvpn-as amd64 2.8.3-f28d2eae-Ubuntu18 ĭebconf: unable to initialize frontend: Dialogĭebconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. Get:1 bionic/main amd64 openvpn-as-bundled-clients all 10 The following NEW packages will be installed:Ġ upgraded, 2 newly installed, 0 to remove and 2 not upgraded.Īfter this operation, 202 MB of additional disk space will be used. The following additional packages will be installed: Get:17 bionic-security/universe amd64 Packages Get:16 bionic-security/main amd64 Packages Get:13 bionic-updates/restricted amd64 Packages Get:12 bionic-updates/multiverse amd64 Packages Get:11 bionic-updates/main amd64 Packages Get:10 bionic-updates/universe amd64 Packages executing container initialization scripts.Ĭurrent default time zone: 'Europe/London'
ensuring user provided files have correct perms.exited 0. making user provided files available at /var/run/s6/etc.exited 0. Any assistance with that would too be appreciated. Any assistance would be appreciated.īonus issue - On the client side, getting the ns cert type deprecated issue. I have also tried removing and adding the container back. This has all worked in the past, but for some reason no longer works. Things I can confirm include 1194 being forwarded locally, container running in bridge mode with no additional changes to the setup. I have tried several options, but with no luck. I have been trying to follow all of the connection issues folks have been having with the web ui. Try accessing on the ip directly, not via reverse proxy Thanks for the people reading this and in general developing this container. Openvpn is configured on UDP 1194 and i've forwarded this port to my unraid server (as per spaceinvaders video).Īny idea what could prevent it from getting a connection?
OPENVPN AS DOWNLOAD
With my setup (as explained above) i can go on my mobile, go to my openvpn domain and download the access file for the mobile openvpn client.īUT when i try to connect to my openvpn server the connection times out. you’re using an unsupported networking method (host or macvlan)ġ) i do not know what this means or what i have to check and possible fixĢ) i've checked in advanced view, docker container is still created with "cap-add NET_ADMIN"ģ) i do not know exactly what this means, is it possible that you cannot run openvpn on a custom setup unraid network (in my case "proxynet" and letsencrypt) - does it only run on "bridge" mode? iptables issues on host (either not installed or missing kernel modules)ģ. Now, people linked to this POST a couple of posts back.ġ. > i get said error on login attempt with my created admin user (5) i go to openvpn.***.*/admin it opens to the admin login page
(4) i go to my web interface login of openvpn: openvpn.***.* -> it opens to the user login page (3) i edit the as.config file entry "boot_pam_users.0=" and put random characters in, so that my admin acc is not accesible if it was reset during switching of dhe network mode (2) I switch the network mode in the container to a custom proxynet (nginx setup from spaceinvader video) so that i can reach my openvpn user and admin login from anywhere (1) I've installed the openvpn-as container in bridge mode - i set up another user name (also with admin access), then login as said user and delete the standard admin user. SESSION ERROR: SESSION: Your session has expired, please reauthenticate (9007)Īnd I am at a loss of what exactly i have to do to fix it.