Dyllan2000alfa
-
Posts
4 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Dyllan2000alfa
-
-
2 hours ago, aptalca said:2 hours ago, Dyllan2000alfa said:The adress was the one unraid sent me to when I clicked web ui and it should be on the right interface as I only have one and I left everything in the unraid network setting default except for setting a static ip.
Did you include "/admin" in the address?
No
-
12 hours ago, aptalca said:13 hours ago, Dyllan2000alfa said:I have used this openvpn docker for a while but recently when i installed on a new machine and i can not access the web ui
here is the the log.[s6-init] making user provided files available at /var/run/s6/etc...exited 0.[s6-init] ensuring user provided files have correct perms...exited 0.[fix-attrs.d] applying ownership & permissions fixes...[fix-attrs.d] done.[cont-init.d] executing container initialization scripts...[cont-init.d] 10-adduser: executing...-------------------------------------_ _ _| |___| (_) ___| / __| | |/ _ \| \__ \ | | (_) ||_|___/ |_|\___/|_|Brought to you by linuxserver.ioWe gratefully accept donations at:https://www.linuxserver.io/donations/-------------------------------------GID/UID-------------------------------------User uid: 99User gid: 100-------------------------------------[cont-init.d] 10-adduser: exited 0.[cont-init.d] 20-time: executing...Current default time zone: 'America/Los_Angeles'Local time is now: Mon Aug 28 19:15:04 PDT 2017.Universal Time is now: Tue Aug 29 02:15:04 UTC 2017.[cont-init.d] 20-time: exited 0.[cont-init.d] 30-config: executing...[cont-init.d] 30-config: exited 0.[cont-init.d] 40-openvpn-init: executing...Detected an existing OpenVPN-AS configuration.Continuing will delete this configuration and restart from scratch.Please enter 'DELETE' to delete existing configuration:OpenVPN Access ServerInitial Configuration Tool------------------------------------------------------OpenVPN Access Server End User License Agreement (OpenVPN-AS EULA)1. Copyright Notice: OpenVPN Access Server License;Copyright (c) 2009-2013 OpenVPN Technologies, Inc.. All rights reserved."OpenVPN" is a trademark of OpenVPN Technologies, Inc.2. Redistribution of OpenVPN Access Server binary forms and related documents,are permitted provided that redistributions of OpenVPN Access Server binaryforms and related documents reproduce the above copyright notice as well asa complete copy of this EULA.3. You agree not to reverse engineer, decompile, disassemble, modify,translate, make any attempt to discover the source code of this software,or create derivative works from this software.4. The OpenVPN Access Server is bundled with other open source softwarecomponents, some of which fall under different licenses. By using OpenVPNor any of the bundled components, you agree to be bound by the conditionsof the license for each respective component. For more information, you canfind our complete EULA (End-User License Agreement) on our website(http://openvpn.net), and a copy of the EULA is also distributed with theAccess Server in the file /usr/local/openvpn_as/license.txt.5. This software is provided "as is" and any expressed or implied warranties,including, but not limited to, the implied warranties of merchantabilityand fitness for a particular purpose are disclaimed. In no event shallOpenVPN Technologies, Inc. be liable for any direct, indirect, incidental,special, exemplary, or consequential damages (including, but not limitedto, procurement of substitute goods or services; loss of use, data, orprofits; or business interruption) however caused and on any theory ofliability, whether in contract, strict liability, or tort (includingnegligence or otherwise) arising in any way out of the use of thissoftware, even if advised of the possibility of such damage.6. OpenVPN Technologies, Inc. is the sole distributor of OpenVPN Access Serverlicenses. This agreement and licenses granted by it may not be assigned,sublicensed, or otherwise transferred by licensee without prior writtenconsent of OpenVPN Technologies Inc. Any licenses violating this provisionwill be subject to revocation and deactivation, and will not be eligiblefor refunds.7. A purchased license entitles you to use this software for the duration oftime denoted on your license key on any one (1) particular device, up tothe concurrent user limit specified by your license. Multiple license keysmay be activated to achieve a desired concurrency limit on this givendevice. Unless otherwise prearranged with OpenVPN Technologies, Inc.,concurrency counts on license keys are not to be divided for use amongstmultiple devices. Upon activation of the first purchased license key inthis software, you agree to forego any free licenses or keys that weregiven to you for demonstration purposes, and as such, the free licenseswill not appear after the activation of a purchased key. You areresponsible for the timely activation of these licenses on your desiredserver of choice. Refunds on purchased license keys are only possiblewithin 30 days of purchase of license key, and then only if the license keyhas not already been activated on a system. To request a refund, contact usthrough our support ticket system using the account you have used topurchase the license key. Exceptions to this policy may be given formachines under failover mode, and when the feature is used as directed inthe OpenVPN Access Server user manual. In these circumstances, a user isgranted one (1) license key (per original license key) for use solely onfailover purposes free of charge. Other failover and/or load balancing usecases will not be eligible for this exception, and a separate license keywould have to be acquired to satisfy the licensing requirements. To requesta license exception, please file a support ticket in the OpenVPN AccessServer ticketing system. A staff member will be responsible for determiningexception eligibility, and we reserve the right to decline any requests notmeeting our eligibility criteria, or requests which we believe may befraudulent in nature.8. Activating a license key ties it to the specific hardware/softwarecombination that it was activated on, and activated license keys arenontransferable. Substantial software and/or hardware changes mayinvalidate an activated license. In case of substantial software and/orhardware changes, caused by for example, but not limited to failure andsubsequent repair or alterations of (virtualized) hardware/software, oursoftware product will automatically attempt to contact our online licensingsystems to renegotiate the licensing state. On any given license key, youare limited to three (3) automatic renegotiations within the license keylifetime. After these renegotiations are exhausted, the license key isconsidered invalid, and the activation state will be locked to the lastvalid system configuration it was activated on. OpenVPN Technologies, Inc.reserves the right to grant exceptions to this policy for license holdersunder extenuating circumstances, and such exceptions can be requestedthrough a ticket via the OpenVPN Access Server ticketing system.9. Once an activated license key expires or becomes invalid, the concurrencylimit on our software product will decrease by the amount of concurrentconnections previously granted by the license key. If all of your purchasedlicense key(s) have expired, the product will revert to demonstration mode,which allows a maximum of two (2) concurrent users to be connected to yourserver. Prior to your license expiration date(s), OpenVPN Technologies,Inc. will attempt to remind you to renew your license(s) by sendingperiodic email messages to the licensee email address on record. You aresolely responsible for the timely renewal of your license key(s) prior totheir expiration if continued operation is expected after the licenseexpiration date(s). OpenVPN Technologies, Inc. will not be responsible forany misdirected and/or undeliverable email messages, nor does it have anobligation to contact you regarding your expiring license keys.10. Any valid license key holder is entitled to use our ticketing system forsupport questions or issues specifically related to the OpenVPN AccessServer product. To file a ticket, go to our website at http://openvpn.net/and sign in using the account that was registered and used to purchase thelicense key(s). You can then access the support ticket system through ourwebsite and submit a support ticket. Tickets filed in the ticketing systemare answered on a best-effort basis. OpenVPN Technologies, Inc. staffreserve the right to limit responses to users of our demo / expiredlicenses, as well as requests that substantively deviate from the OpenVPNAccess Server product line. Tickets related to the open source version ofOpenVPN will not be handled here.11. Purchasing a license key does not entitle you to any special rights orprivileges, except the ones explicitly outlined in this user agreement.Unless otherwise arranged prior to your purchase with OpenVPN Technologies,Inc., software maintenance costs and terms are subject to change after yourinitial purchase without notice. In case of price decreases or specialpromotions, OpenVPN Technologies, Inc. will not retrospectively applycredits or price adjustments toward any licenses that have already beenissued. Furthermore, no discounts will be given for license maintenancerenewals unless this is specified in your contract with OpenVPNTechnologies, Inc.Please enter 'yes' to indicate your agreement [no]:Once you provide a few initial configuration settings,OpenVPN Access Server can be configured by accessingits Admin Web UI using your Web browser.Will this be the primary Access Server node?(enter 'no' to configure as a backup or standby node)> Press ENTER for default [yes]:Please specify the network interface and IP address to beused by the Admin Web UI:(1) all interfaces: 0.0.0.0(2) br0: 192.168.0.3(3) docker0: 172.17.0.1(4) virbr0: 192.168.122.1(5) bond0: 192.168.0.3(6) virbr0-nic: 192.168.122.1Please enter the option number from the list above (1-6).> Press Enter for default [2]:Please specify the port number for the Admin Web UI.> Press ENTER for default [943]:Please specify the TCP port number for the OpenVPN Daemon> Press ENTER for default [443]:Should client traffic be routed by default through the VPN?> Press ENTER for default [yes]:Should client DNS traffic be routed by default through the VPN?> Press ENTER for default [yes]:Use local authentication via internal DB?> Press ENTER for default [no]:Private subnets detected: ['192.168.0.0/24', '192.168.122.0/24', '172.17.0.0/16']Should private subnets be accessible to clients by default?> Press ENTER for default [yes]:To initially login to the Admin Web UI, you must use ausername and password that successfully authenticates youwith the host UNIX system (you can later modify the settingsso that RADIUS or LDAP is used for authentication instead).You can login to the Admin Web UI as "openvpn" or specifya different user account to use for this purpose.Do you wish to login to the Admin UI as "openvpn"?> Press ENTER for default [yes]:> Specify the username for an existing user or for the new user account: Note: This user already exists.> Please specify your OpenVPN-AS license key (or leave blank to specify later):Initializing OpenVPN...Adding new user login...useradd -s /sbin/nologin "admin"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: UNDyllanPreparing web certificates...Getting web user account...Adding web group account...Adding web group...Adjusting license directory ownership...Initializing confdb...Generating init scripts...Generating PAM config...Generating init scripts auto command...Starting openvpnas...Error: Could not execute server start.[cont-init.d] 40-openvpn-init: exited 0.[cont-init.d] 50-interface: executing...MOD Default {u'admin_ui.https.ip_address': u'all'} {u'admin_ui.https.ip_address': 'eth0'}MOD Default {u'cs.https.ip_address': u'all'} {u'cs.https.ip_address': 'eth0'}MOD Default {u'vpn.daemon.0.listen.ip_address': u'all'} {u'vpn.daemon.0.listen.ip_address': 'eth0'}MOD Default {u'vpn.daemon.0.server.ip_address': u'all'} {u'vpn.daemon.0.server.ip_address': 'eth0'}[cont-init.d] 50-interface: exited 0.[cont-init.d] done.[services.d] starting services[services.d] done.No issues in the log. Are you sure it is listening on the correct interface? What address did you try to access?
The adress was the one unraid sent me to when I clicked web ui and it should be on the right interface as I only have one and I left everything in the unraid network setting default except for setting a static ip.
-
I have used this openvpn docker for a while but recently when i installed on a new machine and i can not access the web ui
here is the the log.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-time: executing... Current default time zone: 'America/Los_Angeles' Local time is now: Mon Aug 28 19:15:04 PDT 2017. Universal Time is now: Tue Aug 29 02:15:04 UTC 2017. [cont-init.d] 20-time: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 40-openvpn-init: executing... Detected an existing OpenVPN-AS configuration. Continuing will delete this configuration and restart from scratch. Please enter 'DELETE' to delete existing configuration: OpenVPN Access Server Initial Configuration Tool ------------------------------------------------------ OpenVPN Access Server End User License Agreement (OpenVPN-AS EULA) 1. Copyright Notice: OpenVPN Access Server License; Copyright (c) 2009-2013 OpenVPN Technologies, Inc.. All rights reserved. "OpenVPN" is a trademark of OpenVPN Technologies, Inc. 2. Redistribution of OpenVPN Access Server binary forms and related documents, are permitted provided that redistributions of OpenVPN Access Server binary forms and related documents reproduce the above copyright notice as well as a complete copy of this EULA. 3. You agree not to reverse engineer, decompile, disassemble, modify, translate, make any attempt to discover the source code of this software, or create derivative works from this software. 4. The OpenVPN Access Server is bundled with other open source software components, some of which fall under different licenses. By using OpenVPN or any of the bundled components, you agree to be bound by the conditions of the license for each respective component. For more information, you can find our complete EULA (End-User License Agreement) on our website (http://openvpn.net), and a copy of the EULA is also distributed with the Access Server in the file /usr/local/openvpn_as/license.txt. 5. This software is provided "as is" and any expressed or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall OpenVPN Technologies, Inc. be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage. 6. OpenVPN Technologies, Inc. is the sole distributor of OpenVPN Access Server licenses. This agreement and licenses granted by it may not be assigned, sublicensed, or otherwise transferred by licensee without prior written consent of OpenVPN Technologies Inc. Any licenses violating this provision will be subject to revocation and deactivation, and will not be eligible for refunds. 7. A purchased license entitles you to use this software for the duration of time denoted on your license key on any one (1) particular device, up to the concurrent user limit specified by your license. Multiple license keys may be activated to achieve a desired concurrency limit on this given device. Unless otherwise prearranged with OpenVPN Technologies, Inc., concurrency counts on license keys are not to be divided for use amongst multiple devices. Upon activation of the first purchased license key in this software, you agree to forego any free licenses or keys that were given to you for demonstration purposes, and as such, the free licenses will not appear after the activation of a purchased key. You are responsible for the timely activation of these licenses on your desired server of choice. Refunds on purchased license keys are only possible within 30 days of purchase of license key, and then only if the license key has not already been activated on a system. To request a refund, contact us through our support ticket system using the account you have used to purchase the license key. Exceptions to this policy may be given for machines under failover mode, and when the feature is used as directed in the OpenVPN Access Server user manual. In these circumstances, a user is granted one (1) license key (per original license key) for use solely on failover purposes free of charge. Other failover and/or load balancing use cases will not be eligible for this exception, and a separate license key would have to be acquired to satisfy the licensing requirements. To request a license exception, please file a support ticket in the OpenVPN Access Server ticketing system. A staff member will be responsible for determining exception eligibility, and we reserve the right to decline any requests not meeting our eligibility criteria, or requests which we believe may be fraudulent in nature. 8. Activating a license key ties it to the specific hardware/software combination that it was activated on, and activated license keys are nontransferable. Substantial software and/or hardware changes may invalidate an activated license. In case of substantial software and/or hardware changes, caused by for example, but not limited to failure and subsequent repair or alterations of (virtualized) hardware/software, our software product will automatically attempt to contact our online licensing systems to renegotiate the licensing state. On any given license key, you are limited to three (3) automatic renegotiations within the license key lifetime. After these renegotiations are exhausted, the license key is considered invalid, and the activation state will be locked to the last valid system configuration it was activated on. OpenVPN Technologies, Inc. reserves the right to grant exceptions to this policy for license holders under extenuating circumstances, and such exceptions can be requested through a ticket via the OpenVPN Access Server ticketing system. 9. Once an activated license key expires or becomes invalid, the concurrency limit on our software product will decrease by the amount of concurrent connections previously granted by the license key. If all of your purchased license key(s) have expired, the product will revert to demonstration mode, which allows a maximum of two (2) concurrent users to be connected to your server. Prior to your license expiration date(s), OpenVPN Technologies, Inc. will attempt to remind you to renew your license(s) by sending periodic email messages to the licensee email address on record. You are solely responsible for the timely renewal of your license key(s) prior to their expiration if continued operation is expected after the license expiration date(s). OpenVPN Technologies, Inc. will not be responsible for any misdirected and/or undeliverable email messages, nor does it have an obligation to contact you regarding your expiring license keys. 10. Any valid license key holder is entitled to use our ticketing system for support questions or issues specifically related to the OpenVPN Access Server product. To file a ticket, go to our website at http://openvpn.net/ and sign in using the account that was registered and used to purchase the license key(s). You can then access the support ticket system through our website and submit a support ticket. Tickets filed in the ticketing system are answered on a best-effort basis. OpenVPN Technologies, Inc. staff reserve the right to limit responses to users of our demo / expired licenses, as well as requests that substantively deviate from the OpenVPN Access Server product line. Tickets related to the open source version of OpenVPN will not be handled here. 11. Purchasing a license key does not entitle you to any special rights or privileges, except the ones explicitly outlined in this user agreement. Unless otherwise arranged prior to your purchase with OpenVPN Technologies, Inc., software maintenance costs and terms are subject to change after your initial purchase without notice. In case of price decreases or special promotions, OpenVPN Technologies, Inc. will not retrospectively apply credits or price adjustments toward any licenses that have already been issued. Furthermore, no discounts will be given for license maintenance renewals unless this is specified in your contract with OpenVPN Technologies, Inc. Please enter 'yes' to indicate your agreement [no]: Once you provide a few initial configuration settings, OpenVPN Access Server can be configured by accessing its Admin Web UI using your Web browser. Will this be the primary Access Server node? (enter 'no' to configure as a backup or standby node) > Press ENTER for default [yes]: Please specify the network interface and IP address to be used by the Admin Web UI: (1) all interfaces: 0.0.0.0 (2) br0: 192.168.0.3 (3) docker0: 172.17.0.1 (4) virbr0: 192.168.122.1 (5) bond0: 192.168.0.3 (6) virbr0-nic: 192.168.122.1 Please enter the option number from the list above (1-6). > Press Enter for default [2]: Please specify the port number for the Admin Web UI. > Press ENTER for default [943]: Please specify the TCP port number for the OpenVPN Daemon > Press ENTER for default [443]: Should client traffic be routed by default through the VPN? > Press ENTER for default [yes]: Should client DNS traffic be routed by default through the VPN? > Press ENTER for default [yes]: Use local authentication via internal DB? > Press ENTER for default [no]: Private subnets detected: ['192.168.0.0/24', '192.168.122.0/24', '172.17.0.0/16'] Should private subnets be accessible to clients by default? > Press ENTER for default [yes]: To initially login to the Admin Web UI, you must use a username and password that successfully authenticates you with the host UNIX system (you can later modify the settings so that RADIUS or LDAP is used for authentication instead). You can login to the Admin Web UI as "openvpn" or specify a different user account to use for this purpose. Do you wish to login to the Admin UI as "openvpn"? > Press ENTER for default [yes]: > Specify the username for an existing user or for the new user account: Note: This user already exists. > Please specify your OpenVPN-AS license key (or leave blank to specify later): Initializing OpenVPN... Adding new user login... useradd -s /sbin/nologin "admin" 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: UNDyllan Preparing web certificates... Getting web user account... Adding web group account... Adding web group... Adjusting license directory ownership... Initializing confdb... Generating init scripts... Generating PAM config... Generating init scripts auto command... Starting openvpnas... Error: Could not execute server start. [cont-init.d] 40-openvpn-init: exited 0. [cont-init.d] 50-interface: executing... MOD Default {u'admin_ui.https.ip_address': u'all'} {u'admin_ui.https.ip_address': 'eth0'} MOD Default {u'cs.https.ip_address': u'all'} {u'cs.https.ip_address': 'eth0'} MOD Default {u'vpn.daemon.0.listen.ip_address': u'all'} {u'vpn.daemon.0.listen.ip_address': 'eth0'} MOD Default {u'vpn.daemon.0.server.ip_address': u'all'} {u'vpn.daemon.0.server.ip_address': 'eth0'} [cont-init.d] 50-interface: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done.
[Support] Linuxserver.io - OpenVPN AS
in Docker Containers
Posted
The /admin/ at the end is just to access the admin setting. Just http://<serverIP>:943 has worked before but just brought up a different ui for simple connecting and downloading profiles.