kopia lustrzana https://github.com/linuxserver/docker-documentation
Bot Updating Documentation
LinuxServer-CI
rodzic
8beb3b57ec
commit
b7d60be465
|
|
@ -1,6 +1,14 @@
|
|||
# linuxserver/openvpn-as
|
||||
# [linuxserver/openvpn-as](https://github.com/linuxserver/docker-openvpn-as)
|
||||
|
||||
[](https://github.com/linuxserver/docker-openvpn-as) [](https://github.com/linuxserver/docker-openvpn-as/releases) [](https://github.com/linuxserver/docker-openvpn-as/packages) [](https://gitlab.com/Linuxserver.io/docker-openvpn-as/container_registry) [](https://microbadger.com/images/linuxserver/openvpn-as) [](https://hub.docker.com/r/linuxserver/openvpn-as) [](https://hub.docker.com/r/linuxserver/openvpn-as) [](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-openvpn-as/job/master/) [](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/openvpn-as/latest/index.html)
|
||||
[](https://github.com/linuxserver/docker-openvpn-as)
|
||||
[](https://github.com/linuxserver/docker-openvpn-as/releases)
|
||||
[](https://github.com/linuxserver/docker-openvpn-as/packages)
|
||||
[](https://gitlab.com/Linuxserver.io/docker-openvpn-as/container_registry)
|
||||
[](https://microbadger.com/images/linuxserver/openvpn-as "Get your own version badge on microbadger.com")
|
||||
[](https://hub.docker.com/r/linuxserver/openvpn-as)
|
||||
[](https://hub.docker.com/r/linuxserver/openvpn-as)
|
||||
[](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-openvpn-as/job/master/)
|
||||
[](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/openvpn-as/latest/index.html)
|
||||
|
||||
[Openvpn-as](https://openvpn.net/index.php/access-server/overview.html) is a full featured secure network tunneling VPN software solution that integrates OpenVPN server capabilities, enterprise management capabilities, simplified OpenVPN Connect UI, and OpenVPN Client software packages that accommodate Windows, MAC, Linux, Android, and iOS environments. OpenVPN Access Server supports a wide range of configurations, including secure and granular remote access to internal network and/ or private cloud network resources and applications with fine-grained access control.
|
||||
|
||||
|
|
@ -13,7 +21,7 @@ Simply pulling `linuxserver/openvpn-as` should retrieve the correct image for yo
|
|||
The architectures supported by this image are:
|
||||
|
||||
| Architecture | Tag |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| x86-64 | latest |
|
||||
|
||||
## Version Tags
|
||||
|
|
@ -21,7 +29,7 @@ The architectures supported by this image are:
|
|||
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
|
||||
|
||||
| Tag | Description |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| latest | Stable releases based on ubuntu bionic |
|
||||
| xenial | Stable releases based on ubuntu xenial |
|
||||
|
||||
|
|
@ -31,7 +39,7 @@ Here are some example snippets to help you get started creating a container from
|
|||
|
||||
### docker
|
||||
|
||||
```text
|
||||
```
|
||||
docker create \
|
||||
--name=openvpn-as \
|
||||
--cap-add=NET_ADMIN \
|
||||
|
|
@ -47,6 +55,7 @@ docker create \
|
|||
linuxserver/openvpn-as
|
||||
```
|
||||
|
||||
|
||||
### docker-compose
|
||||
|
||||
Compatible with docker-compose v2 schemas.
|
||||
|
|
@ -76,38 +85,41 @@ services:
|
|||
|
||||
## Parameters
|
||||
|
||||
Docker images are configured using parameters passed at runtime \(such as those above\). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
|
||||
Docker images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
|
||||
|
||||
### Ports \(`-p`\)
|
||||
### Ports (`-p`)
|
||||
|
||||
| Parameter | Function |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| `943` | Admin GUI port. |
|
||||
| `9443` | TCP port. |
|
||||
| `1194/udp` | UDP port. |
|
||||
|
||||
### Environment Variables \(`-e`\)
|
||||
|
||||
### Environment Variables (`-e`)
|
||||
|
||||
| Env | Function |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| `PUID=1000` | for UserID - see below for explanation |
|
||||
| `PGID=1000` | for GroupID - see below for explanation |
|
||||
| `TZ=Europe/London` | Specify a timezone to use EG Europe/London. |
|
||||
| `INTERFACE=eth0` | With bridge networking, leave it as eth0 \(or don't include at all\), if host or macvlan, set it to your host's network interface, found by running `ifconfig` |
|
||||
| `INTERFACE=eth0` | With bridge networking, leave it as eth0 (or don't include at all), if host or macvlan, set it to your host's network interface, found by running `ifconfig` |
|
||||
|
||||
### Volume Mappings \(`-v`\)
|
||||
### Volume Mappings (`-v`)
|
||||
|
||||
| Volume | Function |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| `/config` | Where openvpn-as should store configuration files. |
|
||||
|
||||
## Environment variables from files \(Docker secrets\)
|
||||
|
||||
|
||||
## Environment variables from files (Docker secrets)
|
||||
|
||||
You can set any environment variable from a file by using a special prepend `FILE__`.
|
||||
|
||||
As an example:
|
||||
|
||||
```text
|
||||
```
|
||||
-e FILE__PASSWORD=/run/secrets/mysecretpassword
|
||||
```
|
||||
|
||||
|
|
@ -115,38 +127,44 @@ Will set the environment variable `PASSWORD` based on the contents of the `/run/
|
|||
|
||||
## Umask for running applications
|
||||
|
||||
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional `-e UMASK=022` setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up [here](https://en.wikipedia.org/wiki/Umask) before asking for support.
|
||||
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional `-e UMASK=022` setting.
|
||||
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up [here](https://en.wikipedia.org/wiki/Umask) before asking for support.
|
||||
|
||||
|
||||
## User / Group Identifiers
|
||||
|
||||
When using volumes \(`-v` flags\), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.
|
||||
When using volumes (`-v` flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.
|
||||
|
||||
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
|
||||
|
||||
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
|
||||
|
||||
```text
|
||||
```
|
||||
$ id username
|
||||
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
|
||||
```
|
||||
|
||||
## Application Setup
|
||||
|
||||
The admin interface is available at `https://DOCKER-HOST-IP:943/admin` \(assuming bridge mode\) with a default user/password of admin/password
|
||||
The admin interface is available at `https://DOCKER-HOST-IP:943/admin` (assuming bridge mode) with a default user/password of admin/password
|
||||
|
||||
During first login, make sure that the "Authentication" in the webui is set to "Local" instead of "PAM". Then set up the user accounts with their passwords \(user accounts created under PAM do not survive container update or recreation\).
|
||||
|
||||
The "admin" account is a system \(PAM\) account and after container update or recreation, its password reverts back to the default. It is highly recommended to block this user's access for security reasons: 1\) Create another user and set as an admin, 2\) Log in as the new user, 3\) Delete the "admin" user in the gui, 4\) Modify the `as.conf` file under config/etc and replace the line `boot_pam_users.0=admin` with ~~`#boot_pam_users.0=admin`~~ `boot_pam_users.0=kjhvkhv` \(this only has to be done once and will survive container recreation\)
|
||||
During first login, make sure that the "Authentication" in the webui is set to "Local" instead of "PAM". Then set up the user accounts with their passwords (user accounts created under PAM do not survive container update or recreation).
|
||||
|
||||
The "admin" account is a system (PAM) account and after container update or recreation, its password reverts back to the default. It is highly recommended to block this user's access for security reasons:
|
||||
1) Create another user and set as an admin,
|
||||
2) Log in as the new user,
|
||||
3) Delete the "admin" user in the gui,
|
||||
4) Modify the `as.conf` file under config/etc and replace the line `boot_pam_users.0=admin` with ~~`#boot_pam_users.0=admin`~~ `boot_pam_users.0=kjhvkhv` (this only has to be done once and will survive container recreation)
|
||||
* IMPORTANT NOTE: Commenting out the first pam user in as.conf creates issues in 2.7.5. To make it work while still blocking pam user access, uncomment that line and change admin to a random nonexistent user as described above.
|
||||
|
||||
To ensure your devices can connect to your VPN properly, goto Configuration -> Network Settings -> and change the "Hostname or IP Address" section to either your domain name or public ip address.
|
||||
To ensure your devices can connect to your VPN properly, goto Configuration -> Network Settings -> and change the "Hostname or IP Address" section to either your domain name or public ip address.
|
||||
|
||||
|
||||
## Docker Mods
|
||||
[](https://mods.linuxserver.io/?mod=openvpn-as "view available mods for this container.")
|
||||
|
||||
[](https://mods.linuxserver.io/?mod=openvpn-as)
|
||||
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image (if any) can be accessed via the dynamic badge above.
|
||||
|
||||
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image \(if any\) can be accessed via the dynamic badge above.
|
||||
|
||||
## Support Info
|
||||
|
||||
|
|
@ -168,7 +186,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
|
|||
* **22.08.19:** - Prevent auto-start of openvpn after first time install, before configuration is completed.
|
||||
* **25.07.19:** - Create a xenial branch/tag and rebase master/latest to bionic.
|
||||
* **07.04.19:** - Fix first time config.
|
||||
* **03.04.19:** - Big rewrite of the install and update logic of openvpn-as to fix breaking changes \(should fix updating from 2.6.1 to 2.7.3\), added mysql-client for cluster support.
|
||||
* **03.04.19:** - Big rewrite of the install and update logic of openvpn-as to fix breaking changes (should fix updating from 2.6.1 to 2.7.3), added mysql-client for cluster support.
|
||||
* **14.03.19:** - Update deb package URL.
|
||||
* **21.02.19:** - Rebase to xenial due to incompatibility issues on some older host OSes.
|
||||
* **12.02.19:** - Rename github repo to match the docker hub repo and container name.
|
||||
|
|
@ -190,4 +208,3 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
|
|||
* **28.08.16:** - Add badges to README.
|
||||
* **01.08.16:** - Rebase to xenial.
|
||||
* **18.09.15:** - Initial Release.
|
||||
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue