Troubleshooting

A build failed

Open the branch's Logs tab and read build.log from the bottom up: the step that failed and the error are there.

Development : a red build with a running server usually means failing tests. It stays up so you can connect and look.

Production : any error during the update fails the deploy. The update backup is restored and the previous build keeps running (see Rollback ).

Fix the code and push again, or click Rebuild for a problem that wasn't in the code.

“The HTTPS certificate is still being issued”

A new address (a new branch, or the first build of a project) gets its certificate within about a minute of its first build. Wait a moment and click Connect again. For a custom domain, check that its status is Active in Settings → Custom domains .

Connect doesn't log me in

A Connect link is valid for one minute. If you see This connect link is invalid or has expired , go back and click Connect again.

Allow pop-ups for this site if no tab opens.

If the administrator was renamed or deactivated in Odoo, use Connect as (the arrow next to Connect) and pick another user, or Open login page .

No Connect button? The branch isn't running, or your role doesn't cover this stage (developers: development, testers: development and staging, admins: all three).

My module isn't found or installed

A module is a folder with a __manifest__.py , at most 3 folders deep in the repository. Folders starting with a dot are ignored, and so are modules with "installable": False . The build log lists every module found.

Modules in a submodule need access to that repository: for a private one, add a deploy key in Settings → Submodules , and use Settings → Repository access to check.

A module that depends on Enterprise apps needs Enterprise turned on.

On production, new modules aren't installed automatically: install them from Odoo's Apps .

A Python package is missing (requirements.txt)

Put a requirements.txt at the root of the repository, or in a folder of modules: every build installs them with pip. Pin versions so builds stay reproducible. A package that fails to install fails the build: the error is in build.log .

requirements.txt

phonenumbers==8.13.40

xlsxwriter>=3.1

On production, a change to requirements.txt also takes an update backup before restarting. A package installed by hand with pip install --user only lives in that build.

Some modules were skipped in production (*_demo)

When the production database is created, modules named like *_demo (for example my_shop_demo , demo_data ) are not installed, because they write sample records into your live database. Modules listed in Settings → Production database are skipped too. The build log names the skipped modules.

Install one anyway from Odoo's Apps if you need it. If a module you kept depends on it, Odoo installs it as a dependency.

My development build is gone (Dropped)

Development builds are removed 3 days after they were built, and staging builds after 30 days, to free the server. Click Rebuild , or push a commit.