Changes

From Amahi Wiki
Jump to: navigation, search
no edit summary
You have to access BOTH the shares and the dashboard of each server by IP address of the HDA. <br/><blockquote>For example, "\\192.168.1.20" in Window will get you to the shares on the HDA with that IP address, if you have established a user and password for that client. Also, 192.168.1.20 in a web browser will take you to the dashboard of the HDA with that IP address.</blockquote>
I personally deleted all of the Amahi links on each HDA's Fedora desktop and created a launcher that opens the Amahi dashboard by IP address.<br/>To create the launcher*Right-click on the Fedora Desktop and choose "Create Launcher"*Change "Type" to "Location."*Give it a name (i. e. <i>Amahi HDA Dashboard</i>)*Under "Command" http:// and the IP of the HDA
<u><b>Change External DNS on HDA2</b></u><br/>
{{Code|hda-change-dns ipHDA1 ipHDA1}}
<u><b>Apps You Need</b></u> (Needs details)<br/>*Amahi Web-Apps Proxy (http://www.amahi.org/apps/amahi-web-apps-proxy) on both HDAs. Access <blockquote>*Go to the Amahi Dashboard and under "Apps" find and install Amahi Web-Apps Proxy. In order to configure Amahi Web-Apps Proxy, access the Amahi Web-Apps Proxy for each HDA the first time from a client computer outside of the Local Area Network. Then change the user name and password to suite your needs.<br/blockquote>*Ajaxplorer (http://www.amahi.org/apps/ajaxplorer) installed on HDA1. This met my external file access needs for HDA1.<br/>
*OpenVPN ALS (formerly Adito)(http://www.amahi.org/apps/openvpn-als) on HDA2. This app has a convenience fee to install that it is well worth it. :-)<br/>
<li>Change OpenVPN ALS to listen on port 443
*Complete steps of Amahi Wiki "Access HDA over SSL" (http://wiki.amahi.org/index.php/Access_HDA_over_SSL)
*Complete all steps of Amahi Wiki "Secure App Access" (http://wiki.amahi.org/index.php/Secure_App_Access) but be sure when you are editing the ####-adito.conf file that you change it is like what is listed below, substituting your server's dynamic dns address and correct SSL certificate .crt & .key file names and locations.:
{{Text|<VirtualHost *:443>
SSLCertificateKeyFile /etc/httpd/conf/filename.key
}}
substituting Note: *Substitute your server's dynamic dns address and correct SSL certificate .crt & .key file names and locations.<br/>*Do not change anything from "DocumentRoot" or below in the file. 
<li>Web Forwards - Tunneled Web Apps
* Login as administrator
* Enter Application Name and Description.
* Check Add to Favorites and select Next
* Enter '''<nowiki>http://application</nowiki>''' for Destination URL. <b>Be sure URLs are entered as local area network addresses, not dynamic DNS addresses</b> '''<nowiki>(i.e. http://subsonic.yourlocalhostaddress.com</nowiki>''' not '''<nowiki>subsonic.username.yourhda.com)</nowiki>'''. Local address are used since the VPN tunnel is creating an environment as if you were in the Local Area Network. Applications For applications that use a port other than 80, you need to specify that as part of the URL, for example '''<nowiki>http://subsonic.yourlocalhostaddress.com:4040</nowiki>'''. Select Next.
* Select Everyone, select Add, and select Next
* Select Finish and select Exit Wizard
128

edits