Bitnami Live Helper Chat for Huawei Enterprise Cloud ?· Bitnami Live Helper Chat for Huawei Enterprise…

Download Bitnami Live Helper Chat for Huawei Enterprise Cloud ?· Bitnami Live Helper Chat for Huawei Enterprise…

Post on 25-Jun-2018




0 download

Embed Size (px)


<ul><li><p>Bitnami Live Helper Chat for Huawei </p><p>Enterprise Cloud </p><p>Description </p><p>Open source - Live Support chat for your website. Web and desktop clients. It </p><p>includes: co-browsing, XMPP notifications, GTalk, Jabber, Openfire, Skype, </p><p>Chrome extension, Node.js support, MySQL, PostgreSQL. </p><p>First steps with the Bitnami Live Helper Chat </p><p>Stack </p><p>Welcome to your new Bitnami application running on Huawei Enterprise Cloud! </p><p>Here are a few questions (and answers!) you might need when first starting </p><p>with your application. </p><p>What is the administrator username set for me to log in to the </p><p>application for the first time? </p><p>Username: user </p><p>What is the administrator password? </p><p>To obtain the administrator password, click the "Remote Login" menu option </p><p>next to the server name in the Huawei Cloud Server Console. This will launch </p><p>a new browser window with an encrypted login session. The application </p><p>password will be displayed on the login welcome screen. </p><p>What SSH username should I use for secure shell access to </p><p>my application? </p><p>SSH username: root </p><p>How to connect to the MySQL database? </p><p>You can connect to the MySQL database from the same computer where it is </p><p>installed with the mysql client tool. </p></li><li><p>mysql -u root -p </p><p>You will be prompted to enter the root user password. This is the same as the </p><p>application password. </p><p>Find out how to obtain application credentials. </p><p>How to debug errors in your database? </p><p>The main log file is created at /opt/bitnami/mysql/data/mysqld.log on the </p><p>MySQL database server host. </p><p>How to start or stop the services? </p><p>Each Bitnami stack includes a control script that lets you easily stop, start and </p><p>restart services. The script is located at /opt/bitnami/ Call it without </p><p>any service name arguments to start all services: </p><p>sudo /opt/bitnami/ start </p><p>Or use it to restart a single service, such as Apache only, by passing the </p><p>service name as argument: </p><p>sudo /opt/bitnami/ restart apache </p><p>Use this script to stop all services: </p><p>sudo /opt/bitnami/ stop </p><p>Restart the services by running the script without any arguments: </p><p>sudo /opt/bitnami/ restart </p><p>Obtain a list of available services and operations by running the script without </p><p>any arguments: </p><p>sudo /opt/bitnami/ </p><p>How to create a full backup of Live Helper </p><p>Chat? </p><p></p></li><li><p>Backup </p><p>The Bitnami Live Helper Chat Stack is self-contained and the simplest option </p><p>for performing a backup is to copy or compress the Bitnami stack installation </p><p>directory. To do so in a safe manner, you will need to stop all servers, so this </p><p>method may not be appropriate if you have people accessing the application </p><p>continuously. </p><p>Follow these steps: </p><p> Change to the directory in which you wish to save your backup: </p><p> cd /your/directory </p><p> Stop all servers: </p><p> sudo /opt/bitnami/ stop </p><p> Create a compressed file with the stack contents: </p><p> sudo tar -pczvf application-backup.tar.gz /opt/bitnami </p><p> Restart all servers: </p><p> sudo /opt/bitnami/ start </p><p>You should now download or transfer the application-backup.tar.gz file to a </p><p>safe location. </p><p>Restore </p><p>Follow these steps: </p><p> Change to the directory containing your backup: </p><p> cd /your/directory </p><p> Stop all servers: </p><p> sudo /opt/bitnami/ stop </p><p> Move the current stack to a different location: </p></li><li><p> sudo mv /opt/bitnami /tmp/bitnami-backup </p><p> Uncompress the backup file to the original directoryv </p><p> sudo tar -pxzvf application-backup.tar.gz -C / </p><p> Start all servers: </p><p> sudo /opt/bitnami/ start </p><p>If you want to create only a database backup, refer to these instructions for </p><p>MySQL and PostgreSQL. </p><p>How to configure outbound email settings? </p><p>To configure outbound email, follow these steps: </p><p> Log in to the application as an administrator. </p><p> Click the "System Configuration" icon (next to the "Extra Modules" tab). </p><p> Select the "Mail Settings" in system tab. </p><p> At the "Mail Settings" subtab, configure whatever you want to appear as </p><p>the "From" address. For instance: </p><p> Select the "SMTP" tab. </p><p> Enable SMTP, clicking on the checkbox. </p><p> Configure the server to be used for outbound email. For example, to </p><p>configure a Gmail account, you could use the settings below. Replace </p><p>USERNAME and PASSWORD with your Gmail account username and </p><p>password respectively. </p><p>o SMTP Server - tls:// </p><p>o SMTP port - 465 </p><p>o Login - </p><p>o SMTP Password - PASSWORD </p><p> Click "Save" to save your changes or "Test" to send a test email and </p><p>save the settings. </p><p></p></li><li><p>To configure the application to use other third-party SMTP services for </p><p>outgoing email, such as SendGrid or Mandrill, refer to the FAQ. </p><p>Troubleshooting Gmail SMTP issues </p><p>If you are using Gmail as the outbound email server and you are not able to </p><p>send email correctly, Google may be blocking sign-in attempts from your apps </p><p>or devices. Depending on whether or not you use Google Apps, the steps to </p><p>correct this will differ. </p><p>For Google Apps users </p><p>If you are a Google Apps user, you will need your administrator to allow users </p><p>to change the policy for less secure apps. If you are a Google Apps </p><p>administrator, follow these steps: </p><p> Browse to the Google Apps administration panel. </p><p> Click on "Security" and then "Basic settings". </p><p> Look for the section "Less secure apps" and then click on "Go to </p><p>settings for less secure apps". </p><p> Select "Allow users to manage their access to less secure apps". </p><p>For other Google users </p><p>If you do not use Google Apps, follow the steps in the following sections, </p><p>depending on whether 2-step verification has been enabled on the account or </p><p>not. </p><p>If 2-step verification has not been enabled on the account, follow these steps: </p><p></p></li><li><p> Browse to the "Less secure apps" page and log in using the account you </p><p>are having problems with. This option is typically required by many </p><p>popular email clients, such as Outlook and Thunderbird, and should not </p><p>be considered unsafe. </p><p> Select the "Turn on" option. </p><p>If 2-step verification has been enabled on the account, you have to generate </p><p>an app password. Follow these steps: </p><p> Browse to the "App passwords" page. </p><p> Click "Select app" and choose the app you're using. </p><p> Click "Select device" and choose the device you're using. </p><p> Click the "Generate" button. </p><p> Enter the app password on your device. </p><p> Click the "Done" button. </p><p>Here are other options you may try: </p><p> Browse to the web version of Gmail and sign in to your account. Once </p><p>you're signed in, try to enable access for the application again. </p><p> Browse to the "Unlock Captcha" function page and sign in with your </p><p>Gmail username and password. </p><p> Disable IMAP from the Gmail web server interface and enable it again. </p><p>How to upload files to the server with SFTP? </p><p></p></li><li><p>Although you can use any SFTP/SCP client to transfer files to your server, the </p><p>link below explains how to configure FileZilla (Windows, Linux and Mac OS X), </p><p>WinSCP (Windows) and Cyberduck (Mac OS X). It is required to use your </p><p>server's private SSH key to configure the SFTP client properly. Choose your </p><p>preferred application and follow the steps in the link below to connect to the </p><p>server through SFTP. </p><p>How to upload files to the server </p><p>How to enable HTTPS support with SSL </p><p>certificates? </p><p>NOTE: The steps below assume that you are using a custom domain name </p><p>and that you have already configured the custom domain name to point to your </p><p>cloud server. </p><p>Bitnami images come with SSL support already pre-configured and with a </p><p>dummy certificate in place. Although this dummy certificate is fine for testing </p><p>and development purposes, you will usually want to use a valid SSL certificate </p><p>for production use. You can either generate this on your own (explained here) </p><p>or you can purchase one from a commercial certificate authority. </p><p>Once you obtain the certificate and certificate key files, you will need to update </p><p>your server to use them. Follow these steps to activate SSL support: </p><p> Use the table below to identify the correct locations for your certificate </p><p>and configuration files. </p><p>Variable Value </p><p>Current </p><p>application URL https://[custom-domain]/ </p><p> Example: or </p><p> </p><p>Apache </p><p>configuration file /opt/bitnami/apache2/conf/bitnami/bitnami.conf </p><p>Certificate file /opt/bitnami/apache2/conf/server.crt </p><p>Certificate key file /opt/bitnami/apache2/conf/server.key </p><p>CA certificate </p><p>bundle file (if </p><p>present) </p><p>/opt/bitnami/apache2/conf/server-ca.crt </p><p> Copy your SSL certificate and certificate key file to the specified </p><p>locations. </p><p>NOTE: If you use different names for your certificate and key files, you should </p><p>reconfigure the SSLCertificateFile and SSLCertificateKeyFile directives in the </p><p>corresponding Apache configuration file to reflect the correct file names. </p><p></p></li><li><p> If your certificate authority has also provided you with a PEM-encoded </p><p>Certificate Authority (CA) bundle, you must copy it to the correct </p><p>location in the previous table. Then, modify the Apache configuration </p><p>file to include the following line below the SSLCertificateKeyFile </p><p>directive. Choose the correct directive based on your scenario and </p><p>Apache version: </p><p>Variable Value </p><p>Apache </p><p>configuration file /opt/bitnami/apache2/conf/bitnami/bitnami.conf </p><p>Directive to include </p><p>(Apache v2.4.8+) </p><p>SSLCACertificateFile </p><p>"/opt/bitnami/apache2/conf/server-ca.crt" </p><p>Directive to include </p><p>(Apache &lt; v2.4.8) </p><p>SSLCertificateChainFile </p><p>"/opt/bitnami/apache2/conf/server-ca.crt" </p><p>NOTE: If you use a different name for your CA certificate bundle, you should </p><p>reconfigure the SSLCertificateChainFile or SSLCACertificateFile directives in </p><p>the corresponding Apache configuration file to reflect the correct file name. </p><p> Once you have copied all the server certificate files, you may make </p><p>them readable by the root user only with the following commands: </p><p> sudo chown root:root /opt/bitnami/apache2/conf/server* </p><p> sudo chmod 600 /opt/bitnami/apache2/conf/server* </p><p> Open port 443 in the server firewall. Refer to the FAQ for more </p><p>information. </p><p> Restart the Apache server. </p><p>You should now be able to access your application using an HTTPS URL. </p><p>How to create an SSL certificate? </p><p>You can create your own SSL certificate with the OpenSSL binary. A certificate </p><p>request can then be sent to a certificate authority (CA) to get it signed into a </p><p>certificate, or if you have your own certificate authority, you may sign it yourself, </p><p>or you can use a self-signed certificate (because you just want a test certificate </p><p>or because you are setting up your own CA). </p><p> Create your private key (if you haven't created it already): </p><p> sudo openssl genrsa -out /opt/bitnami/apache2/conf/server.key 2048 </p><p> Create a certificate: </p><p></p></li><li><p> sudo openssl req -new -key /opt/bitnami/apache2/conf/server.key -o</p><p>ut /opt/bitnami/apache2/conf/cert.csr </p><p>IMPORTANT: Enter the server domain name when the above </p><p>command asks for the "Common Name". </p><p> Send cert.csr to the certificate authority. When the certificate authority </p><p>completes their checks (and probably received payment from you), they </p><p>will hand over your new certificate to you. </p><p> Until the certificate is received, create a temporary self-signed </p><p>certificate: </p><p> sudo openssl x509 -in /opt/bitnami/apache2/conf/cert.csr -out /opt</p><p>/bitnami/apache2/conf/server.crt -req -signkey /opt/bitnami/apach</p><p>e2/conf/server.key -days 365 </p><p> Back up your private key in a safe location after generating a </p><p>password-protected version as follows: </p><p> sudo openssl rsa -des3 -in /opt/bitnami/apache2/conf/server.key -o</p><p>ut privkey.pem </p><p>Note that if you use this encrypted key in the Apache configuration file, it </p><p>will be necessary to enter the password manually every time Apache </p><p>starts. Regenerate the key without password protection from this file as </p><p>follows: </p><p>sudo openssl rsa -in privkey.pem -out /opt/bitnami/apache2/conf/se</p><p>rver.key </p><p>Find more information about certificates at </p><p>How to force HTTPS redirection? </p><p>Add the following to the top of the </p><p>/opt/bitnami/apps/livehelperchat/conf/httpd-prefix.conf file: </p><p>RewriteEngine On </p><p>RewriteCond %{HTTPS} !=on </p><p>RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L] </p><p></p></li><li><p>After modifying the Apache configuration files, restart Apache to apply the </p><p>changes. </p><p>How to debug Apache errors? </p><p>Once Apache starts, it will create two log files at </p><p>/opt/bitnami/apache2/logs/access_log and /opt/bitnami/apache2/logs/error_log </p><p>respectively. </p><p> The access_log file is used to track client requests. When a client </p><p>requests a document from the server, Apache records several </p><p>parameters associated with the request in this file, such as: the IP </p><p>address of the client, the document requested, the HTTP status code, </p><p>and the current time. </p><p> The error_log file is used to record important events. This file includes </p><p>error messages, startup messages, and any other significant events in </p><p>the life cycle of the server. This is the first place to look when you run </p><p>into a problem when using Apache. </p><p>If no error is found, you will see a message similar to: </p><p>Syntax OK </p><p>How to modify PHP settings? </p><p>The PHP configuration file allows you to configure the modules enabled, the </p><p>email settings or the size of the upload files. It is located at </p><p>/opt/bitnami/php/etc/php.ini. </p><p>After modifying the PHP configuration file, restart both Apache and PHP-FPM </p><p>for the changes to take effect: </p><p>sudo /opt/bitnami/ restart apache </p><p>sudo /opt/bitnami/ restart php-fpm </p><p>For example, to modify the default upload limit for PHP, update the PHP </p><p>configuration file following these instructions. </p><p>How to modify the allowed limit for uploaded </p><p>files? </p><p></p></li><li><p>Modify the following options in the /opt/bitnami/php/etc/php.ini file to increase </p><p>the allowed size for uploads: </p><p>; Maximum size of POST data that PHP will accept. </p><p>post_max_size = 16M </p><p>; Maximum allowed size for uploaded files. </p><p>upload_max_filesize = 16M </p><p>Restart PHP-FPM and Apache for the changes to take effect. </p><p>sudo /opt/bitnami/ restart apache </p><p>sudo /opt/bitnami/ restart php-fpm </p><p>How to access phpMyAdmin? </p><p>For security reasons, phpMyAdmin is accessible only when using</p></li></ul>