Amahi Wiki - User contributions [en]

Plex Media Server

2017-10-16T16:11:43Z

Beaker2382: /* Server Setup v Player Login */

{{MessageBox|backgroundcolor = #FBB|
image =Warning.png|
heading =WARNING|
message = Manually upgrading may break the Amahi 7 or greater Plex Media Server app or your HDA.

Amahi or Plex Inc. cannot provide support to help or correct any issues resulting from this upgrade if you chose to do it.}}

= Recent "White Page" Issue =
There is an issue in recent releases of the Plex Media Server app. If reaching the server yields a white page, please access it with this work-around link until (Plex fixes the issue): [http://hda:32400/web http://hda:32400/web].

= Source Install =
WARNING: This is a user contributed tutorial. Proceed with this guide at your own risk. If it breaks your HDA or you need assistance, Amahi cannot provide support.

This is a quick guide on how to install manually the PlexMediaServer (not the Amahi web app) on Amahi 7 or greater (Fedora). Find out the latest version by checking '''<nowiki>https://plex.tv/downloads</nowiki>''' and copy the link under the Fedora icon. Note that PlexPass users occassionally have access to preview versions of Plex that may contain additional functionality not yet released to other users. Use the toggle to download the preview release if you have a PlexPass.

* Install the current Plex server version from the link above, where x.x.x.x-xxxxxxx is the current version (1.2.2.2857-d34b464 at October 2017)

:64-bit
<pre>wget <nowiki>https://downloads.plex.tv/plex-media-server/x.x.x.x-xxxxxxx/plexmediaserver-x.x.x.x-xxxxxxx.x86_64.rpm</nowiki></pre>

:''Fedora 19 or older''
sudo yum localinstall plexmediaserver-x.x.x.x-xxxxxxx.x86_64.rpm

:''Fedora 21 or newer''
sudo dnf -y install plexmediaserver-x.x.x.x-xxxxxxx.x86_64.rpm

:32-bit (Amahi 7 or older '''ONLY''')
<pre>wget <nowiki>https://downloads.plex.tv/plex-media-server/x.x.x.x-xxxxxxx/plexmediaserver-x.x.x.x-xxxxxxx.i386.rpm</nowiki>
sudo yum localinstall plexmediaserver-x.x.x.x-xxxxxxx.i386.rpm</pre>

* Start the service: Next up we actually have to start Plex, the following command will do just that as well as create a symlink to always start Plex at boot.
sudo systemctl enable plexmediaserver.service && systemctl start plexmediaserver
:NOTE: If you get an error with the above command while connected to the server with SSH through a terminal, it seems you have to relogin as root.

* Run at least once the PlexMediaServer (and do nothing, just run once), from any browser in your network enter 
''<nowiki>http://localhost:32400/web/index.html#!/dashboard</nowiki>''

* Stop the PlexMediaServer (preferably log in with a terminal):
sudo systemctl stop plexmediaserver

* File permissions and access: Our first big problem (although it’s not really) is to allow Plex to access any of our files. PMS runs as it’s own user (surprisingly a user called plex), not you by default. So we need to give that user access to your files. The easiest way to do this is to add the plex user to your users group. Type the following command in a terminal:
sudo gpasswd -a plex users

* Restart the PlexMediaServer, wait 1-2 minutes and log in again to edit your libraries:
sudo systemctl start plexmediaserver

:NOTE: Don't forget if you are using Greyhole, that in this case you have always to use your files "inside" from the [[Mount_Shares_Locally|mounted local files]]

* Either by auto update (done so around midnight), or if you ask manually for updating the system, Amahi will replace the original Plex Media Server package with it's own amahi-plex (webapp). In order to prevent that you have to exclude the auto-update in the Amahi repo. Edit (as root) ''/etc/yum/yum.conf'' (Amahi 8 older) or ''/etc/dnf/dnf.conf'' (Amahi 9 or newer) and add the following at the bottom:
exclude=amahi-plex

= Use with Greyhole =
If you add a library section connected to a folder that is part of your drive pool and thus handled by [[Greyhole]], you should NOT check the option to allow clients to delete media in the Plex Media Server preferences dialog.

If you want to enable this feature you should [[Mount_Shares_Locally|mount your shares locally]] on your HDA and point [http://www.amahi.org/apps/plex-media-server Plex Media Server] to these mount points instead. Otherwise deletes could cause orphan files in the storage pool since only the symlink would actually be deleted and not the actual file.

= Locally Mounted Shares (Ubuntu ONLY) =
If you access your media files using [https://wiki.amahi.org/index.php/Mount_Shares_Locally locally mounted shares] (eg if you are a [https://wiki.amahi.org/index.php/Greyhole Greyhole] user as suggested above), you will need to change the permissions of your plex server user. The Plex Media Server is run by a special user plex who doesnt have access to the local shares by default.

To fix, open terminal as root user and type:
sudo usermod -a -G users plex

You may need to restart Plex. Now when you want to add directories using the web interface all your shares should be accessible.

= Update Plex Media Server =

* If you have installed manually by source the PlexMediaServer, it now has the ability to update itself through the settings' webpage

* If you are using amahi-plex it will auto update itself as so as the developers push the new version into Amahi's repo. Don't try to update the amahi-plex web app although in the setting's webpage it will inform you that a new version of Plex Media Server is available. Most likely it will fail or it will break your system!

= Troubleshooting =

== Server Setup v Player Login ==
After install the Plex server still needs to be configured and logged into a [http://www.plex.tv Plex.tv] account. Before the Plex server has been named properly, going to [//plexms.amahi.net //PlexMS.Amahi.Net] from your LAN will bring you to a Plex.tv login then redirect you to a player-only page. To get around this, visit your [HDA's static IP]:32400/web/
example: 192.168.0.1:32400/web/ 
This should bring you to the same log in page, but redirect you to the server setup.

The default server name is LocalHostLocalDomain, change this to PlexMS. Now the address [//plexms.amahi.net //PlexMS.Amahi.Net] should bring you to the server page (with player too).

Also, visiting your Dynamic DNS name followed by port 32400 (example.yourhda.com:32400) will bring you to a player from anywhere on the internet. Port forwarding is required at your router's firewall.

== Data not shown with Main page login ==

We noticed that when logging in to <nowiki>http://plexms/</nowiki> plex does not seem to list any data from the plex server, allow you to set up libraries, or allow logins going through this front-door. It does not seem to "be able to connect to this server" on the left side. However, going through <nowiki>http://hda:32400/web/index.html</nowiki> it all works well.

The work-around is this: going to
<nowiki>http://hda:32400/web/index.html#!/settings/server/</nowiki>
Then login to plex on this page and give it a friendly name there."My Amahi server" or similar should do.

After that, it should show up under <nowiki>http://plexms/</nowiki>.

== Dashboard Link Workaround ==
If the launch icon and link for Plex Media Server in the dashboard does not properly load the server, you may need to try a workaround.

First, try just restarting httpd.This should hold for as long as your server is running.
systemctl restart httpd

If that does not work, or you are restarting your server often, this longer workaround also works.
Start by finding your ####-plexms.conf file in /etc/httpd/conf.d/ Open this file up in a text editor like vi or nano and remove (or comment out) the following two lines:

ProxyPass / <nowiki>http://hda:32400/web/</nowiki>
ProxyPassReverse / <nowiki>http://hda:32400/web/</nowiki>

Option 1 
:Add the following three lines below the two you commented out above:
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule (.*) <nowiki>http://%{HTTP_HOST}:32400/web/</nowiki> [R,L]

:After completing the changes, restart httpd
systemctl restart httpd

Option 2 
:Create a text file called "index.html" and save that file in /var/hda/web-apps/plexms/html The contents of the file is a simple redirect. It should read:

<html>
<head><meta http-equiv="refresh" content="0; url=<nowiki>http://hda:32400/web/</nowiki>" />
</head>
<body></body></hmtl>

:Set the file ownership permissions:
chown apache:users index.html;

The Plex Media server page should now load when you click on the icon or link in the dashboard.

== Looking For Servers ==
Can logon to the app, but displays "Looking for Servers" is the top left corner of screen.

Some users have reported that accessing the app by IP address resolves this issue.

[[Category:apps]]

Plex Media Server

2017-10-16T16:10:53Z

Beaker2382: /* Server Setup v Player Login */

{{MessageBox|backgroundcolor = #FBB|
image =Warning.png|
heading =WARNING|
message = Manually upgrading may break the Amahi 7 or greater Plex Media Server app or your HDA.

Amahi or Plex Inc. cannot provide support to help or correct any issues resulting from this upgrade if you chose to do it.}}

= Recent "White Page" Issue =
There is an issue in recent releases of the Plex Media Server app. If reaching the server yields a white page, please access it with this work-around link until (Plex fixes the issue): [http://hda:32400/web http://hda:32400/web].

= Source Install =
WARNING: This is a user contributed tutorial. Proceed with this guide at your own risk. If it breaks your HDA or you need assistance, Amahi cannot provide support.

This is a quick guide on how to install manually the PlexMediaServer (not the Amahi web app) on Amahi 7 or greater (Fedora). Find out the latest version by checking '''<nowiki>https://plex.tv/downloads</nowiki>''' and copy the link under the Fedora icon. Note that PlexPass users occassionally have access to preview versions of Plex that may contain additional functionality not yet released to other users. Use the toggle to download the preview release if you have a PlexPass.

* Install the current Plex server version from the link above, where x.x.x.x-xxxxxxx is the current version (1.2.2.2857-d34b464 at October 2017)

:64-bit
<pre>wget <nowiki>https://downloads.plex.tv/plex-media-server/x.x.x.x-xxxxxxx/plexmediaserver-x.x.x.x-xxxxxxx.x86_64.rpm</nowiki></pre>

:''Fedora 19 or older''
sudo yum localinstall plexmediaserver-x.x.x.x-xxxxxxx.x86_64.rpm

:''Fedora 21 or newer''
sudo dnf -y install plexmediaserver-x.x.x.x-xxxxxxx.x86_64.rpm

:32-bit (Amahi 7 or older '''ONLY''')
<pre>wget <nowiki>https://downloads.plex.tv/plex-media-server/x.x.x.x-xxxxxxx/plexmediaserver-x.x.x.x-xxxxxxx.i386.rpm</nowiki>
sudo yum localinstall plexmediaserver-x.x.x.x-xxxxxxx.i386.rpm</pre>

* Start the service: Next up we actually have to start Plex, the following command will do just that as well as create a symlink to always start Plex at boot.
sudo systemctl enable plexmediaserver.service && systemctl start plexmediaserver
:NOTE: If you get an error with the above command while connected to the server with SSH through a terminal, it seems you have to relogin as root.

* Run at least once the PlexMediaServer (and do nothing, just run once), from any browser in your network enter 
''<nowiki>http://localhost:32400/web/index.html#!/dashboard</nowiki>''

* Stop the PlexMediaServer (preferably log in with a terminal):
sudo systemctl stop plexmediaserver

* File permissions and access: Our first big problem (although it’s not really) is to allow Plex to access any of our files. PMS runs as it’s own user (surprisingly a user called plex), not you by default. So we need to give that user access to your files. The easiest way to do this is to add the plex user to your users group. Type the following command in a terminal:
sudo gpasswd -a plex users

* Restart the PlexMediaServer, wait 1-2 minutes and log in again to edit your libraries:
sudo systemctl start plexmediaserver

:NOTE: Don't forget if you are using Greyhole, that in this case you have always to use your files "inside" from the [[Mount_Shares_Locally|mounted local files]]

* Either by auto update (done so around midnight), or if you ask manually for updating the system, Amahi will replace the original Plex Media Server package with it's own amahi-plex (webapp). In order to prevent that you have to exclude the auto-update in the Amahi repo. Edit (as root) ''/etc/yum/yum.conf'' (Amahi 8 older) or ''/etc/dnf/dnf.conf'' (Amahi 9 or newer) and add the following at the bottom:
exclude=amahi-plex

= Use with Greyhole =
If you add a library section connected to a folder that is part of your drive pool and thus handled by [[Greyhole]], you should NOT check the option to allow clients to delete media in the Plex Media Server preferences dialog.

If you want to enable this feature you should [[Mount_Shares_Locally|mount your shares locally]] on your HDA and point [http://www.amahi.org/apps/plex-media-server Plex Media Server] to these mount points instead. Otherwise deletes could cause orphan files in the storage pool since only the symlink would actually be deleted and not the actual file.

= Locally Mounted Shares (Ubuntu ONLY) =
If you access your media files using [https://wiki.amahi.org/index.php/Mount_Shares_Locally locally mounted shares] (eg if you are a [https://wiki.amahi.org/index.php/Greyhole Greyhole] user as suggested above), you will need to change the permissions of your plex server user. The Plex Media Server is run by a special user plex who doesnt have access to the local shares by default.

To fix, open terminal as root user and type:
sudo usermod -a -G users plex

You may need to restart Plex. Now when you want to add directories using the web interface all your shares should be accessible.

= Update Plex Media Server =

* If you have installed manually by source the PlexMediaServer, it now has the ability to update itself through the settings' webpage

* If you are using amahi-plex it will auto update itself as so as the developers push the new version into Amahi's repo. Don't try to update the amahi-plex web app although in the setting's webpage it will inform you that a new version of Plex Media Server is available. Most likely it will fail or it will break your system!

= Troubleshooting =

== Server Setup v Player Login ==
After install the Plex server still needs to be configured and logged into a [http://www.plex.tv Plex.tv] account. Before the Plex server has been named properly, going to [//plexms.amahi.net //PlexMS.Amahi.Net] from your LAN will bring you to a Plex.tv login then redirect you to a player-only page. To get around this, visit your [HDA's static IP]:32400/web/
example: 192.168.0.1:32400/web/ 
This should bring you to the same log in page, but redirect you to the server setup.

The default server name is LocalHostLocalDomain, change this to PlexMS. Now the address [//plexms.amahi.net //PlexMS.Amahi.Net] should bring you to server page (with player too).

Also, visiting your Dynamic DNS name followed by port 32400 (example.yourhda.com:32400) will bring you to a player from anywhere on the internet. Port forwarding is required at your router's firewall.

== Data not shown with Main page login ==

We noticed that when logging in to <nowiki>http://plexms/</nowiki> plex does not seem to list any data from the plex server, allow you to set up libraries, or allow logins going through this front-door. It does not seem to "be able to connect to this server" on the left side. However, going through <nowiki>http://hda:32400/web/index.html</nowiki> it all works well.

The work-around is this: going to
<nowiki>http://hda:32400/web/index.html#!/settings/server/</nowiki>
Then login to plex on this page and give it a friendly name there."My Amahi server" or similar should do.

After that, it should show up under <nowiki>http://plexms/</nowiki>.

== Dashboard Link Workaround ==
If the launch icon and link for Plex Media Server in the dashboard does not properly load the server, you may need to try a workaround.

First, try just restarting httpd.This should hold for as long as your server is running.
systemctl restart httpd

If that does not work, or you are restarting your server often, this longer workaround also works.
Start by finding your ####-plexms.conf file in /etc/httpd/conf.d/ Open this file up in a text editor like vi or nano and remove (or comment out) the following two lines:

ProxyPass / <nowiki>http://hda:32400/web/</nowiki>
ProxyPassReverse / <nowiki>http://hda:32400/web/</nowiki>

Option 1 
:Add the following three lines below the two you commented out above:
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule (.*) <nowiki>http://%{HTTP_HOST}:32400/web/</nowiki> [R,L]

:After completing the changes, restart httpd
systemctl restart httpd

Option 2 
:Create a text file called "index.html" and save that file in /var/hda/web-apps/plexms/html The contents of the file is a simple redirect. It should read:

<html>
<head><meta http-equiv="refresh" content="0; url=<nowiki>http://hda:32400/web/</nowiki>" />
</head>
<body></body></hmtl>

:Set the file ownership permissions:
chown apache:users index.html;

The Plex Media server page should now load when you click on the icon or link in the dashboard.

== Looking For Servers ==
Can logon to the app, but displays "Looking for Servers" is the top left corner of screen.

Some users have reported that accessing the app by IP address resolves this issue.

[[Category:apps]]

Plex Media Server

2017-10-16T16:08:07Z

Beaker2382: /* Server Setup v Player Login */

{{MessageBox|backgroundcolor = #FBB|
image =Warning.png|
heading =WARNING|
message = Manually upgrading may break the Amahi 7 or greater Plex Media Server app or your HDA.

Amahi or Plex Inc. cannot provide support to help or correct any issues resulting from this upgrade if you chose to do it.}}

= Recent "White Page" Issue =
There is an issue in recent releases of the Plex Media Server app. If reaching the server yields a white page, please access it with this work-around link until (Plex fixes the issue): [http://hda:32400/web http://hda:32400/web].

= Source Install =
WARNING: This is a user contributed tutorial. Proceed with this guide at your own risk. If it breaks your HDA or you need assistance, Amahi cannot provide support.

This is a quick guide on how to install manually the PlexMediaServer (not the Amahi web app) on Amahi 7 or greater (Fedora). Find out the latest version by checking '''<nowiki>https://plex.tv/downloads</nowiki>''' and copy the link under the Fedora icon. Note that PlexPass users occassionally have access to preview versions of Plex that may contain additional functionality not yet released to other users. Use the toggle to download the preview release if you have a PlexPass.

* Install the current Plex server version from the link above, where x.x.x.x-xxxxxxx is the current version (1.2.2.2857-d34b464 at October 2017)

:64-bit
<pre>wget <nowiki>https://downloads.plex.tv/plex-media-server/x.x.x.x-xxxxxxx/plexmediaserver-x.x.x.x-xxxxxxx.x86_64.rpm</nowiki></pre>

:''Fedora 19 or older''
sudo yum localinstall plexmediaserver-x.x.x.x-xxxxxxx.x86_64.rpm

:''Fedora 21 or newer''
sudo dnf -y install plexmediaserver-x.x.x.x-xxxxxxx.x86_64.rpm

:32-bit (Amahi 7 or older '''ONLY''')
<pre>wget <nowiki>https://downloads.plex.tv/plex-media-server/x.x.x.x-xxxxxxx/plexmediaserver-x.x.x.x-xxxxxxx.i386.rpm</nowiki>
sudo yum localinstall plexmediaserver-x.x.x.x-xxxxxxx.i386.rpm</pre>

* Start the service: Next up we actually have to start Plex, the following command will do just that as well as create a symlink to always start Plex at boot.
sudo systemctl enable plexmediaserver.service && systemctl start plexmediaserver
:NOTE: If you get an error with the above command while connected to the server with SSH through a terminal, it seems you have to relogin as root.

* Run at least once the PlexMediaServer (and do nothing, just run once), from any browser in your network enter 
''<nowiki>http://localhost:32400/web/index.html#!/dashboard</nowiki>''

* Stop the PlexMediaServer (preferably log in with a terminal):
sudo systemctl stop plexmediaserver

* File permissions and access: Our first big problem (although it’s not really) is to allow Plex to access any of our files. PMS runs as it’s own user (surprisingly a user called plex), not you by default. So we need to give that user access to your files. The easiest way to do this is to add the plex user to your users group. Type the following command in a terminal:
sudo gpasswd -a plex users

* Restart the PlexMediaServer, wait 1-2 minutes and log in again to edit your libraries:
sudo systemctl start plexmediaserver

:NOTE: Don't forget if you are using Greyhole, that in this case you have always to use your files "inside" from the [[Mount_Shares_Locally|mounted local files]]

* Either by auto update (done so around midnight), or if you ask manually for updating the system, Amahi will replace the original Plex Media Server package with it's own amahi-plex (webapp). In order to prevent that you have to exclude the auto-update in the Amahi repo. Edit (as root) ''/etc/yum/yum.conf'' (Amahi 8 older) or ''/etc/dnf/dnf.conf'' (Amahi 9 or newer) and add the following at the bottom:
exclude=amahi-plex

= Use with Greyhole =
If you add a library section connected to a folder that is part of your drive pool and thus handled by [[Greyhole]], you should NOT check the option to allow clients to delete media in the Plex Media Server preferences dialog.

If you want to enable this feature you should [[Mount_Shares_Locally|mount your shares locally]] on your HDA and point [http://www.amahi.org/apps/plex-media-server Plex Media Server] to these mount points instead. Otherwise deletes could cause orphan files in the storage pool since only the symlink would actually be deleted and not the actual file.

= Locally Mounted Shares (Ubuntu ONLY) =
If you access your media files using [https://wiki.amahi.org/index.php/Mount_Shares_Locally locally mounted shares] (eg if you are a [https://wiki.amahi.org/index.php/Greyhole Greyhole] user as suggested above), you will need to change the permissions of your plex server user. The Plex Media Server is run by a special user plex who doesnt have access to the local shares by default.

To fix, open terminal as root user and type:
sudo usermod -a -G users plex

You may need to restart Plex. Now when you want to add directories using the web interface all your shares should be accessible.

= Update Plex Media Server =

* If you have installed manually by source the PlexMediaServer, it now has the ability to update itself through the settings' webpage

* If you are using amahi-plex it will auto update itself as so as the developers push the new version into Amahi's repo. Don't try to update the amahi-plex web app although in the setting's webpage it will inform you that a new version of Plex Media Server is available. Most likely it will fail or it will break your system!

= Troubleshooting =

== Server Setup v Player Login ==
After install the Plex server still needs to be configured and logged into a [http://www.plex.tv Plex.tv] account. Before the Plex server has been named properly, going to plexms.amahi.net (from LAN, not internet) will bring you to a Plex.tv login then redirect you to a player-only page. To get around this, visit your [HDA's static IP]:32400/web/
example: 192.168.0.1:32400/web/ 
This should bring you to the same log in page, but redirect you to the server setup.

The default server name is LocalHostLocalDomain, change this to PlexMS. Now the address [//plexms.amahi.net //PlexMS.Amahi.Net] should bring you to server page (with player too).

Also, visiting your Dynamic DNS name followed by port 32400 (example.yourhda.com:32400) will bring you to a player from anywhere on the internet. Port forwarding is required at your router's firewall.

== Data not shown with Main page login ==

We noticed that when logging in to <nowiki>http://plexms/</nowiki> plex does not seem to list any data from the plex server, allow you to set up libraries, or allow logins going through this front-door. It does not seem to "be able to connect to this server" on the left side. However, going through <nowiki>http://hda:32400/web/index.html</nowiki> it all works well.

The work-around is this: going to
<nowiki>http://hda:32400/web/index.html#!/settings/server/</nowiki>
Then login to plex on this page and give it a friendly name there."My Amahi server" or similar should do.

After that, it should show up under <nowiki>http://plexms/</nowiki>.

== Dashboard Link Workaround ==
If the launch icon and link for Plex Media Server in the dashboard does not properly load the server, you may need to try a workaround.

First, try just restarting httpd.This should hold for as long as your server is running.
systemctl restart httpd

If that does not work, or you are restarting your server often, this longer workaround also works.
Start by finding your ####-plexms.conf file in /etc/httpd/conf.d/ Open this file up in a text editor like vi or nano and remove (or comment out) the following two lines:

ProxyPass / <nowiki>http://hda:32400/web/</nowiki>
ProxyPassReverse / <nowiki>http://hda:32400/web/</nowiki>

Option 1 
:Add the following three lines below the two you commented out above:
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule (.*) <nowiki>http://%{HTTP_HOST}:32400/web/</nowiki> [R,L]

:After completing the changes, restart httpd
systemctl restart httpd

Option 2 
:Create a text file called "index.html" and save that file in /var/hda/web-apps/plexms/html The contents of the file is a simple redirect. It should read:

<html>
<head><meta http-equiv="refresh" content="0; url=<nowiki>http://hda:32400/web/</nowiki>" />
</head>
<body></body></hmtl>

:Set the file ownership permissions:
chown apache:users index.html;

The Plex Media server page should now load when you click on the icon or link in the dashboard.

== Looking For Servers ==
Can logon to the app, but displays "Looking for Servers" is the top left corner of screen.

Some users have reported that accessing the app by IP address resolves this issue.

[[Category:apps]]

Plex Media Server

2017-10-16T15:06:34Z

Beaker2382: /* Troubleshooting */

{{MessageBox|backgroundcolor = #FBB|
image =Warning.png|
heading =WARNING|
message = Manually upgrading may break the Amahi 7 or greater Plex Media Server app or your HDA.

Amahi or Plex Inc. cannot provide support to help or correct any issues resulting from this upgrade if you chose to do it.}}

= Recent "White Page" Issue =
There is an issue in recent releases of the Plex Media Server app. If reaching the server yields a white page, please access it with this work-around link until (Plex fixes the issue): [http://hda:32400/web http://hda:32400/web].

= Source Install =
WARNING: This is a user contributed tutorial. Proceed with this guide at your own risk. If it breaks your HDA or you need assistance, Amahi cannot provide support.

This is a quick guide on how to install manually the PlexMediaServer (not the Amahi web app) on Amahi 7 or greater (Fedora). Find out the latest version by checking '''<nowiki>https://plex.tv/downloads</nowiki>''' and copy the link under the Fedora icon. Note that PlexPass users occassionally have access to preview versions of Plex that may contain additional functionality not yet released to other users. Use the toggle to download the preview release if you have a PlexPass.

* Install the current Plex server version from the link above, where x.x.x.x-xxxxxxx is the current version (1.2.2.2857-d34b464 at October 2017)

:64-bit
<pre>wget <nowiki>https://downloads.plex.tv/plex-media-server/x.x.x.x-xxxxxxx/plexmediaserver-x.x.x.x-xxxxxxx.x86_64.rpm</nowiki></pre>

:''Fedora 19 or older''
sudo yum localinstall plexmediaserver-x.x.x.x-xxxxxxx.x86_64.rpm

:''Fedora 21 or newer''
sudo dnf -y install plexmediaserver-x.x.x.x-xxxxxxx.x86_64.rpm

:32-bit (Amahi 7 or older '''ONLY''')
<pre>wget <nowiki>https://downloads.plex.tv/plex-media-server/x.x.x.x-xxxxxxx/plexmediaserver-x.x.x.x-xxxxxxx.i386.rpm</nowiki>
sudo yum localinstall plexmediaserver-x.x.x.x-xxxxxxx.i386.rpm</pre>

* Start the service: Next up we actually have to start Plex, the following command will do just that as well as create a symlink to always start Plex at boot.
sudo systemctl enable plexmediaserver.service && systemctl start plexmediaserver
:NOTE: If you get an error with the above command while connected to the server with SSH through a terminal, it seems you have to relogin as root.

* Run at least once the PlexMediaServer (and do nothing, just run once), from any browser in your network enter 
''<nowiki>http://localhost:32400/web/index.html#!/dashboard</nowiki>''

* Stop the PlexMediaServer (preferably log in with a terminal):
sudo systemctl stop plexmediaserver

* File permissions and access: Our first big problem (although it’s not really) is to allow Plex to access any of our files. PMS runs as it’s own user (surprisingly a user called plex), not you by default. So we need to give that user access to your files. The easiest way to do this is to add the plex user to your users group. Type the following command in a terminal:
sudo gpasswd -a plex users

* Restart the PlexMediaServer, wait 1-2 minutes and log in again to edit your libraries:
sudo systemctl start plexmediaserver

:NOTE: Don't forget if you are using Greyhole, that in this case you have always to use your files "inside" from the [[Mount_Shares_Locally|mounted local files]]

* Either by auto update (done so around midnight), or if you ask manually for updating the system, Amahi will replace the original Plex Media Server package with it's own amahi-plex (webapp). In order to prevent that you have to exclude the auto-update in the Amahi repo. Edit (as root) ''/etc/yum/yum.conf'' (Amahi 8 older) or ''/etc/dnf/dnf.conf'' (Amahi 9 or newer) and add the following at the bottom:
exclude=amahi-plex

= Use with Greyhole =
If you add a library section connected to a folder that is part of your drive pool and thus handled by [[Greyhole]], you should NOT check the option to allow clients to delete media in the Plex Media Server preferences dialog.

If you want to enable this feature you should [[Mount_Shares_Locally|mount your shares locally]] on your HDA and point [http://www.amahi.org/apps/plex-media-server Plex Media Server] to these mount points instead. Otherwise deletes could cause orphan files in the storage pool since only the symlink would actually be deleted and not the actual file.

= Locally Mounted Shares (Ubuntu ONLY) =
If you access your media files using [https://wiki.amahi.org/index.php/Mount_Shares_Locally locally mounted shares] (eg if you are a [https://wiki.amahi.org/index.php/Greyhole Greyhole] user as suggested above), you will need to change the permissions of your plex server user. The Plex Media Server is run by a special user plex who doesnt have access to the local shares by default.

To fix, open terminal as root user and type:
sudo usermod -a -G users plex

You may need to restart Plex. Now when you want to add directories using the web interface all your shares should be accessible.

= Update Plex Media Server =

* If you have installed manually by source the PlexMediaServer, it now has the ability to update itself through the settings' webpage

* If you are using amahi-plex it will auto update itself as so as the developers push the new version into Amahi's repo. Don't try to update the amahi-plex web app although in the setting's webpage it will inform you that a new version of Plex Media Server is available. Most likely it will fail or it will break your system!

= Troubleshooting =

== Server Setup v Player Login ==
After install Plex server still needs to be configured and logged into a [[www.plex.tv Plex.tv]] account. Before the Plex server has been named properly, going to plexms.amahi.net (from LAN, not internet) will bring you to a Plex.tv login then redirect you to a player-only page. To get around this, visit your [HDA's static IP]:32400/web/ . This should bring you to the same log in page, but redirect you to the server setup. Default Server name is LocalHostLocalDomain, change this to PlexMS. Now the address [[plexms.amahi.net]] should bring you to server page (with player too).

Also, visiting your Dynamic DNS name followed by port 32400 (example.yourhda.com:32400) will bring you to a player from anywhere on the internet. Port forwarding is required at your router's firewall.

== Data not shown with Main page login ==

We noticed that when logging in to <nowiki>http://plexms/</nowiki> plex does not seem to list any data from the plex server, allow you to set up libraries, or allow logins going through this front-door. It does not seem to "be able to connect to this server" on the left side. However, going through <nowiki>http://hda:32400/web/index.html</nowiki> it all works well.

The work-around is this: going to
<nowiki>http://hda:32400/web/index.html#!/settings/server/</nowiki>
Then login to plex on this page and give it a friendly name there."My Amahi server" or similar should do.

After that, it should show up under <nowiki>http://plexms/</nowiki>.

== Dashboard Link Workaround ==
If the launch icon and link for Plex Media Server in the dashboard does not properly load the server, you may need to try a workaround.

First, try just restarting httpd.This should hold for as long as your server is running.
systemctl restart httpd

If that does not work, or you are restarting your server often, this longer workaround also works.
Start by finding your ####-plexms.conf file in /etc/httpd/conf.d/ Open this file up in a text editor like vi or nano and remove (or comment out) the following two lines:

ProxyPass / <nowiki>http://hda:32400/web/</nowiki>
ProxyPassReverse / <nowiki>http://hda:32400/web/</nowiki>

Option 1 
:Add the following three lines below the two you commented out above:
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule (.*) <nowiki>http://%{HTTP_HOST}:32400/web/</nowiki> [R,L]

:After completing the changes, restart httpd
systemctl restart httpd

Option 2 
:Create a text file called "index.html" and save that file in /var/hda/web-apps/plexms/html The contents of the file is a simple redirect. It should read:

<html>
<head><meta http-equiv="refresh" content="0; url=<nowiki>http://hda:32400/web/</nowiki>" />
</head>
<body></body></hmtl>

:Set the file ownership permissions:
chown apache:users index.html;

The Plex Media server page should now load when you click on the icon or link in the dashboard.

== Looking For Servers ==
Can logon to the app, but displays "Looking for Servers" is the top left corner of screen.

Some users have reported that accessing the app by IP address resolves this issue.

[[Category:apps]]

VPNAndroid

2017-10-16T14:15:50Z

Beaker2382: /* OpenVPN for Android Client Configuration */

{{NeedsUpdate}}


=OpenVPN for Android Client Configuration=
This wiki has been updated for use with OpenVPN for Android v0.6.73 without Android Root access. Older versions of the wiki are maintained below.

It is presumed that you have installed the [http://www.amahi.org/apps/openvpn OpenVPN] server app on your HDA and [https://wiki.amahi.org/index.php/OpenVPN configured] it properly.

# Download the (3) certificate files. They can be found on the [[OpenVPN Client Certificates]] download page.
##If downloading from link above directly to Android Device, Google translate may ask if you wish to translate the document, DO NOT allow any translation to occur.
##If downloading to a computer first, the key is often downloaded as xxx.key.txt. You must remove the .txt extension.
# Launch the OpenVPN app, select Add Profile (+), give it a name and it will bring you to the Basic configuration tab [[File:NoVPNDefined.png | 180px]][[File:AddProfile.png | 180px]]
# In the Basic tab, Select "User/PW + Certificates" from the pull down menu of Types [[File:TypeAndCerts.png | 180px]]
# In turn, select the CA Certificate, Client Certificate and Client Key files that you downloaded to your device [[File:CertsAdded.png | 180px]]
# Username refers to a configured User of the Amahi server you are trying to connect to. Leave password field empty to be prompted to enter a password every time.
#Swipe left or right to change tabs in the Configuration page or select them directly from the tab bar.
#From the Server List tab, enter your server Dynamic DNS name found on the [http://www.amahi.org Control Panel] - xxx.yourhda.com [[File:serverDNSname.png | 180px]]
#From the Authentication/Encryption tab, select Remote Certificate Subject and look closely for the pull down arrow in the open window, select RDN Prefix [[File:SubjectPulldown.png | 180px]]
#In the Remote Certificate Subject box change the data field to read Amahi-Server-OpenVPN [[File:HostnameSubject.png | 180px]]
#Configuration is complete, hit the android device's back button to return to the OpenVPN main screen. This will show your new profile, and if you are NOT connected to your local network (turn off Wi-Fi and use cellular data), you will be able to select your profile and it will connect. A secure connection will be shown as a key symbol next to the cellular signal strength bar.

 

= VPN Client - Android - HTC Android G1/Dream =

'''NOTE:''' [https://play.google.com/store/apps/details?id=de.blinkt.openvpn&hl=en OpenVPN for Android] works with the certificates below for ICS 4.0 or greater without rooting your device. There is no additional configuration required to the HDA or your device (Tested on HTC One X and Samsung Tab 2 also on HTC One V). For Sony Xperia ZR (and I suspect most other Android devices) the following was necessary:

# Download the certificates. They can be found on the [[OpenVPN Client Certificates]] download page.
# Launch the OpenVPN app, Add Profile and go to the Basic configuration page [[File:OpenVPNAndroid-1-AddProfile.png|180px]] [[File:OpenVPNAndroid-2-ChooseBasic.png|180px]]
# Enter your server address - the Dynamic DNS name works for me, I guess the fixed IP address would as well [[File:OpenVPNAndroid-3-EnterServerAddress.png|180px]]
# Select "User/PW + Certificates" from the list of Types (the certificates alone are not enough) [[File:OpenVPNAndroid-4-SelectType.png|180px]] [[File:OpenVPNAndroid-5-SelectedType.png|180px]]
# In turn, select the CA Certificate, Client Certificate and Client Key files that you downloaded to your device; note that the app will disable the file type it doesn't think will work so beware if you rename these files [[File:OpenVPNAndroid-6-SelectCertKey.png|180px]]
# Enter your username - a general user with access to the shares and apps on your HDA [[File:OpenVPNAndroid-7-EnterUsername.png|180px]]
# Go back to the list of profiles and click on this new profile to start connecting to your HDA: you will be alerted to the fact that OpenVPN for Android can intercept network traffic and asked to trust the application (ensure that your device is not already connected to the same network - test from a different location or turn of wifi and use your mobile data connection) [[File:OpenVPNAndroid-8-TrustApplication.png|180px]]
# Enter your password - you can decide whether or not the application should save the password [[File:OpenVPNAndroid-9-EnterPassword.png|180px]]
# Watch for connection messages to go past as Android notifications and you will also see the OpenVPN log [[File:OpenVPNAndroid-A-Connecting.png|180px]]
# Once you get a successful connection you will see a key in the notification bar; selecting this notification will show the status of the connection ind give you some options for working with it [[File:OpenVPNAndroid-B-Connected.png|180px]]
# You should now be able to open your favourite app used to access files on your HDA, be that the Amahi app, Plex client, OwnCloud, etc. (note that some of these apps may need to be switched between Local and Remote connection type)

This guide is written for a HTC Android G1/Dream phone rooted with Cyanongenmod 5.

[update March 24, 2011: Tested and works with Cyanogenmod 7.0, thus any CM7 compatible phone]

[update August 8, 2011: Tested and works with Cyanogenmod 7.1, thus any CM 7.1 compatible phone]

[update September 9, 2011: Tested and works with MIUI 1.9.2 on a HTC Droid Incredible 2, should work on any MIUI ROM]

[update 22 March 2013: Tested and works with Android 4.2.2 on Nexus Devices]

In your Linux-based OS computer..

Download the certificates. They can be found on the [[OpenVPN Client Certificates]] download page. Save them in your /home/username/openvpn folder (where ''username'' is your main users name).

Then, from the terminal run

cd /home/username/openvpn
openssl pkcs12 -export -in Amahi-Client-OpenVPN.crt -inkey Amahi-Client-OpenVPN.key -certfile ca.crt -name Amahi -out certs.p12

You will be asked for a export password for the certs.p12 file - enter amahi twice.

To automate this process, paste the code from [http://wiki.amahi.org/images/f/f9/Automate.script automate.script] in your favorite editor. Save it & run it with
sh <filename>

You should now have a certs.p12 file in your /home/username/openvpn folder, copy this certs.p12 file to the root of your sdcard on the Android phone.

Now on the Android phone..

<pre><nowiki>
Menu -> Settings -> Location & Security -> Install from SD card
</nowiki></pre>

This will show you certs.p12, select this and enter the password amahi, after it has extracted the certificates, you will be asked to name the certificate, enter Amahi.

Now on the Android phone

<pre><nowiki>
Menu -> Settings -> Wireless & networks -> VPN settings -> Add VPN -> Add OpenVPN VPN
</nowiki></pre>

VPN name = Amahi

Set VPN server = yourHDAnickname.yourhda.com

User authentication = Yes

Set CA certificate - Amahi

Set user certificate - Amahi

Menu -> Advanced -> LZO compression = Yes

Back

Menu -> Save

You should now see an Amahi entry, click on this to connect. It may ask you for the certificate access password. Then it may ask for your username and password that you use to loginon your HDA. You should see that you are connected, enjoy your VPN connection to your HDA server.

= VPN Client - Android 2.2 - DROID X (Verizon Wireless) =
Contact me in the forums if you need help setting this up. If you have a later version of Android such as Gingerbread (Android 2.3) then you can't use this tutorial for setting up openvpn. You can however use the openvpn configurations if your phone is already set up with openvpn.

[[User:Sag47|Sag47]] 00:51, 5 April 2011 (PDT)

This tutorial is not for the feeble minded. I tried writing it as best as I could to keep it a "How to VPN" article and not a "How to root my droid" topic.

The default Droid X from Verizon does not come with openvpn installed. It's a little annoying and you have to be a little tech savvy to get it working. I am outlining instructions here for how I connected my Droid X to my Amahi HDA.

Some prerequisites:
* Your phone must be rooted.
* I am running Android 2.2 so these instructions may become outdated. I also recommend you be running Android 2.2 Froyo on your Droid X
* You should have adb installed (or running a more advanced bash terminal on Android like Better Terminal Emulator Pro app)
* Install the following apps
** OpenVPN Installer
** OpenVPN Settings

Create a directory on your SDCARD called openvpn or if in the terminal /sdcard/openvpn.

Follow the general [[VPNLinux]] instructions but place all of the configurations and certificates in the openvpn folder on your sdcard.

Install openvpn using the "OpenVPN Installer" app and select /system/bin each time the app asks for a location to place a binary.

You can run one of the following commands to grab the mount point of your system folder. (Run commands through adb or in a terminal on your Droid)
<pre><nowiki>
df | grep system
cat /proc/mounts | grep system
cat /proc/mounts
</nowiki></pre>

My device is mounted on /dev/block/mmcblk1p21 so that is the device I am using in this tutorial. Download tun_alt.ko as recommended in [http://forum.xda-developers.com/showpost.php?p=11109394&postcount=25 this post]. Copy it to the root of your sdcard.

Now we install the kernel module. Run the following command sequence (through adb or a terminal on your Droid).
<pre><nowiki>
su
mount -o rw,remount /dev/block/mmcblk1p21 /system
mv /sdcard/tun_alt.ko /system/lib/modules/tun.ko
cd /system/lib/modules
chown root\: tun.ko
chmod 644 tun.ko

#now lets test it
insmod /system/lib/modules/tun.ko
</nowiki></pre>
If you don't see any output and the "OpenVPN Installer" app successfully installed openvpn then you should be set up.

Double check your configuration in /sdcard/openvpn. Once you know everything is good then run the "OpenVPN Settings" app. It should automatically detect your configuration.

Enable OpenVPN. Select your config to turn on the tunnel. Then you should see a prompt in your notification status prompting for a password. My Droid X connected to the network after that.

There's one final step. If you remember you manually ran the insmod /system/lib/modules/tun.ko command but when you reboot your phone the module will no longer be loaded.

Go into the settings for the "OpenVPN Settings" app and modify the TUN module settings.
* Set "Load module using" to insmod.
* Set "Path to tun module" to /system/lib/modules/tun.ko

Reboot your phone and test the configurations. It should be a one click process within the "OpenVPN Settings" app.

[[Category: VPN]]

VPNAndroid

2017-10-16T14:11:47Z

Beaker2382: /* OpenVPN for Android Client Configuration */

{{NeedsUpdate}}


=OpenVPN for Android Client Configuration=
This wiki has been updated for use with OpenVPN for Android v0.6.73 without Android Root access. Older versions of the wiki are maintained below.

It is presumed that you have installed the [http://www.amahi.org/apps/openvpn OpenVPN] server app on your HDA and [https://wiki.amahi.org/index.php/OpenVPN configured] it properly.

# Download the (3) certificate files. They can be found on the [[OpenVPN Client Certificates]] download page.
##If downloading from link above directly to Android Device, Google translate may ask if you wish to translate the document, DO NOT allow any translation to occur.
##If downloading to a computer first, the key is often downloaded as xxx.key.txt. You must remove the .txt extension.
# Launch the OpenVPN app, select Add Profile (+), give it a name and it will bring you to the Basic configuration tab [[File:NoVPNDefined.png | 180px]][[File:AddProfile.png | 180px]]
# In the Basic tab, Select "User/PW + Certificates" from the pull down menu of Types [[File:TypeAndCerts.png | 180px]]
# In turn, select the CA Certificate, Client Certificate and Client Key files that you downloaded to your device [[File:CertsAdded.png | 180px]]
#Swipe left or right to change tabs in the Configuration page or select them directly from the tab bar.
#From the Server List tab, enter your server Dynamic DNS name found on the [http://www.amahi.org Control Panel] - xxx.yourhda.com [[File:serverDNSname.png | 180px]]
#From the Authentication/Encryption tab, select Remote Certificate Subject and look closely for the pull down arrow in the open window, select RDN Prefix [[File:SubjectPulldown.png | 180px]]
#In the Remote Certificate Subject box change the data field to read Amahi-Server-OpenVPN [[File:HostnameSubject.png | 180px]]
#Configuration is complete, hit the android device's back button to return to the OpenVPN main screen. This will show your new profile, and if you are NOT connected to your local network (turn off Wi-Fi and use cellular data), you will be able to select your profile and it will connect. A secure connection will be shown as a key symbol next to the cellular signal strength bar.

 

= VPN Client - Android - HTC Android G1/Dream =

'''NOTE:''' [https://play.google.com/store/apps/details?id=de.blinkt.openvpn&hl=en OpenVPN for Android] works with the certificates below for ICS 4.0 or greater without rooting your device. There is no additional configuration required to the HDA or your device (Tested on HTC One X and Samsung Tab 2 also on HTC One V). For Sony Xperia ZR (and I suspect most other Android devices) the following was necessary:

# Download the certificates. They can be found on the [[OpenVPN Client Certificates]] download page.
# Launch the OpenVPN app, Add Profile and go to the Basic configuration page [[File:OpenVPNAndroid-1-AddProfile.png|180px]] [[File:OpenVPNAndroid-2-ChooseBasic.png|180px]]
# Enter your server address - the Dynamic DNS name works for me, I guess the fixed IP address would as well [[File:OpenVPNAndroid-3-EnterServerAddress.png|180px]]
# Select "User/PW + Certificates" from the list of Types (the certificates alone are not enough) [[File:OpenVPNAndroid-4-SelectType.png|180px]] [[File:OpenVPNAndroid-5-SelectedType.png|180px]]
# In turn, select the CA Certificate, Client Certificate and Client Key files that you downloaded to your device; note that the app will disable the file type it doesn't think will work so beware if you rename these files [[File:OpenVPNAndroid-6-SelectCertKey.png|180px]]
# Enter your username - a general user with access to the shares and apps on your HDA [[File:OpenVPNAndroid-7-EnterUsername.png|180px]]
# Go back to the list of profiles and click on this new profile to start connecting to your HDA: you will be alerted to the fact that OpenVPN for Android can intercept network traffic and asked to trust the application (ensure that your device is not already connected to the same network - test from a different location or turn of wifi and use your mobile data connection) [[File:OpenVPNAndroid-8-TrustApplication.png|180px]]
# Enter your password - you can decide whether or not the application should save the password [[File:OpenVPNAndroid-9-EnterPassword.png|180px]]
# Watch for connection messages to go past as Android notifications and you will also see the OpenVPN log [[File:OpenVPNAndroid-A-Connecting.png|180px]]
# Once you get a successful connection you will see a key in the notification bar; selecting this notification will show the status of the connection ind give you some options for working with it [[File:OpenVPNAndroid-B-Connected.png|180px]]
# You should now be able to open your favourite app used to access files on your HDA, be that the Amahi app, Plex client, OwnCloud, etc. (note that some of these apps may need to be switched between Local and Remote connection type)

This guide is written for a HTC Android G1/Dream phone rooted with Cyanongenmod 5.

[update March 24, 2011: Tested and works with Cyanogenmod 7.0, thus any CM7 compatible phone]

[update August 8, 2011: Tested and works with Cyanogenmod 7.1, thus any CM 7.1 compatible phone]

[update September 9, 2011: Tested and works with MIUI 1.9.2 on a HTC Droid Incredible 2, should work on any MIUI ROM]

[update 22 March 2013: Tested and works with Android 4.2.2 on Nexus Devices]

In your Linux-based OS computer..

Download the certificates. They can be found on the [[OpenVPN Client Certificates]] download page. Save them in your /home/username/openvpn folder (where ''username'' is your main users name).

Then, from the terminal run

cd /home/username/openvpn
openssl pkcs12 -export -in Amahi-Client-OpenVPN.crt -inkey Amahi-Client-OpenVPN.key -certfile ca.crt -name Amahi -out certs.p12

You will be asked for a export password for the certs.p12 file - enter amahi twice.

To automate this process, paste the code from [http://wiki.amahi.org/images/f/f9/Automate.script automate.script] in your favorite editor. Save it & run it with
sh <filename>

You should now have a certs.p12 file in your /home/username/openvpn folder, copy this certs.p12 file to the root of your sdcard on the Android phone.

Now on the Android phone..

<pre><nowiki>
Menu -> Settings -> Location & Security -> Install from SD card
</nowiki></pre>

This will show you certs.p12, select this and enter the password amahi, after it has extracted the certificates, you will be asked to name the certificate, enter Amahi.

Now on the Android phone

<pre><nowiki>
Menu -> Settings -> Wireless & networks -> VPN settings -> Add VPN -> Add OpenVPN VPN
</nowiki></pre>

VPN name = Amahi

Set VPN server = yourHDAnickname.yourhda.com

User authentication = Yes

Set CA certificate - Amahi

Set user certificate - Amahi

Menu -> Advanced -> LZO compression = Yes

Back

Menu -> Save

You should now see an Amahi entry, click on this to connect. It may ask you for the certificate access password. Then it may ask for your username and password that you use to loginon your HDA. You should see that you are connected, enjoy your VPN connection to your HDA server.

= VPN Client - Android 2.2 - DROID X (Verizon Wireless) =
Contact me in the forums if you need help setting this up. If you have a later version of Android such as Gingerbread (Android 2.3) then you can't use this tutorial for setting up openvpn. You can however use the openvpn configurations if your phone is already set up with openvpn.

[[User:Sag47|Sag47]] 00:51, 5 April 2011 (PDT)

This tutorial is not for the feeble minded. I tried writing it as best as I could to keep it a "How to VPN" article and not a "How to root my droid" topic.

The default Droid X from Verizon does not come with openvpn installed. It's a little annoying and you have to be a little tech savvy to get it working. I am outlining instructions here for how I connected my Droid X to my Amahi HDA.

Some prerequisites:
* Your phone must be rooted.
* I am running Android 2.2 so these instructions may become outdated. I also recommend you be running Android 2.2 Froyo on your Droid X
* You should have adb installed (or running a more advanced bash terminal on Android like Better Terminal Emulator Pro app)
* Install the following apps
** OpenVPN Installer
** OpenVPN Settings

Create a directory on your SDCARD called openvpn or if in the terminal /sdcard/openvpn.

Follow the general [[VPNLinux]] instructions but place all of the configurations and certificates in the openvpn folder on your sdcard.

Install openvpn using the "OpenVPN Installer" app and select /system/bin each time the app asks for a location to place a binary.

You can run one of the following commands to grab the mount point of your system folder. (Run commands through adb or in a terminal on your Droid)
<pre><nowiki>
df | grep system
cat /proc/mounts | grep system
cat /proc/mounts
</nowiki></pre>

My device is mounted on /dev/block/mmcblk1p21 so that is the device I am using in this tutorial. Download tun_alt.ko as recommended in [http://forum.xda-developers.com/showpost.php?p=11109394&postcount=25 this post]. Copy it to the root of your sdcard.

Now we install the kernel module. Run the following command sequence (through adb or a terminal on your Droid).
<pre><nowiki>
su
mount -o rw,remount /dev/block/mmcblk1p21 /system
mv /sdcard/tun_alt.ko /system/lib/modules/tun.ko
cd /system/lib/modules
chown root\: tun.ko
chmod 644 tun.ko

#now lets test it
insmod /system/lib/modules/tun.ko
</nowiki></pre>
If you don't see any output and the "OpenVPN Installer" app successfully installed openvpn then you should be set up.

Double check your configuration in /sdcard/openvpn. Once you know everything is good then run the "OpenVPN Settings" app. It should automatically detect your configuration.

Enable OpenVPN. Select your config to turn on the tunnel. Then you should see a prompt in your notification status prompting for a password. My Droid X connected to the network after that.

There's one final step. If you remember you manually ran the insmod /system/lib/modules/tun.ko command but when you reboot your phone the module will no longer be loaded.

Go into the settings for the "OpenVPN Settings" app and modify the TUN module settings.
* Set "Load module using" to insmod.
* Set "Path to tun module" to /system/lib/modules/tun.ko

Reboot your phone and test the configurations. It should be a one click process within the "OpenVPN Settings" app.

[[Category: VPN]]

File:TypeAndCerts.png

2017-10-16T14:09:47Z