Bitnami Odoo Installer

NOTE: Before running the commands shown on this page, you should load the Bitnami stack environment by executing the installdir/use_APPNAME script (Linux and Mac OS X) or by clicking the shortcut in the Start Menu under "Start -> Bitnami APPNAME Stack -> Application console" (Windows). Learn more.
NOTE: When running the commands shown on this page, replace the installdir placeholder with the full installation directory for your Bitnami stack.

Description

Odoo is an open source ERP and CRM platform, formerly known as OpenERP, that can connect a wide variety of business operations such as sales, supply chain, finance, and project management.

Try the OS X VM for Mac (beta version). This new product makes it really easy to run this application on your Mac with just a few clicks. No VirtualBox needed! Find here further information on this.

First steps with the Bitnami Odoo Stack

Welcome to your new Bitnami application! Here are a few questions (and answers!) you might need when first starting with your application.

What are the system requirements?

Before you download and install your application, check that your system meets these requirements.

How do I install the Bitnami Odoo Stack?

Windows, OS X and Linux installer
  • Download the executable file for the Bitnami Odoo Stack from the Bitnami website.

  • Run the downloaded file:

    • On Linux, give the installer executable permissions and run the installation file in the console.
    • On other platforms, double-click the installer and follow the instructions shown.

Check the FAQ instructions on how to download and install a Bitnami Stack for more details.

The application will be installed to the following default directories:

Operating System Directory
Windows C:\Bitnami\APPNAME-VERSION
Mac OS X /Applications/APPNAME-VERSION
Linux /opt/APPNAME-VERSION (running as root user)
OS X VM
  • Download the OS X VM file for the Bitnami Odoo Stack from the Bitnami website.
  • Begin the installation process by double-clicking the image file and dragging the WordPress OS X VM icon to the Applications folder.
  • Launch the VM by double-clicking the icon in the Applications folder.

What credentials do I need?

You need application credentials, consisting of a username and password. These credentials allow you to log in to your new Bitnami application.

What is the administrator username set for me to log in to the application for the first time?

  • For Windows, Linux and OS X installers, the username was configured by you when you first installed the application.
  • For OS X VMs, the username can be obtained by clicking the Bitnami badge at the bottom right corner of the application welcome page.

What is the administrator password?

  • For Windows, Linux and OS X installers, the password was configured by you when you first installed the application.
  • For OS X VMs, the password can be obtained by clicking the Bitnami badge at the bottom right corner of the application welcome page.

What is the default configuration?

Odoo application

A new database will be created during the deployment process.

Linux and Mac OS X

The Odoo package is installed at installdir/apps/odoo/lib/odoo-version.egg.

Windows

The Odoo package is installed at installdir/apps/odoo/lib/site-packages/odoo-version.egg.

Odoo configuration file

The Odoo server configuration file is at installdir/apps/odoo/conf/odoo-server.conf.

NOTE: The configuration file name changed since the Odoo 10 version was released. If you are using a prior version, the configuration file is at installdir/apps/odoo/conf/openerp-server.conf.

Odoo servers

By default, two Odoo servers run:

  • odoo_background_worker, which controls the scheduled actions

  • odoo_gevent, which handles the Instant Message connections. Its port can be found in the Odoo configuration file in the longpolling_port variable.

Odoo log

The Odoo logs are located at installdir/apps/odoo/log.

How to start or stop the services?

Linux

Bitnami native installers include a graphical tool to manage services. This tool is named manager-linux-x64.run on Linux and is located in the installation directory. To use this tool, double-click the file and then use the graphical interface to start, stop or restart services. Server log messages can be checked in the "Server Events" tab.

Management tool

The native installer also includes a command-line script to start, stop and restart applications, named ctlscript.sh. This script can be found in the installation directory and accepts the options start, stop, restart, and status. To use it, log in to the server console and execute it following the examples below:

  • Call it without any service names to start all services:

      $ sudo installdir/ctlscript.sh start
    
  • Use it to restart a specific service only by passing the service name as argument - for example, mysql, postgresql or apache:

      $ sudo installdir/ctlscript.sh restart mysql
      $ sudo installdir/ctlscript.sh restart postgresql
      $ sudo installdir/ctlscript.sh restart apache
    
  • Obtain current status of all services:

      $ installdir/ctlscript.sh status
    

The list of available services varies depending on the required components for each application.

Mac OS X

Bitnami native installers include a graphical tool to manage services. This tool is named manager-osx on Mac OS X and is located in the installation directory. To use this tool, double-click the file and then use the graphical interface to start, stop or restart services. Server log messages can be checked in the "Server Events" tab.

Management tool

The native installer also includes a command-line script to start, stop and restart applications, named ctlscript.sh. This script can be found in the installation directory and accepts the options start, stop, restart, and status. To use it, log in to the server console and execute it following the examples below:

  • Call it without any service names to start all services:

    $ sudo installdir/ctlscript.sh start
    
  • Use it to restart a specific service only by passing the service name as argument - for example, mysql or apache:

     $ sudo installdir/ctlscript.sh restart mysql
     $ sudo installdir/ctlscript.sh restart apache
    
  • Obtain current status of all services:

     $ installdir/ctlscript.sh status
    

The list of available services varies depending on the required components for each application.

NOTE: If you are using the stack manager for Mac OS X-VM, please check the following blog post to learn how to manage services from its graphical tool.

Windows

Bitnami native installers include a graphical tool to manage services. This tool is named manager-windows.exe on Windows and is located in the installation directory. To use this tool, double-click the file and then use the graphical interface to start, stop or restart services. Server log messages can be checked in the "Server Events" tab.

Management tool

The Windows native installer creates shortcuts to start and stop services created in the Start Menu, under "Programs -> Bitnami APPNAME Stack -> Bitnami Service". Servers can also be managed from the Windows "Services" control panel. Services are named using the format APPNAMESERVICENAME, where APPNAME is a placeholder for the application name and SERVICENAME is a placeholder for the service name. For example, the native installer for the Bitnami WordPress Stack installs services named wordpressApache and wordpressMySQL.

These services will be automatically started during boot. To modify this behaviour, refer to the section on disabling services on Windows.

How to find the master password?

For security reasons the master password is randomly generated during the installation of the application. To find the master password, view the installdir/apps/odoo/conf/odoo-server.conf configuration file and search for the line below, which contains the password:

admin_passwd = PASSWORD

To set another password:

  • Edit the installdir/apps/odoo/conf/odoo-server.conf file:

      $ sudo nano installdir/apps/odoo/conf/odoo-server.conf
    
  • Modify the line below and replace the PASSWORD placeholder with your desired password:

      admin_passwd = PASSWORD
    
  • Restart the Apache server:

      $ sudo installdir/ctlscript.sh restart apache
    
NOTE: The configuration file name changed since the Odoo 10 version was released. If you are using a prior version, the configuration file is at installdir/apps/odoo/conf/openerp-server.conf.

How to configure the Odoo timezone?

The Odoo server is forced to be UTC. The rendering of datetime values in the user's timezone is meant to be done on the client-side exclusively. You can configure the timezone per user in the user's "Settings" panel.

Odoo preferences

How to configure outbound email settings?

In order to configure outbound email, follow the steps below:

  • Browse to the Settings -> General settings -> Configure outgoing email server -> Create menu.

  • Fill the required information. The settings below configure Odoo to send emails through a Gmail account. Replace USERNAME and PASSWORD with your Gmail account username and password respectively.

       Description: smtp.gmail.com
    
       #### Connection Information
       SMTP Server: smtp.gmail.com
       SMTP Port: 587
    
       #### Security and Authentication
       Connection Security: TLS
       Username: USERNAME@gmail.com
       Password: PASSWORD
    
  • Save the changes.

To configure the application to use other third-party SMTP services for outgoing email, such as SendGrid or Mandrill, refer to the FAQ.

NOTE: If you are using Gmail as the outbound email server and have experienced issues trying to send emails correctly, check the How to troubleshoot Gmail SMTP issues to learn the causes of these issues and how to solve them.

How to install a plugin on Odoo?

NOTE: The steps in this section assume that you have logged in to Odoo.com. Log in now, or sign up for new account.

How to install a plugin on Odoo from the Admin panel?

You can install modules and addons from the admin panel of the application. To install a new module in Odoo, follow the next steps:

  • Log in to the Odoo administration panel and on the top menu bar, click "Apps":

    Install plugins from Administration panel

  • In the Apps menu, you will see the Odoo plugin catalog. Search for the plugin you want to install.

    Select an Odoo plugin to install

  • Click the "Install" button in the plugin you want to enable. If you are already logged in Odoo.com the installation will be automatically done. The plugin will appear as "Installed":

    Install a plugin on Odoo

How to manually install a plugin on Odoo?

If you can't find the plugin you want to install in the Odoo plugin catalog, you can upload and install a module from the command line. To do so, follow these instructions:

  • Navigate to the Odoo plugin catalog and select the version of the application you have installed (in this case, v10.0):

    Odoo Apps catalog

  • Select the plugin you want to install and download it (make sure that you are downloading a plugin compatible with the current version of Odoo).

    Download an Odoo plugin

  • Connect to the Odoo server through SSH. Refer to the FAQ for more information on this.
  • Once you have accessed the server, change to the following directory (note that xyz are placeholders of the current Odoo version):

    $ cd /apps/odoo/lib/odoo-10.0.xyz.egg/odoo
    
  • Change the permissions of the addons directory so you can move folders and files into it. Execute the following to get the right permissions:

     $ sudo chmod 777 /addons
    
  • Upload the unzipped directories and files. Follow these instructions to upload files to the server with SFTP.
  • Once you have uploaded the module into the /apps/odoo/lib/odoo-10.0.xyz.egg/odoo/addons directory, you need to make sure that you can manage the uploaded files as the daemon user. Execute the following command:

     $ sudo chown -R daemon:daemon addons/MODULE-FOLDER-NAME
    
  • Restore the permissions to the /apps/odoo/lib/odoo-10.0.xyz.egg/odoo/addons directory:

     $ sudo chmod 755 addons/
    
  • Log in to the Odoo administration panel and in the top menu bar, click "Settings":

Navigate to the Settings section

  • In the right corner, you will find a description of Odoo. Under that information, you will see both the "Activate developer mode" and the "Activate developer mode (with assets)". Click on any of these links (the "Activate the developer mode (with assets)") is recommended:

Activate the developer mode

NOTE: When you have the developer mode activated, you can see a bug icon in the upper right corner of the screen.

Developer mode activated

  • In the top menu bar, click "Apps". In the left side menu of the resulting screen, click "Update Apps List". Click "Update" in the Module Update dialog to start the process.

    Apps menu: update Apps list

  • Click the "Apps" menu item. The plugin should appear in the Apps list:

Plugin installed

  • Click the "Install" button in the plugin you want to enable. If you are already logged in Odoo.com the installation will be automatically done. The plugin will appear as "Installed":

    Install a plugin on Odoo

How to install the Live Chat module?

Follow these steps:

  • In the administration panel, click the "Apps" menu located in the upper-left margin and click "Install" button in the Website Live Chat module.

Install Website Live Chat Module

How to install Wkhtmltopdf?

Wkhtmltopdf is necessary for some Odoo functionality. To install it on your system, follow the steps described below.

  • Download the latest version of the package from the Wkhtmltopdf project releases page and install it. Replace the X.Y.Z placeholders with the latest version available for your platform.
NOTE: The latest version available of Wkhtmltopdf is not compatible with some Odoo functionalities in some Linux distributions. Please check what is the recommended version for your Linux distribution in the Odoo GitHub repository.
      $ wget https://github.com/wkhtmltopdf/wkhtmltopdf/releases/download/X.Y.Z/wkhtmltox-X.Y.Z_linux-generic-amd64.tar.xz
      $ tar -xvf wkhtmltox-X.Y.Z_linux-generic-amd64.tar.xz
  • Copy the binaries to the /usr/bin directory:

       $ sudo cp ./wkhtmltox/bin/wkhtmltoimage /usr/bin/
       $ sudo cp ./wkhtmltox/bin/wkhtmltopdf /usr/bin/
    
  • (Odoo 11.x only) Install the necessary dependencies:
    • Debian:

       $ sudo apt-get install zlib1g fontconfig libxrender1 libfreetype6 libxext6 libx11-6
      
    • CentOS:

       $ sudo yum install zlib-devel fontconfig libXext libXrender freetype freetype-devel libX11-devel
      
  • Restart all running servers:

     $ sudo sudo installdir/ctlscript.sh restart
     $ sudo sudo installdir/ctlscript.sh restart apache
    

Now, PDF options will be available in your Odoo application.

Troubleshooting

If you experience issues with display resolution on Linux platforms, they could be related to the xfonts-75dpi or xfonts-100dpi packages. Uninstall them by executing:

$ sudo dpkg --remove --force-depends xfonts-75dpi
$ sudo dpkg --remove --force-depends xfonts-100dpi

How to create a full backup of Odoo?

The Bitnami Odoo Stack is self-contained and the simplest option for performing a backup is to copy or compress the Bitnami stack installation directory. To do so in a safe manner, you will need to stop all servers, so this method may not be appropriate if you have people accessing the application continuously.

NOTE: If you want to create only a database backup, refer to these instructions for MySQL and PostgreSQL.

Backup on Linux and Mac OS X

Follow these steps:

  • Change to the directory in which you wish to save your backup.

     $ cd /your/directory
    
  • Stop all servers.

     $ sudo installdir/ctlscript.sh stop
    
  • Create a compressed file with the stack contents.

     $ sudo tar -pczvf application-backup.tar.gz installdir
    
  • Start all servers.

     $ sudo installdir/ctlscript.sh start
    
  • Download or transfer the application-backup.tar.gz file to a safe location.

You should now download or transfer the application-backup.tar.gz file to a safe location.

Backup on Windows

Follow these steps:

  • Stop all servers using the shortcuts in the Start Menu or the graphical manager tool.

  • Create a compressed file with the stack contents. You can use a graphical tool like 7-Zip or WinZip or just right-click the folder, click "Send to", and select the "Compressed (zipped) folder" option.

  • Download or transfer the compressed file to a safe location.

  • Start all servers using the shortcuts in the Start Menu or the graphical manager tool.

Restore on Linux and Mac OS X

Follow these steps:

  • Change to the directory containing your backup:

    $ cd /your/directory
    
  • Stop all servers.

    $ sudo installdir/ctlscript.sh stop
    
  • Move the current stack to a different location:

    $ sudo mv installdir /tmp/bitnami-backup
    
  • Uncompress the backup file to the original directory:

    $ sudo tar -pxzvf application-backup.tar.gz -C /
    
  • Start all servers.

    $ sudo installdir/ctlscript.sh start
    
IMPORTANT: When restoring, remember to maintain the original permissions for the files and folders. For example, if you originally installed the stack as the root user on Linux, make sure that the restored files are owned by root as well.

Restore on Windows

  • Change to the directory containing your backup:

       $ cd /your/directory
    
  • Stop all servers using the shortcuts in the Start Menu or the graphical manager tool.

  • Uninstall the previous services by executing the following command:

        $ serviceinstall.bat
    
  • Create a safe folder named Backups in the desktop and move the current stack to it. Remember to replace PATH with the right location of your folder:

        $ move installdir \PATH\Backups
    
  • Uncompress the backup file using a tool like 7-Zip or Winzip or just double-click the .zip file to uncompress it, and move it to the original directory.
  • Install services by running the following commands from an elevated command prompt:

      $ cd installdir
      $ serviceinstall.bat INSTALL
    
  • Start all servers using the shortcuts in the Start Menu or the graphical manager tool.

How to upgrade the Bitnami Odoo Stack?

It is strongly recommended that you create a backup before starting the update process. If you have important data, it is advisable that you create and try to restore a backup to ensure that everything works properly.

WARNING: The process described in this section, only works in the same major version of Odoo (i.e. upgrading from Odoo11.x.y to Odoo11.x.z). If you want to upgrade between Odoo Major versions (i.e. upgrading from Odoo10.x to Odoo11.y) please check the Odoo Community Forum and this Odoo Community Association project.
  • Go to your Odoo installation and instead of logging in, click "Manage Databases".

  • From this web interface, create a backup of the bitnami_odoo database.

  • Stop the running application.

  • Install a new version of Bitnami Odoo (or deploy a new server).

  • From the "Manage Databases" interface, restore the bitnami_odoo database.

  • Stop all servers except PostgreSQL and migrate your data as explained in the section on migration.

NOTE: The default database name changed since the Odoo 10 version was released. If you are upgrading a prior version, the default database name is bitnami_openerp.

Upgrade only Odoo in the Bitnami Odoo Stack

Linux and Mac OS X

This approach is not recommended because a new Odoo version may have new dependencies not included in your base stack.

NOTE: If you are using Odoo 10 or earlier, you need to replace the python3 command with python.
  • Download and install the latest Odoo version. For example:

    $ cd /tmp/
    $ wget http://nightly.odoo.com/10.0/nightly/src/odoo_10.0.latest.tar.gz
    $ tar zxvf odoo_10.0.latest.tar.gz
    $ cd odoo-10.0-VERSION
    $ sudo python3 setup.py install --prefix=installdir/apps/odoo --install-lib=installdir/apps/odoo/lib
    $ sudo chown -R daemon:daemon installdir/apps/odoo/lib
    
  • Change the line

     #!installdir/python/bin/.python2.7.bin
    

    to

     #!installdir/python/bin/python3
    

    in the installdir/apps/odoo/bin/odoo-bin file.

  • Update your configuration to point to this version of Odoo. Edit the installdir/apps/odoo/conf/odoo-server.conf file and replace the addons path to point to the new Odoo version.

Migrate data to the new Odoo installation

Once your Odoo installation have been updated, follow the steps below to migrate data to the new installation.

  • Stop monit and other services

     $ sudo monit quit
     $ sudo installdir/ctlscript.sh stop
     $ sudo installdir/ctlscript.sh start postgresql
    
  • Start the Odoo server with the following parameters:

     $ sudo su daemon -c "installdir/python/bin/python3 installdir/apps/odoo/bin/odoo-bin -c installdir/apps/odoo/conf/odoo-server.conf --workers 0 -d bitnami_odoo -u all &"
    
  • Wait until the server is completely started and the modules updated. You can check the start-up status in the Odoo log file as shown below:

     $ sudo tail -f installdir/apps/odoo/log/production.log
    

    The upgrade process is finished when the messages "INFO bitnami_odoo odoo.service: Hit CTRL-C again or send a second signal to force the shutdown" or "Odoo waiting for connections" appear in the log file.

  • Start all the servers:

    $ sudo installdir/ctlscript.sh start
    

Remember that when importing the data, you will also be importing the Odoo users, including the admin user and its password.

NOTE: The Odoo server configuration file, the Odoo log file and the default database name changed since Odoo 10 version. If you are using a prior version, the Odoo server configuration file is at installdir/apps/odoo/conf/openerp-server.conf, the Odoo log file is at installdir/apps/odoo/log/openerp-server.log and the default database name is bitnami_openerp.

How to create an SSL certificate?

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

Follow the steps below for your platform.

Linux and Mac OS X

NOTE: OpenSSL will typically already be installed on Linux and Mac OS X. If not installed, install it manually using your operating system's package manager.

Follow the steps below:

  • Generate a new private key:

     $ sudo openssl genrsa -out installdir/apache2/conf/server.key 2048
    
  • Create a certificate:

     $ sudo openssl req -new -key installdir/apache2/conf/server.key -out installdir/apache2/conf/cert.csr
    
    IMPORTANT: Enter the server domain name when the above command asks for the "Common Name".
  • Send cert.csr to the certificate authority. When the certificate authority completes their checks (and probably received payment from you), they will hand over your new certificate to you.

  • Until the certificate is received, create a temporary self-signed certificate:

     $ sudo openssl x509 -in installdir/apache2/conf/cert.csr -out installdir/apache2/conf/server.crt -req -signkey installdir/apache2/conf/server.key -days 365
    
  • Back up your private key in a safe location after generating a password-protected version as follows:

     $ sudo openssl rsa -des3 -in installdir/apache2/conf/server.key -out privkey.pem
    

    Note that if you use this encrypted key in the Apache configuration file, it will be necessary to enter the password manually every time Apache starts. Regenerate the key without password protection from this file as follows:

     $ sudo openssl rsa -in privkey.pem -out installdir/apache2/conf/server.key
    

Windows

NOTE: OpenSSL is not typically installed on Windows. Before following the steps below, download and install a binary distribution of OpenSSL.

Follow the steps below once OpenSSL is installed:

  • Set the OPENSSL_CONF environment variable to the location of your OpenSSL configuration file. Typically, this file is located in the bin/ subdirectory of your OpenSSL installation directory. Replace the OPENSSL-DIRECTORY placeholder in the command below with the correct location.

     $ set OPENSSL_CONF=C:\OPENSSL-DIRECTORY\bin\openssl.cfg
    
  • Change to the bin/ sub-directory of the OpenSSL installation directory. Replace the OPENSSL-DIRECTORY placeholder in the command below with the correct location.

     $ cd C:\OPENSSL-DIRECTORY\bin
    
  • Generate a new private key:

     $ openssl genrsa -out installdir/apache2/conf/server.key 2048
    
  • Create a certificate:

     $ openssl req -new -key installdir/apache2/conf/server.key -out installdir/apache2/conf/cert.csr
    
    IMPORTANT: Enter the server domain name when the above command asks for the "Common Name".
  • Send cert.csr to the certificate authority. When the certificate authority completes their checks (and probably received payment from you), they will hand over your new certificate to you.

  • Until the certificate is received, create a temporary self-signed certificate:

     $ openssl x509 -in installdir/apache2/conf/cert.csr -out installdir/apache2/conf/server.crt -req -signkey installdir/apache2/conf/server.key -days 365
    
  • Back up your private key in a safe location after generating a password-protected version as follows:

     $ openssl rsa -des3 -in installdir/apache2/conf/server.key -out privkey.pem
    

    Note that if you use this encrypted key in the Apache configuration file, it will be necessary to enter the password manually every time Apache starts. Regenerate the key without password protection from this file as follows:

     $ openssl rsa -in privkey.pem -out installdir/apache2/conf/server.key
    

Find more information about certificates at http://www.openssl.org.

How to enable HTTPS support with SSL certificates?

TIP: If you wish to use a Let's Encrypt certificate, you will find specific instructions for enabling HTTPS support with Let's Encrypt SSL certificates in our Let's Encrypt guide.
NOTE: The steps below assume that you are using a custom domain name and that you have already configured the custom domain name to point to your cloud server.

Bitnami images come with SSL support already pre-configured and with a dummy certificate in place. Although this dummy certificate is fine for testing and development purposes, you will usually want to use a valid SSL certificate for production use. You can either generate this on your own (explained here) or you can purchase one from a commercial certificate authority.

Once you obtain the certificate and certificate key files, you will need to update your server to use them. Follow these steps to activate SSL support:

  • Use the table below to identify the correct locations for your certificate and configuration files.

    Variable Value
    Current application URL https://[custom-domain]/
      Example: https://my-domain.com/ or https://my-domain.com/appname
    Apache configuration file installdir/apache2/conf/bitnami/bitnami.conf
    Certificate file installdir/apache2/conf/server.crt
    Certificate key file installdir/apache2/conf/server.key
    CA certificate bundle file (if present) installdir/apache2/conf/server-ca.crt
  • Copy your SSL certificate and certificate key file to the specified locations.

    NOTE: If you use different names for your certificate and key files, you should reconfigure the SSLCertificateFile and SSLCertificateKeyFile directives in the corresponding Apache configuration file to reflect the correct file names.
  • If your certificate authority has also provided you with a PEM-encoded Certificate Authority (CA) bundle, you must copy it to the correct location in the previous table. Then, modify the Apache configuration file to include the following line below the SSLCertificateKeyFile directive. Choose the correct directive based on your scenario and Apache version:

    Variable Value
    Apache configuration file installdir/apache2/conf/bitnami/bitnami.conf
    Directive to include (Apache v2.4.8+) SSLCACertificateFile "installdir/apache2/conf/server-ca.crt"
    Directive to include (Apache < v2.4.8) SSLCertificateChainFile "installdir/apache2/conf/server-ca.crt"
    NOTE: If you use a different name for your CA certificate bundle, you should reconfigure the SSLCertificateChainFile or SSLCACertificateFile directives in the corresponding Apache configuration file to reflect the correct file name.
  • Once you have copied all the server certificate files, you may make them readable by the root user only with the following commands:

     $ sudo chown root:root installdir/apache2/conf/server*
    
     $ sudo chmod 600 installdir/apache2/conf/server*
    
  • Open port 443 in the server firewall. Refer to the FAQ for more information.

  • Restart the Apache server.

You should now be able to access your application using an HTTPS URL.

How to force HTTPS redirection with Apache?

Add the following lines in the default Apache virtual host configuration file at installdir/apache2/conf/bitnami/bitnami.conf, inside the default VirtualHost directive:

<VirtualHost _default_:80>
  DocumentRoot "installdir/apache2/htdocs"
  RewriteEngine On
  RewriteCond %{HTTPS} !=on
  RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]
  ...
</VirtualHost>

After modifying the Apache configuration files:

  • Open port 443 in the server firewall. Refer to the FAQ for more information.

  • Restart Apache to apply the changes.

How to debug Apache errors?

Once Apache starts, it will create two log files at installdir/apache2/logs/access_log and installdir/apache2/logs/error_log respectively.

  • The access_log file is used to track client requests. When a client requests a document from the server, Apache records several parameters associated with the request in this file, such as: the IP address of the client, the document requested, the HTTP status code, and the current time.

  • The error_log file is used to record important events. This file includes error messages, startup messages, and any other significant events in the life cycle of the server. This is the first place to look when you run into a problem when using Apache.

If no error is found, you will see a message similar to:

Syntax OK

How to find the database credentials?

  • Database username: postgres.
  • Database password: The password entered during the installation process.

How to connect to the PostgreSQL database?

You can connect to the PostgreSQL database from the same computer where it is installed with the psql client tool.

$ psql -U postgres

You will be prompted to enter the *postgres* user password. This is the same as the [application password](/installer/faq#how-to-find-application-credentials).

How to add new databases?

Odoo include a built-in feature to add new databases from the "Manage databases" section.

In order to enable the Odoo scheduler for any database different from the default one (bitnami_odoo), add the new database in the file installdir/apps/odoo/conf/odoo-server.conf as follows (administrator permissions are needed for editing the file):

db_name = bitnami_odoo, newdatabase

After doing so, please restart the service odoo_background_worker:

$ sudo installdir/ctlscript.sh restart odoo_background_worker
NOTE: The Odoo server configuration file and the default database name changed since the Odoo 10 version was released. If you are using a prior version, the Odoo server configuration file is at installdir/apps/odoo/conf/openerp-server.conf and the default database name is bitnami_openerp.

How to configure domain-based database filters option?

Odoo can be configured to use sub-domain filtering so the users can run different Odoo databases on different sub-domains. This means you can have different Odoo websites/applications for different uses.

Odoo 10.x or higher

Linux and Mac OS X
  • Edit the installdir/apps/odoo/conf/odoo-server.conf file and change these parameters:

      db_name = False
      dbfilter = ^%d$
      proxy_mode = True
    
  • Edit the installdir/apps/odoo/scripts/odoo_background_worker.sh file and configure as shown below:

      SCHEDULER_START="$ODOO_HOME/bin/odoo-bin -c $ODOO_HOME/conf/odoo-server.conf --max-cron-thread 1 --db-filter=^%d$"
    
  • Edit the installdir/apps/odoo/scripts/odoo_gevent.sh file and add the following values:

      GEVENT_START="$ODOO_HOME/bin/odoo-bin gevent -c $ODOO_HOME/conf/odoo-server.conf --max-cron-thread 0 --db-filter=^%d$"
    
  • Add the following lines at the bottom of the installdir/apps/odoo/conf/httpd-app.conf file:

       <Proxy *>
         Order deny,allow
         Allow from all
       </Proxy>
       ProxyRequests Off
    
  • Restart all the services:

      $ sudo installdir/ctlscript.sh restart
    
Windows
  • Edit the installdir/apps/odoo/conf/odoo-server.conf and change these parameters:

      db_name = False
      dbfilter = ^%d$
      proxy_mode = True
    
  • Edit the installdir/apps/odoo/scripts/serviceinstall_odoo_background_worker.bat file and configure as shown below:

       "installdir/apps\scripts\winserv.exe" install "odooBackgrooundWorker" -start auto "installdir/apps\scripts\odoo-bin.bat" "-c" "installdir/apps\conf\odoo-server.conf" "--max-cron-thread" "1" "--db-filter=^%d$"
    
  • Edit the installdir/apps/odoo/scripts/serviceinstall_odoo_gevent.bat file and configure as shown below:

      "installdir/apps\scripts\winserv.exe" install "odooGevent" -start auto "installdir/apps\scripts\odoo-bin.bat" "gevent" "-c" "installdir/apps\conf\odoo-server.conf" "--max-cron-thread" "0" "--db-filter=^%d$"
    
  • Add the following lines at the bottom of the installdir/apps/odoo/conf/httpd-app.conf file:

       <Proxy *>
         Order deny,allow
         Allow from all
       </Proxy>
       ProxyRequests Off
    
  • Uninstall the old Services and install the new modified ones. Load the Bitnami stack environment and execute the following commands::

       $ installdir/apps/odoo/scripts/serviceinstall_odoo_background_worker.bat UNINSTALL
       $ installdir/apps/odoo/scripts/serviceinstall_odoo_background_worker.bat INSTALL
       $ installdir/apps/odoo/scripts/serviceinstall_odoo_gevent.bat UNINSTALL
       $ installdir/apps/odoo/scripts/serviceinstall_odoo_gevent.bat INSTALL
    
  • Restart all the services using the Windows Manager tool.

Odoo 9.x or earlier

  • Edit the installdir/apps/odoo/conf/openerp-server.conf file and change these parameters:

      db_name = False
      dbfilter = ^%d$
      proxy_mode = True
    
  • Edit the installdir/apps/odoo/scripts/openerp_background_worker.sh file and configure as shown below:

      SCHEDULER_START="$OPENERP_HOME/bin/openerp-server -c $OPENERP_HOME/conf/openerp-server.conf --max-cron-thread 1 --db-filter=^%d$"
    
  • Edit the installdir/apps/odoo/scripts/openerp_gevent.sh file and add the following values:

      GEVENT_START="$OPENERP_HOME/bin/openerp-gevent -c $OPENERP_HOME/conf/openerp-server.conf --max-cron-thread 0 --db-filter=^%d$"
    
  • Add the following lines at the bottom of the installdir/apps/odoo/conf/httpd-app.conf file:

       <Proxy *>
         Order deny,allow
         Allow from all
       </Proxy>
       ProxyRequests Off
    
  • Restart all the services:

    	$ sudo installdir/ctlscript.sh restart
    
nativeInstaller

Bitnami Documentation