How to Host Odoo on a VPS: A Practical Setup Walkthrough

• DigitalOcean, Bangalore region, dependable performance and simple pricing, with 4 GB RAM near 1700 rupees a month.
• Hetzner, strong price to performance, with 8 GB RAM near 1200 rupees a month. No India data centre, but Europe latency is fine for most teams.
• AWS Lightsail, Mumbai region, a simplified slice of AWS infrastructure with predictable billing, near 2500 rupees a month for 4 GB RAM.
• Hostinger, Contabo and similar budget providers, very cheap at 500 to 1000 rupees for 4 GB RAM, but shared resources are often oversold. Fine for a trial, risky for production.

• Update packages with sudo apt update && sudo apt upgrade -y and set the timezone with sudo timedatectl set-timezone Asia/Kolkata.
• Create a non root user if one does not already exist, then add it to the sudo group.
• Lock down SSH by disabling root login and password authentication so only key based access works.
• Enable the firewall with sudo ufw allow OpenSSH && sudo ufw allow 'Nginx Full' && sudo ufw enable.

• PostgreSQL with sudo apt install postgresql -y.
• Python and build tools with sudo apt install python3-pip python3-dev python3-venv build-essential libxml2-dev libxslt1-dev libpq-dev libjpeg-dev zlib1g-dev -y.
• wkhtmltopdf for PDF reports, using the build recommended in Odoo's own documentation rather than the default apt package.
• Node.js, npm and Git with sudo apt install nodejs npm git -y.

• Create a dedicated system user with sudo useradd -m -d /opt/odoo -U -r -s /bin/bash odoo, and never run the service as root.
• Give that user database rights with sudo su - postgres -c "createuser -s odoo".
• Switch to the odoo user and clone the source with git clone https://github.com/odoo/odoo.git --depth 1 --branch RELEASE_BRANCH /opt/odoo/odoo-server, choosing the branch that matches your release.
• Install the Python requirements with pip3 install -r /opt/odoo/odoo-server/requirements.txt.

• Create /etc/odoo-server.conf with contents like this.

[options]
admin_passwd = your_strong_master_password
db_host = False
db_port = False
db_user = odoo
db_password = False
addons_path = /opt/odoo/odoo-server/addons
logfile = /var/log/odoo/odoo-server.log
data_dir = /opt/odoo/.local/share/Odoo

• Lock permissions with sudo chown odoo: /etc/odoo-server.conf && sudo chmod 640 /etc/odoo-server.conf.
• Create a systemd unit at /etc/systemd/system/odoo-server.service, then run sudo systemctl daemon-reload && sudo systemctl enable odoo-server && sudo systemctl start odoo-server.
• Confirm it started with sudo systemctl status odoo-server, which should read active and running.

• Open http://your-server-ip:8069 in a browser to reach the database creation screen.
• Enter a database name, the master password from your configuration file, an admin email and a strong admin password, then pick your country and default language.
• Once the database exists, install only the apps you need, such as CRM, Sales, Inventory or Accounting, from the Apps menu.
• In production, set list_db = False so the database manager page is hidden from anonymous visitors.
• Change the master password to something long and unique, since anyone holding it can manage any database on the server.

• Create an A record in your domain registrar pointing your chosen subdomain, for example erp.yourcompany.com, to the VPS IP address, which usually propagates within half an hour.
• Install Certbot with sudo apt install certbot python3-certbot-nginx -y.
• Request a certificate with sudo certbot --nginx -d erp.yourcompany.com, and Certbot will configure Nginx for HTTPS and handle renewal automatically every 90 days.
• Visit the site over HTTPS to confirm the padlock appears. If it does not, check the Nginx configuration and the Certbot logs for the exact error.

• Create /etc/nginx/sites-available/odoo with an upstream block for Odoo on 8069, an upstream block for the longpolling service on 8072, a redirect from port 80 to HTTPS, and a server block on port 443 with generous proxy timeouts for long running reports.

upstream odoo { server 127.0.0.1:8069; }
upstream odoochat { server 127.0.0.1:8072; }
server {
  listen 80;
  server_name erp.yourcompany.com;
  return 301 https://$host$request_uri;
}
server {
  listen 443 ssl;
  server_name erp.yourcompany.com;
  proxy_read_timeout 720s;
  client_max_body_size 200m;
  location / { proxy_pass http://odoo; proxy_set_header Host $host; }
  location /websocket { proxy_pass http://odoochat; proxy_set_header Upgrade $http_upgrade; }
}

• Enable the site with sudo ln -s /etc/nginx/sites-available/odoo /etc/nginx/sites-enabled/ and remove the default site.
• Test and reload with sudo nginx -t && sudo systemctl reload nginx.

• Set worker counts to match RAM, roughly two workers for 4 GB and four for 8 GB, since each worker consumes 150 to 300 MB.
• Set memory limits in the configuration file so a runaway process gets recycled rather than taking down the server.
• Tune PostgreSQL settings such as shared buffers and effective cache size to match available RAM.
• Configure log rotation for the Odoo log directory so it does not grow without bound.
• Keep max_cron_threads at 1 so scheduled actions do not eat into a regular worker slot.

• If server administration eats more than a few hours a month, that cost often exceeds the premium of a managed hosting and administration plan.
• If you deploy custom modules often and need real staging environments, building those by hand takes far longer than a managed platform where it is a single click.
• If you have had a close call, a failed backup, a security scare or an outage you could not resolve quickly, treat it as a signal the risk has outgrown your team.
• Your code sits on disk and your data sits in PostgreSQL, so both are portable whenever you graduate to a managed setup.