FAQ Redirected from BitNami Hosting/FAQ

    Table of contents
    1. 1. General
      1. 1.1. Support and where can I get more info?
      2. 1.2. What is my helpdesk password
    2. 2. Billing
      1. 2.1. How much does it cost?
      2. 2.2. How much do backups cost?
      3. 2.3. Do you provide refunds?
      4. 2.4. Why AWS Free Tier servers still show as charges in the BCH console
      5. 2.5. Can I use a reserved instance?
      6. 2.6. How can I cancel my account?
    3. 3. Amazon Web Services
      1. 3.1. How to create AWS account?
      2. 3.2. Sending emails from EC2 instances
      3. 3.3. Is Static IP address free of charge?
      4. 3.4. How do I get more than 5 static IP addresses
      5. 3.5. Learn more about Amazon Web Services
    4. 4. Operating System
      1. 4.1. What operating systems are supported
      2. 4.2. How do I keep my base system up to date?
      3. 4.3. How to install ec2-api-tools?
      4. 4.4. What is the root password
      5. 4.5. Can I install and use Linux default Apache / MySQL servers ?
    5. 5. BitNami Cloud Hosting Servers
      1. 5.1. What is the password
      2. 5.2. Access your machine
      3. 5.3. Uploading files with WinSCP, FileZilla and OSX Cyberduck
      4. 5.4. What is the FTP password
      5. 5.5. How to ssh to my machine
      6. 5.6. Is it possible to connect using VNC
      7. 5.7. How can I move an existing PHP app (such as Wordpress) to a BitNami server?
      8. 5.8. How to move a server to another AWS account?
      9. 5.9. How to open an additional server port
      10. 5.10. How can I remove the Unassigned Static IP Address?
      11. 5.11. How can I move my instance to a different availability zone?
      12. 5.12. Does BitNami Hosting automate DNS configuration?
      13. 5.13. How can I assign another domain / URL to my BitNami server?
      14. 5.14. Server in 'pending' state for an hour
      15. 5.15. Server operations problems - Unexpected Error
      16. 5.16. How can I add webmin to my server on BitNami Cloud Hosting?
      17. 5.17. Which Browsers are Supported?
    6. 6. BitNami Stack
      1. 6.1. BitNami Base Stack
      2. 6.2. How to manage BitNami stack components
      3. 6.3. What is the MySQL, PHP and Apache version installed in my machine
      4. 6.4. What is the MySQL password?
      5. 6.5. How to connect to the BitNami MySQL remotely?
      6. 6.6. What is the phpMyAdmin password
      7. 6.7. Getting 1045 error when trying to login to phpmyadmin
      8. 6.8. What is the PostgreSQL password?
      9. 6.9. What is the phpPgAdmin password? 
      10. 6.10. Configuring PHP script to send emails via external SMTP server
      11. 6.11. How can I set up a development environment for Ruby, PHP, or Java
      12. 6.12. What is the JBoss console password?
      13. 6.13. How to connect to the JBoss console?
      14. 6.14. How to activate Java and OpenOffice in the base server
      15. 6.15. How to activate subversion server
      16. 6.16. What is the Tomcat Web Application Manager password? 
      17. 6.17. How to enable SSL to access through https?
      18. 6.18. How to create a SSL certificate?
      19. 6.19. How to force the HTTPS access?
      20. 6.20. How to confgure multiple SSL domains on the same IP address?
    7. 7. BitNami Applications
      1. 7.1. How to manage BitNami Applications
      2. 7.2. What are the default login and passwords for BitNami applications
      3. 7.3. Where are my apps installed?
      4. 7.4. Adding a new application to an existing server
      5. 7.5. Remove an application from an existing server
      6. 7.6. Custom Applications
      7. 7.7. Caching

    1. 1. General
      1. 1.1. Support and where can I get more info?
      2. 1.2. What is my helpdesk password
    2. 2. Billing
      1. 2.1. How much does it cost?
      2. 2.2. How much do backups cost?
      3. 2.3. Do you provide refunds?
      4. 2.4. Why AWS Free Tier servers still show as charges in the BCH console
      5. 2.5. Can I use a reserved instance?
      6. 2.6. How can I cancel my account?
    3. 3. Amazon Web Services
      1. 3.1. How to create AWS account?
      2. 3.2. Sending emails from EC2 instances
      3. 3.3. Is Static IP address free of charge?
      4. 3.4. How do I get more than 5 static IP addresses
      5. 3.5. Learn more about Amazon Web Services
    4. 4. Operating System
      1. 4.1. What operating systems are supported
      2. 4.2. How do I keep my base system up to date?
      3. 4.3. How to install ec2-api-tools?
      4. 4.4. What is the root password
      5. 4.5. Can I install and use Linux default Apache / MySQL servers ?
    5. 5. BitNami Cloud Hosting Servers
      1. 5.1. What is the password
      2. 5.2. Access your machine
      3. 5.3. Uploading files with WinSCP, FileZilla and OSX Cyberduck
      4. 5.4. What is the FTP password
      5. 5.5. How to ssh to my machine
      6. 5.6. Is it possible to connect using VNC
      7. 5.7. How can I move an existing PHP app (such as Wordpress) to a BitNami server?
      8. 5.8. How to move a server to another AWS account?
      9. 5.9. How to open an additional server port
      10. 5.10. How can I remove the Unassigned Static IP Address?
      11. 5.11. How can I move my instance to a different availability zone?
      12. 5.12. Does BitNami Hosting automate DNS configuration?
      13. 5.13. How can I assign another domain / URL to my BitNami server?
      14. 5.14. Server in 'pending' state for an hour
      15. 5.15. Server operations problems - Unexpected Error
      16. 5.16. How can I add webmin to my server on BitNami Cloud Hosting?
      17. 5.17. Which Browsers are Supported?
    6. 6. BitNami Stack
      1. 6.1. BitNami Base Stack
      2. 6.2. How to manage BitNami stack components
      3. 6.3. What is the MySQL, PHP and Apache version installed in my machine
      4. 6.4. What is the MySQL password?
      5. 6.5. How to connect to the BitNami MySQL remotely?
      6. 6.6. What is the phpMyAdmin password
      7. 6.7. Getting 1045 error when trying to login to phpmyadmin
      8. 6.8. What is the PostgreSQL password?
      9. 6.9. What is the phpPgAdmin password? 
      10. 6.10. Configuring PHP script to send emails via external SMTP server
      11. 6.11. How can I set up a development environment for Ruby, PHP, or Java
      12. 6.12. What is the JBoss console password?
      13. 6.13. How to connect to the JBoss console?
      14. 6.14. How to activate Java and OpenOffice in the base server
      15. 6.15. How to activate subversion server
      16. 6.16. What is the Tomcat Web Application Manager password? 
      17. 6.17. How to enable SSL to access through https?
      18. 6.18. How to create a SSL certificate?
      19. 6.19. How to force the HTTPS access?
      20. 6.20. How to confgure multiple SSL domains on the same IP address?
    7. 7. BitNami Applications
      1. 7.1. How to manage BitNami Applications
      2. 7.2. What are the default login and passwords for BitNami applications
      3. 7.3. Where are my apps installed?
      4. 7.4. Adding a new application to an existing server
      5. 7.5. Remove an application from an existing server
      6. 7.6. Custom Applications
      7. 7.7. Caching

    General

    Support and where can I get more info?

    Other useful BitNami resources

    What is my helpdesk password

    If you did not set your helpdesk.bitnami.com password yet, then go to the following page:

    http://helpdesk.bitnami.com/access/help

    Billing

    How much does it cost?

    BitNami Cloud Hosting is available as a monthly subscription. You can view the available plans on the BitNami Cloud Hosting website. As you will see, we also offer a free tier of service that allows you to deploy and manage one micro os small instance for free. Please note that the BitNami monthly subscription fees are in addition to the charges you will incur from Amazon for running your servers on the Amazon Cloud. We have developed a cloud cost estimator to make it easy to get the estimated costs for running your servers on Amazon. 

    How much do backups cost?

    BitNami Cloud Hosting backups are complete, incremental snapshots of your server. They are based on Amazon EBS snapshots which are stored incrementally on Amazon infrastructure. This means that you will only get billed for the amount of data that has been modified on the EBS volume since the latest snapshot.  You can learn more about EBS snapshots at the following page: http://aws.amazon.com/ebs

    Amazon EBS provides the ability to back up point-in-time snapshots of your data to Amazon S3 for durable recovery. Amazon EBS snapshots are incremental backups, meaning that only the blocks on the device that have changed since your last snapshot will be saved. If you have a device with 100 GBs of data, but only 5 GBs of data has changed since your last snapshot, only the 5 additional GBs of snapshot data will be stored back to Amazon S3. Even though the snapshots are saved incrementally, when you delete a snapshot, only the data not needed for any other snapshot is removed. So regardless of which prior snapshots have been deleted, all active snapshots will contain all the information needed to restore the volume. In addition, the time to restore the volume is the same for all snapshots, offering the restore time of full backups with the space savings of incremental.

    Do you provide refunds?

    Please see our refund policy.

    Why AWS Free Tier servers still show as charges in the BCH console

    If you signed up for your Amazon account after November 1st 2010, you are eligible for one year of use of a free micro instance, plus some other free services from Amazon. You can find more details on what is available free of charge here: http://aws.amazon.com/free/ As long as you meet the criteria and your usage limits are within those provided on that page, you will not incur any charges from Amazon. The charges that we display in the BitNami Cloud Hosting (BCH) console are based on Amazon’s normal rates – we do not yet have the ability to account for any free services from Amazon within the BCH console. So, if you are looking at the BCH console, what you’re seeing are the charges that you would incur from Amazon if you were not eligible for the free service (or once your eligibility expires), not the actual charges that you will be billed for from Amazon.

    Can I use a reserved instance?

    Yes, you can buy reserved instances via AWS console and then use the BitNami Cloud Hosting interface to launch servers in a very specific availability zone. The reserved instance is just a billing term. For example, if you buy an AWS micro reserved instance for a year via AWS console, then you can launch and terminate micro instances any time you want (via BCH console, API calls etc.), and as long as they are created in the same AWS availability zone as your reserved instance, you will be billed with the lower rate.

    Make sure that you select the Availability Zone where you have purchased the reserved instance when launching your server with BitNami Cloud Hosting, to make sure that you are charged based on the reserved instance pricing. To do so, first click on the icon with the American flag on it on the Create Server screen. Then, select the appropriate Amazon Region and click on 'Advanced Options' to select the Availability Zone.

    Choosing between light, medium or heavy utilization will depend on the percentage of time you expect your server to be running but it will not affect anything of the mentioned above. You can find more details here: http://aws.amazon.com/ec2/reserved-instances/#2

    How can I cancel my account?

    Are you sure you want to cancel your account? You can downgrade to our free tier to preserve your account! While we are sorry to see you go, cancelling your account is easy. Just login to BitNami and in "Cloud Hosting" section, click on "Access Console" and you will access Bitnami Cloud Hosting. Now click on the 'Billing' link in the left panel and then click on the 'delete account' button. Please note that this action is permanent - your BitNami Cloud Hosting data cannot be restored after it is deleted, so make sure that you are ready to cancel when you click the button. Also, note that any servers that you have running or backups that you have made will remain in your Amazon Web Services account. If you want to delete those after cancelling your BitNami Cloud Hosting account, you will need to login to the Amazon Web Services console and do so manually. 

    Operating System

    What operating systems are supported

    We do support currently only Linux. The main Linux distributions supported are:

    • Ubuntu
    • Amazon Linux
    • Red Hat

    More detailed information about our base images changes, updated software, bundled components versions etc. can be found at this wiki page.

    How do I keep my base system up to date?

    Connect via SSH and execute the following commands:

    • Linux Ubuntu
    $ sudo apt-get update
    $ sudo apt-get dist-upgrade
    
    • Linux Fedora
    $ sudo yum -y upgrade
    

    How to install ec2-api-tools?

    The API tools are commands that wrap the Amazon EC2 API actions. You can find more details at http://docs.amazonwebservices.com/AWSEC2/latest/CommandLineReference/ .

    Ubuntu

    Before installing, make sure you have multiverse enabled” (EC2StartersGuide). Try to add the following lines to /etc/apt/sources.list (it is an example for us-east zone):

    deb http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ lucid multiverse
    deb-src http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ lucid multiverse
    deb http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ lucid-updates multiverse
    deb-src http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ lucid-updates multiverse
    

    and then

    $ sudo apt-get update
    $ sudo apt-get install ec2-api-tools
    $ ec2-version
    1.3-46266 2009-11-30
    

    Fedora

    You should download the latest version from http://aws.amazon.com/developertools/351 .

    $ wget -nv http://s3.amazonaws.com/ec2-downloads/ec2-api-tools.zip -O /tmp/ec2-api-tools.zip
    $ unzip /tmp/ec2-api-tools.zip
     
    Alternatively, you may install euca2ools from Fedora repositories:
    $ sudo yum -y install euca2ools
    $ euca-version
    main-31337 2009-04-04
     

    Tabs end

    Another way is to install BitNami Cloud Tools. The BitNami Cloud Tools installer packages the Amazon Web Services command line tools together with preconfigured Java, Ruby and Perl language runtimes. It is a self-contained, easy to use distribution with one goal in mind: to make it simple to get started using AWS services from the command line.

    What is the root password

    We do not configure a password for the "root" account by default. You will need to use 'sudo' command to switch to the root user. You will not be asked for the password:

    sudo su -
    

    Learn more about sudo

    Can I install and use Linux default Apache / MySQL servers ?

    The machines started with BitNami Hosting interface comes with already preinstalled full stack (MySQL, Apache, PHP, Ruby, etc.). For more information please visit the following BitNami Wiki resources:

    Please make sure to stop the BitNami stack services before trying to install or start/stop system Apache/MySQL. You can do it executing the following command:

    /opt/bitnami/ctlscript.sh stop
    

    Then you should remove the ctlscript.sh entry from the /etc/init.d/bitnami initialization script.

    BitNami Cloud Hosting Servers

    Uploading files with WinSCP, FileZilla and OSX Cyberduck

    At this wiki page we are describing how to upload files to your cloud machine from Windows WinSCP, FileZilla and OSX Cyberduck.

    What is the FTP password

    The default login and password are:

    login: bitnami

    Ubuntu

    password: <auto-generated>

    It is saved automatically in the application config file, for instance for WordPress take a look at the /opt/bitnami/apps/wordpress/htdocs/wp-config.php file and search for FTP_PASS entry.

    Red Hat, Amazon Linux, Fedora

    password: <user defined> (default: auto-generated more info)

    Tabs end

    You can reconfigure your FTP password connecting via SSH to your server and executing the following command:

    $ sudo passwd bitnami
    

    The FTP server is not available from outside and the port 21 is closed by default. You can open additional ports following these steps there, but we do not recommend it for security reasons. Much better option is to use an encrypted SSH channel for uploading files. We recommend SFTP with programs like WinSCP or FileZilla. You can find more info about how to connect or upload files to your machine in the wiki:

    Is it possible to connect using VNC

    The VNC Server is not installed by default. You may take a look at the following BitNami Blog article to do so.

    How to move a server to another AWS account?

    BitNami Cloud Hosting makes it very easy to move a server from one AWS account to another. To move your server from one AWS account to another:

    1. Sign into your BitNami Cloud Hosting account at: app.bitnamihosting.com
    2. Make sure that you have the new AWS account to which you want to move the server setup as a 'Cloud' in BCH (Go to 'Manage' under the Clouds section in the left navigation pane and click 'New')
    3. Go to the 'Servers' section and select the server that you want to move. Then click on the 'manage' button.
    4. Go to the 'backups' tab and click 'Create Backup' button.
    5. Once the backup is finished, you will see it in the Backups section. Click on 'Restore'. You will see in the pop-up that you can specify a number of variables, including which cloud account you want to launch the server on.

    The above steps will give you an exact copy of your server on the new AWS account. Note that to run 2 servers at once, you will need to be at least on our Basic plan. You can always stop the original server during this process and then delete it once you have the new one running if you want to stay on our free, single-server plan.

    How to open an additional server port

    BitNami Cloud Hosting

    BitNami Cloud Hosting by default opens the following ports for each server: 22, 80 and 443.  You are able to add more ports if you need.

    If you want to open a port, you should:

    1. Go to the Servers section, select your machine and click "Manage" button. Then click 'Firewall' tab.
    2. If your server was created recently, then you will see two buttons:
      Add Custom Firewall Rules - will allow you to add / remove firewall rules which are applied only to this particular instance. This option may not be available for old BitNami Cloud Hosting machines.
      Edit Default Firewall Rules - will let you modify the main AWS Security Group. Please note that any changes here will affect all your servers launched with this BitNami Cloud Hosting cloud account and running in the same AWS region as the current instance.
    3. You can enter the port number (1-65535) or the range of ports (<from port>-<to port>) and the protocol (tcp / udp).
    4. Optionally, you can restrict the access for a specific IP, modifying the Source IP from everyone (0.0.0.0/0) to (<ip value>/32). 

    AWS

    You need to modify the instance Security Group to open an aditional server port.

    Azure

    The Azure opens by default only port 22. You need to add/remove ports in the Azure console, the server Endpoints section.

    Tabs end

     

    How can I remove the Unassigned Static IP Address?

    The BitNami Cloud Hosting allows you manage all your Static IP addresses located in different regions. If you want to delete one of your Static IP addresses, please follow these steps:

    • Login to the BitNami Cloud Hosting console
    • Go to the 'Clouds/Manage' section in the left menu
    • Select your AWS account.
    • Click 'Manage Static IPs' button in the details panel.
    • Select the region where your IP address was created
    • Click 'Delete' next to the IP address which you want to remove

    How can I move my instance to a different availability zone?

    Bitnami Cloud Hosting allows you move your current instances to different availability zones but not to different regions for the moment. Please follow these steps:

    • Stop the current server
    • Create a Backup (Manage -> Backups -> Create Backup)
    • Once it finishes, click "Restore" next to the new backup.
    • In the popup, click on "Advanced Options" and specify the desired availability zone. For example: "us-east-1b".
    • Click restore.
    • Once you have your server running in a different availability zone, you can unassign the static ip from the old server and assign it to the new one.

    Does BitNami Hosting automate DNS configuration?

    BitNami Hosting launches instances with a dynamic IP by default, which means that the IP address changes after you stop and restart the machine. In many cases, this is not desired and instead you want to assign a specific IP address (also known in EC2 as ‘elastic IP’). To do so, go to the ‘Manage’ section, click ‘Assign IP’ and choose one of the already available IP addresses or select ‘Newly created static IP’ to create a new one. Then, click ‘Confirm’. Your machine should be accessible with the new IP, though it may take a a few minutes.

    You can point an existing domain name to a dynamic or static IP address. To do so, go to your DNS provider management console and point the domain name to the BitNami Hosting machine IP. It may take some time before all DNS servers refresh the new domain location.  We do not currently allow creating or managing domain names from the BitNami Hosting interface yet.

    Server in 'pending' state for an hour

    Please take a look at this article.

    Server operations problems - Unexpected Error

    There are several possible reasons for a server operation such as "Server Build", "Server Start", "Server Resize", etc. to finish with an "Unexpected Error" message or with a server being in the Pending state for longer period of time. Please take a look at the list below for details.

    AWS EC2 reporting that the instance is in the pending state

    For every server operation executed, we make sure that the server is in the proper, ready-to-run state. This means that we have to wait for the machine to be in that specific state to continue the process of setting up your applications on it. Sometimes, the AWS EC2 API services continue to answer our queries with the response that the server is still Pending when in fact the machine is available. In rare cases, the server build/start/stop operation may just take more time than usual (this part of the process depends on Amazon, not BitNami).

    Static IP address was assigned to your instance

    Once the 'change IP' operation is executed, BitNami waits for the server to answer from new IP address. This may sometimes take some additional time and is dependent on the responsiveness of AWS.

    Your AWS credentials are not valid

    • If you use special AWS IAM user credentials and this user does not have enough permissions required by BitNami Cloud Hosting system, BitNami will not be able to execute operations on your behalf.
    • If you changed / reset your AWS credentials (Access Key ID and Secret Access Key) with Amazon, you must also update them in BitNami Cloud Hosting.

    Required ports are not open

    Please make sure that ports 22 and 80 are open in your security group settings. If you need to keep those ports closed, please at least open them for IP address 184.72.221.134. It is sufficient to add the following

    entries in your Security Group:

    port  source IP address
    22     184.72.221.134/32
    80     184.72.221.134/32

    We use those ports to check if your server is available and to collect monitoring data.


    You can check the status of BitNami Cloud Hosting on our announcements page or you can follow our twitter account, @bitnami_status. You can also go to the AWS status page for the latest info on AWS: http://status.aws.amazon.com. As always, if you have questions or run into any issues you can contact us through our helpdesk.

     

    How can I add webmin to my server on BitNami Cloud Hosting?

    Webmin is a web-based interface for system administration for Unix. Using any modern web browser, you can setup user accounts, Apache, DNS, file sharing and much more. Webmin is not currently included when BitNami Cloud Hosting servers are built, but you can add it by doing the following:

    $ wget http://www.webmin.com/download/webmin-current.tar.gz
    
    • Install the dependencies and uncompress the tarball:
    $ sudo apt-get install perl5 libnet-ssleay-perl
    $ tar -xzvf webmin-current.tar.gz
    $ cd webmin-*
    
    • Run the installer and follow the instructions.
    $ sudo sh setup.sh
    
    • Once the setup process finished, you can access webmin with the user/password that you set during the installation process in the port 10000. This port is not accessible from the outside by default, you should create an SSH tunnel (recommended) or open the port in the server firewall
    • Once you can access the Webmin application, you must configure it to manage your BitNami services. Belows are the configuration files for Apache, MySQL and PostgreSQL servers:

    /etc/webmin/apache/config

    link_dir=
    test_manual=0
    show_list=0
    mime_types=/opt/bitnami/apache2/conf/mime.types
    access_conf=
    auto_mods=1
    stop_cmd=/opt/bitnami/apache2/scripts/ctl.sh stop
    virt_file=
    test_apachectl=1
    max_servers=100
    srm_conf=
    httpd_dir=/opt/bitnami/apache2
    start_cmd=/opt/bitnami/apache2/scripts/ctl.sh start
    show_order=0
    test_always=0
    httpd_conf=/opt/bitnami/apache2/conf/httpd.conf
    defines_file=/opt/bitnami/apache2/bin/envvars
    apachectl_path=/opt/bitnami/apache2/bin/apachectl
    show_names=0
    test_config=1
    apply_cmd=/opt/bitnami/apache2/bin/apachectl graceful
    httpd_path=/opt/bitnami/apache2/bin/httpd

    /etc/webmin/mysql/config

    date_subs=0
    max_text=1000
    perpage=25
    stop_cmd=/opt/bitnami/mysql/scripts/ctl.sh stop
    mysqldump=/opt/bitnami/mysql/bin/mysqldump
    nodbi=1
    mysql_libs=/opt/bitnami/mysql/lib
    max_dbs=50
    start_cmd=/opt/bitnami/mysql/scripts/ctl.sh start
    mysql_data=/opt/bitnami/mysql/data
    mysqlimport=/opt/bitnami/mysql/bin/mysqlimport
    access=*: *
    style=0
    my_cnf=/opt/bitnami/mysql/my.cnf
    mysqlshow=/opt/bitnami/mysql/bin/mysqlshow
    mysql=/opt/bitnami/mysql/bin/mysql
    nopwd=0
    add_mode=1
    passwd_mode=0
    blob_mode=0
    mysqladmin=/opt/bitnami/mysql/bin/mysqladmin

    /etc/webmin/postgresql/config (only if you have this service enabled)

    simple_sched=0
    sameunix=1
    date_subs=0
    max_text=1000
    perpage=25
    stop_cmd=/opt/bitnami/postgresql/scripts/ctl.sh stop
    pid_file=/opt/bitnami/postgresql/data/postmaster.pid
    hba_conf=/opt/bitnami/postgresql/data/pg_hba.conf
    psql=/opt/bitnami/postgresql/bin/psql
    plib=
    nodbi=1
    max_dbs=50
    start_cmd=/opt/bitnami/postgresql/scripts/ctl.sh start
    pass=
    dump_cmd=/opt/bitnami/postgresql/bin/pg_dump
    access=*: *
    webmin_subs=0
    style=0
    rstr_cmd=/opt/bitnami/postgresql/bin/pg_restore
    access_own=0
    basedb=template1
    login=postgres
    add_mode=1
    blob_mode=0

     

    After you have replaced the configuration files, you should click "Refresh Modules" on the left menu in the Webmin application.  You should see the "Apache Webserver",  "MySQL Database Server", "PostgreSQL Database Server) in the Servers tag, as shown below.

    webmin.png

    Which Browsers are Supported?

    BitNami Cloud Hosting currently supports the following browsers:

     
    Browser Version Comments

    FireFox

    ≥ 22.x We will continue to support the latest version.*

    Internet Explorer
    ≥ 8 We will continue to support the latest version.*

    Google Chrome
    ≥ 28.x.x.x We will continue to support the latest version.*

    Safari
    ≥ 5.x We will continue to support the latest version.*

    Opera
    n/a Partial support; some interactivity may be nonfunctional.

    *Users of older browser versions may find some functionality impaired/non-functioning in the Bitnami Cloud Hosting control panel.

    BitNami Stack

    BitNami Base Stack

    More detailed information about our base images changes, updated software, bundled components versions etc. can be found at this wiki page.

    What is the MySQL, PHP and Apache version installed in my machine

    You can find it out connecting to your machine via SSH and then executing the following command:

    $ /opt/bitnami/mysql/bin/mysql -V ; /opt/bitnami/apache2/bin/apachectl -V; /opt/bitnami/php/bin/php -v
    

    You can also take a look at our Base Stack page. We keep here the detailed changelog of the BitNami Cloud Hosting base images together with BitNami base stack components list.

    What is the MySQL password?

    The default MySQL root password is the same as the one specified in the machine build wizard (default: auto-generated more info). Once you ssh to your machine try to execute this:

    $ /opt/bitnami/mysql/bin/mysql -u root  -p
    

    Each application uses its own auto-generated db user. For example, in case of Drupal it is bn_drupal and you can find more info in the /opt/bitnami/apps/drupal/htdocs/sites/default/settings.php file.

    More info can be found here: MySQL component

    How to connect to the BitNami MySQL remotely?

    More info can be found here: How to connect to MySQL remotely and MySQL component

    What is the phpMyAdmin password

    The default login and password are:

    username/login: root  (for previous versions is "administrator")
    password: <user defined> (default: auto-generated more info)

    You can find more info about phpmyadmin in other sections of our wiki:

    Getting 1045 error when trying to login to phpmyadmin

    You can login to phpmyadmin only from the localmachine using the following credentials:

    login: administrator

    password: bitnami

    If you get #1045 error, you probably changed the default 'bitnami' password when building a new server. The phpmyadmin configuration database access section is not updated with your chosen password value. You can fix it following the steps below:

    SSH to your machine and modify the phpmyadmin config file: /opt/bitnami/apps/phpmyadmin/htdocs/config.inc.php.

    sudo vim /opt/bitnami/apps/phpmyadmin/htdocs/config.inc.php
    

    Change the default 'bitnami' password to the one chosen during the server build wizard. The following line:

    $cfg['Servers'][$i]['password'] = 'bitnami';
    

    should be changed to

    $cfg['Servers'][$i]['password'] = 'YOUR_APP_PASSWORD';
    

    What is the PostgreSQL password?

    The default PostgreSQL password for postgres user is the same as the one specified in the machine build wizard (default: auto-generated more info). Once you ssh to your machine try to execute this:

    $ /opt/bitnami/postgresql/bin/psql -U postgres
    

    Each application uses its own auto-generated db user. For example, in case of OSQA it is bn_osqa and you can find the password in the file /opt/bitnami/apps/osqa/settings_local.py.

    More info can be found here: PostgreSQL component

     

    What is the phpPgAdmin password? 

    The default login and password are:

    username/login: postgres (for previous versions is "administrator")
    password: <user defined> (default: auto-generated more info)

    You can find more info about phpmyadmin in other sections of our wiki:

    Configuring PHP script to send emails via external SMTP server

    How to send emails via Gmail account

    How can I set up a development environment for Ruby, PHP, or Java

    To get a ready-to-run development environment for PHP, Ruby on Rails or Java on BitNami Cloud Hosting, simply launch a server from the BitNami Cloud Hosting console without adding any applications to it. That will get you a server with what we call our 'base stack'. To see a full list of bundled components and versions, visit our Base Stack page.

    What is the JBoss console password?

    username/login: manager
    password: <user defined> (default: auto-generated more info)

    How to connect to the JBoss console?

    The JBoss console by default runs on port 9990. You may need to open the port 9990 followin this article:

    Please note that is not recommended to keep this port open, it is not a secure channel. You may consider creating an encrypted tunnel using SSH and then opening the port 9990 is not required. Please find the steps to open a SSH tunnel to the JBoss console below:

    • Get your SSH private key if you don't have it already (more info)
    • Create the SSH tunnel.
    • If you are in Linux or Mac you can run the following in a console in your local machine:
    $ ssh -v -N -L 9991:127.0.0.1:9990 -i bitnami_hosting.pem bitnami@your-server.bitnamiapp.com
    
    • On Windows you can use Putty. Follow the steps described here. Before opening the connection. Go to Connection -> SSH -> Tunnels, enter the values below and click "Add" button:
    Source port: "9991"
    Destination: "localhost:9990" 
    
    • Click Open

    How to activate Java and OpenOffice in the base server

    When launching the server without Java apps (like JasperServer or Alfresco), the Java environment is disabled. You have to execute the following commands to activate it.

    • Activate Apache Tomcat.
    sudo mv /opt/bitnami/apache-tomcat/scripts/ctl.sh.disabled /opt/bitnami/apache-tomcat/scripts/ctl.sh
    sudo /opt/bitnami/ctlscript.sh start tomcat
    
    • Decompress and enable Java.
    cd /opt/bitnami/
    sudo tar zxf java.tgz
    sudo rm java.tgz 
    
    • Decompress and enable OpenOffice if you need so.
    cd /opt/bitnami/
    sudo tar zxf openoffice.tgz
    sudo rm openoffice.tgz
    sudo /opt/bitnami/ctlscript.sh start openoffice
    

    How to activate subversion server

    The subversion server is already installed by default but it may be disabled. You can activate it executing the following commands:

    $ sudo mv /opt/bitnami/subversion/scripts/ctl.sh.disabled /opt/bitnami/subversion/scripts/ctl.sh
    $ sudo /opt/bitnami/ctlscript.sh start subversion
    /opt/bitnami/subversion/scripts/ctl.sh : subversion started at port 369

    If you want to access it remotely, you need to open port 3690 (read more how to open additional port), however it is not recommended for security reasons. Please note that you may consider accessing your subversion repositoreis in more secure way via SSH and then no subversion server running is required.

    What is the Tomcat Web Application Manager password? 

    The default login and password are:

    username/login: manager
    password: <user defined> (default: auto-generated more info)

    How to enable SSL to access through https?

    First, you need to have the SSL certificate and the SSL certificate key already in place. You can generate them on your own as explained in the next section, get them from one of many commercial cetrtificate authorities or use the dummy one that is set by default.

    Cloud Image/BitNami Hosting

    SSL is enabled by default with a dummy certificate. You can upload your own certificate and key files to the default locations:

    /opt/bitnami/apache2/conf/server.crt
    /opt/bitnami/apache2/conf/server.key

    Note that the server key may be already in the server if you followed the steps to create a certificate.

    If you use different file names, you should reconfigure the options SSLCertificateFile and SSLCertificateKeyFile in  /opt/bitnami/apache2/conf/bitnami/bitnami.conf.

    It may happen, that your certificate authority will provide you with the file of PEM-encoded Server CA Certificates. If it is the case, you will need to place this file in "/opt/bitnami/apache2/conf/server-ca.crt", and then edit the file "/opt/bitnami/apache2/conf/bitnami/bitnami.conf" to include the following line below the SSLCertificateKeyFile:

    SSLCertificateChainFile "/opt/bitnami/apache2/conf/server-ca.crt"
    

    Then restart the Apache server and try to access at "https://xyz.bitnamiapp.com".

    $ sudo /opt/bitnami/ctlscript.sh restart apache
    

    Note: You can find more info about how to upload and edit files in this page.

    Once you have copied all the server certificate files, you may make them readable by root user only with the following commands:

    $ sudo chown root:root /opt/bitnami/apache2/conf/server*
    $ sudo chmod 600 /opt/bitnami/apache2/conf/server*

    Native Installer

    SSL is enabled by default with a dummy certificate. You can upload your own certificate and key files to the default locations:

    /installdir/apache2/conf/server.crt
    /installdir/apache2/conf/server.key
    

    If you use different file names, you should reconfigure the options SSLCertificateFile and SSLCertificateKeyFile in  /installdir/apache2/conf/bitnami/bitnami.conf.

    It may happen, that your certificate authority will provide you with the file of PEM-encoded Server CA Certificates. If it is the case, you will need to place this file in /installdir/apache2/conf/server-ca.crt, and then edit the file /installdir/apache2/conf/bitnami/bitnami.conf to include the following line below the SSLCertificateKeyFile:

    SSLCertificateChainFile "/installdir/apache2/conf/server-ca.crt"
    

    Then restart the Apache server and try to access at "https://yourdomain.com".

    $ sudo /installdir/ctlscript.sh restart apache
    

    The path to the default configuration file is

    /installdir/apache2/conf/bitnami/bitnami.conf
    

    Virtual Machine

    SSL is enabled by default with a dummy certificate. You can upload your own certificate and key files to the default locations:

    /installdir/apache2/conf/server.crt
    /installdir/apache2/conf/server.key
    

    If you use different file names, you should reconfigure the options SSLCertificateFile and SSLCertificateKeyFile in  /installdir/apache2/conf/bitnami/bitnami.conf (or  /installdir/apache2/conf/extra/httpd-ssl.conf it doesn't exist).

    It may happen, that your certificate authority will provide you with the file of PEM-encoded Server CA Certificates. If it is the case, you will need to place this file in /installdir/apache2/conf/server-ca.crt, and then edit the file /installdir/apache2/conf/bitnami/bitnami.conf to include the following line below the SSLCertificateKeyFile:

    SSLCertificateChainFile "/installdir/apache2/conf/server-ca.crt"
    

    Then restart the Apache server and try to access at "https://yourdomain.com".

    $ sudo /installdir/ctlscript.sh restart apache
    

    The path to the default configuration file is

    /installdir/apache2/conf/bitnami/bitnami.conf
    

    Amazon Linux / RHEL

    Upload your certificate to the "/opt/bitnami/apache2/conf/server.crt" location and the certificate key file to "/opt/bitnami/apache2/conf/server.key". Server key may be already in the server if you followed the steps to create a certificate.

    Edit the options "SSLCertificateFile" and "SSLCertificateKeyFile" in /etc/httpd/conf.d/ssl.conf so they point to your certificate files:

    SSLCertificateFile /opt/bitnami/apache2/conf/server.crt
    
    SSLCertificateKeyFile /opt/bitnami/apache2/conf/server.key

    It may happen, that your certificate authority will provide you with the file of PEM-encoded Server CA Certificates. If it is the case, you will need to place this file in /opt/bitnami/apache2/conf/server-ca.crt, and then uncomment and configure the option SSLCertificateChainFile in /etc/httpd/conf.d/ssl.conf:

    SSLCertificateChainFile "/opt/bitnami/apache2/conf/server-ca.crt"

    Then restart the Apache server and try to access at "https://xyz.bitnamiapp.com".

    $ sudo /opt/bitnami/ctlscript.sh restart apache
    

    Note: You can find more info about how to upload and edit files in this page.

    Once you have copied all the server certificate files, you may make them readable by root user only with the following commands:

    $ sudo chown root:root /opt/bitnami/apache2/conf/server*
    $ sudo chmod 600 /opt/bitnami/apache2/conf/server*

    Tabs end

    For Amazon instances you'll need to add the port 443 to your security groups, see the following link:

    http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html#adding-security-group-rule

     

    Note: If you use a custom domain for your server or you application URL location was changed from /myapp to the root  /, you should make sure that the ServerName option is set to "your domain" and DocumentRoot points to the application htdocs directory for the default VirtualHost in the file apache2/conf/bitnami/bitnami.conf (or apache2/conf/extra/httpd-ssl.conf if it doesn't exist). For example, if you have a Wordpress application configured in the root URL with the www.example.com domain, it will look as below: 
    <VirtualHost _default_:443>
    #   General setup for the virtual host
    DocumentRoot "/opt/bitnami/apps/wordpress/htdocs"
    ServerName www.example.com:443
    

     

    Note2: You can configure per application certificates if you use Virtual Host configutarion. To enable Virtual Host in your application, follow the steps here http://wiki.bitnami.com/Components/Apache#How_to_create_a_Virtual_Host.3f

    After that, you have to add the following lines in the 443 Virtual Host (or the one you want to be accessed through HTTPS). Change the path if necessary

    SSLEngine on
    SSLCertificateFile "/opt/bitnami/apps/wordpress/conf/certs/server.crt"
    SSLCertificateKeyFile "/opt/bitnami/apps/wordpress/conf/certs/server.key"
    

    How to create a SSL certificate?

    You can create your own SSL certificate with the OpenSSL binary. A certificate request can then be sent to a certificate authority to get it signed into a certificate, or if you have your own certificate authority, you may sign it yourself, or if you need a self-signed certificate (because you just want a test certificate or because you are setting up your own CA).

    Native Installer

    First create your private key (if you haven't created it already):

    $ /installdir/common/bin/openssl genrsa -out /installdir/apache2/conf/server.key 2048 
    

    The certificate request is created like this:

    $ /installdir/common/bin/openssl req -new -key /installdir/apache2/conf/server.key -out /installdir/apache2/conf/cert.csr
    

    Important: You should enter the server domain when the above command asks for the "Common Name"

    Now, cert.csr can be sent to the certificate authority. When the certificate authority has then done the checks they need to do (and probably gotten payment from you), they will hand over your new certificate to you.

    In the meantime, until you get your certificate, you will need to create a temporary self-signed certificate:

    $ /installdir/common/bin/openssl x509 -in /installdir/apache2/conf/cert.csr -out /installdir/apache2/conf/server.crt -req -signkey /installdir/apache2/conf/server.key -days 365
    
     
    If you want to back up your private key in a safe location, you may generate a password protected version as follows: (Note that if you use this encrypted key in the Apache onfiguration you will need to enter the password manually on every Apache startup)
    $ /installdir/common/bin/openssl rsa -des3 -in /installdir/apache2/conf/server.key -out privkey.pem
     

    VMware and Cloud

    First create your private key  (if you haven't created it already):

    $ sudo /opt/bitnami/common/bin/openssl genrsa -out /opt/bitnami/apache2/conf/server.key 2048
    

    The certificate request is created like this:

    $ sudo /opt/bitnami/common/bin/openssl req -new -key /opt/bitnami/apache2/conf/server.key -out /opt/bitnami/apache2/conf/cert.csr

    Important: You should enter the server domain when the above command asks for the "Common Name"

    Now, cert.csr can be sent to the certificate authority. When the certificate authority has then done the checks they need to do (and probably gotten payment from you), they will hand over your new certificate to you.

    In the meantime, until you get your certificate, you will need to create a temporary self-signed certificate:

    $ sudo /opt/bitnami/common/bin/openssl x509 -in /opt/bitnami/apache2/conf/cert.csr -out /opt/bitnami/apache2/conf/server.crt -req -signkey /opt/bitnami/apache2/conf/server.key -days 365
    
     
    If you want to back up your private key in a safe location, you may generate a password protected version as follows:
    $ sudo /opt/bitnami/common/bin/openssl rsa -des3 -in /opt/bitnami/apache2/conf/server.key -out privkey.pem
    

    Note that if you use this encrypted key in the Apache configuration you will need to enter the password manually on every Apache startup. You can regenerate the key without password protection from this file as follows:

    $ sudo /opt/bitnami/common/bin/openssl rsa -in privkey.pem -out /opt/bitnami/apache2/conf/server.key
    

     

    Note:  If you are using Amazon Linux or RedHat Enterprise you should replace "/opt/bitnami/common/bin/openssl" with "openssl" in the commands above.

    Tabs end
     

     

    You can find more info about certificates at http://www.openssl.org.
     

    How to force the HTTPS access?

    Apache

    How to confgure multiple SSL domains on the same IP address?

    Apache

    BitNami Applications

    What are the default login and passwords for BitNami applications

    Note: The below is only for BitNami Cloud Hosting. If you are using a BitNami Virtual Appliance or a BitNami AMI check the product page in bitnami.com for each product.

    All your choosen applications on each server share the same login and password. The image below shows the part of the server setup interface. You can choose your own username and password when configuring a server by clicking on the 'Application Options' button.

    bitnami-set-password.png

     

    The new dialog will pop up. You can set your applications login and password here. If you don't configure a username and password, a random password will be generated for you and the login will be 'user'.

    Once the server is started, to view the password, go to the Servers section in the left menu, then select the server for which you want the password and click on the 'manage' button that appears. You will see that there is a 'show' link next to the word 'Application Credentials'. Click on that to view the password. Please use both Application Login and Application Password to sign in to you aplications. Note: if you decide to set your own application password, it will not be available here.

    bitnami-cloud-hosting-default-password.png

    The default login and password for BitNami applications

    • login: user
    • password:  The one specified under Application Options or if none is, one will be automatically generated for you and will be available under the server manage screen.

    The applications listed below do not follow the default login/password policy. You can also click the application name in the server details  in the BitNami Cloud Hosting console to get the specific application credentials.

    JasperServer

    • login: jasperadmin
    • password: jasperadmin

    Liferay

    • login: username @liferay.com  Where username will be the one specified under Application Options or 'user' if none is.
    • password:  The one specified under Application Options or if none is, one will be automatically generated for you and will be available under the server manage screen. 

    ThinkUp and Spree

    • login: The email specified under 'Application Options' or your BitNami Cloud Hosting account email if none is.

    • password:  The one specified under 'Application Options' or if none is, one will be automatically generated for you and will be available under the server manage screen.

    eZ Publish and Plone

    • login: admin
    • password:  The one specified under Application Options or if none is, one will be automatically generated for you and will be available under the server manage screen.

    Where are my apps installed?

    BitNami Stack components (Apache, MySQL, PHP, Ruby ... ) are installed in /opt/bitnami directory.  You can find your web application files in the /opt/bitnami/apps location.

    You can also take a look at our Base Stack page. We keep here the detailed changelog of the BitNami Cloud Hosting base images together with BitNami base stack components list.

    Adding a new application to an existing server

    It is not currently possible to add another application to already created server via the BitNami Cloud Hosting console. However, you can add another application manually to a running server using the BitNami Modules. You can follow the steps below:

    • First, check if the BitNami Module installer is available in the stack page. Go to http://bitnami.com/stack/ruby/modules, select the application of your choice. Copy the download link for Linux 64-bit or 32-bit BitNami Module depending on the server architecture you are using. For example, if you want to add SugarCRM, you can go to the page http://bitnami.com/stack/ruby/modules#sugarcrm and copy Linux 64-bit URL:
    http://downloads.bitnami.com/files/stacks/sugarcrm/6.5.2-0/bitnami-sugarcrm-6.5.2-0-module-linux-x64-installer.run
    

    NOTE: If you can't find a "BitNami Module" available at bitnami.com for the application you want to include, contact us at http://helpdesk.bitnami.com.

    • Connect to your server via SSH. Learn more about how to connect
    • Download the module you want to install with "wget" and the URL you got from bitnami website:
    bitnami@domU-...:~$ wget http://downloads.bitnami.com/files/stacks/sugarcrm/6.5.2-0/bitnami-sugarcrm-6.5.2-0-module-linux-x64-installer.run
    --2011-02-21 10:22:36--  http://downloads.bitnami.com/files/stacks/sugarcrm/6.5.2-0/bitnami-sugarcrm-6.5.2-0-module-linux-x64-installer.run
    Resolving downloads.bitnami.com... 216.235.167.23
    Connecting to downloads.bitnami.com|216.235.167.23|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 12105939 (12M) [application/octet-stream]
    Saving to: `bitnami-sugarcrm-6.5.2-0-module-linux-x64-installer.run'
    
    100%[==========================================================================>] 12,105,939  3.82M/s   in 3.0s    
    
    2011-02-21 10:22:40 (3.82 MB/s) - `bitnami-sugarcrm-6.5.2-0-module-linux-x64-installer.run' saved [12105939/12105939]
    
    • Make the application binary executable.
    bitnami@domU-...:~$ chmod a+x bitnami-sugarcrm-6.5.2-0-module-linux-x64-installer.run
    
    • Start the module installer with "sudo" in the folder /opt/bitnami: ( the MySQL password is the "Application Password" by default: more info )
    bitnami@domU-...:~$ sudo ./bitnami-sugarcrm-6.5.2-0-module-linux-x64-installer.run
    ----------------------------------------------------------------------------
    Welcome to the BitNami SugarCRM Module Setup Wizard.
    ----------------------------------------------------------------------------
    Installation folder
    
    Please choose a folder that contains an installation of BitNami LAMPStack.
    
    Select a folder []: /opt/bitnami
    
    ----------------------------------------------------------------------------
    Create Admin account
    Please enter the existing MySQL password for BitNami LAMPStack
    
    Password :
    
    ----------------------------------------------------------------------------
    Setup is now ready to begin installing BitNami SugarCRM Module on your computer.
    
    Do you want to continue? [Y/n]:
    
    ----------------------------------------------------------------------------
    Please wait while Setup installs BitNami SugarCRM Module on your computer.
    
     Installing
     0% ______________ 50% ______________ 100%
     #########################################
    
    ----------------------------------------------------------------------------
    Setup has finished installing BitNami SugarCRM Module on your computer.
    
    Launch BitNami SugarCRM Module [Y/n]: y
    
    • Your new appllication should be already available.

    NOTE: Please note that in most cases you can't install the same application module more than once (i.e Drupal or Joomla!). You will need to install and configure the application manually in this case. Please check the section about adding several instances of the same application.

    Remove an application from an existing server

    If you want to disable one of the applications you can remove or comment out the related 'Include' line in /opt/bitnami/apache2/conf/httpd.conf file and restart the Apache:

    # Include "/opt/bitnami/apps/sugarcrm/conf/sugarcrm.conf"
    
    $ sudo /opt/bitnami/ctlscript.sh restart apache
    

    Alternatevely, you can use the unistaller in the application directory to delete all application files and settings.

    $ sudo /opt/bitnami/apps/sugarcrm/uninstall
    

    Comments

    You must login to post a comment.