Troubleshooting¶
Errors of the scheduled sync are shown at the top of the connector (Last sync failed) and in the Last Error column of the connector list. Test Connection and Sync Now show them right away. Each message contains OpenProject's own answer, with the HTTP status code.

"OpenProject refused the access token (401 ...)"¶
Cause: the token is wrong or was deleted, or the user of the token was locked.
Fix: create a new token (Configuration, step 1), paste it into the connector and click Test Connection.
"The access token may not do this (403 ...)"¶
Cause: the user of the token has a role in the project that does not allow viewing or editing work packages, adding comments or viewing members.
Fix: make the user a member of the project with a role that has these permissions (Administration → Users and permissions → Roles and permissions). Odoo can only do what that user can do in OpenProject.
"OpenProject answered /projects/... with 404 Not Found. Check the project identifier ..."¶
Cause: the OpenProject Project is not the identifier of the project, or the user of the token cannot see the project. OpenProject answers 404 instead of 403 for projects the user has no access to.
Fix: copy the identifier from the address of the project (https://openproject.example.com/projects/website
→ website), and make the user of the token a member of it.
"Could not reach OpenProject at https://...: ..."¶
Cause: the Odoo server cannot open a connection to OpenProject. The reason at the end says why:
- the host name does not resolve: a typo in the OpenProject URL, or the name only exists in another network;
- the connection was refused or no answer within 60 seconds: a firewall, a proxy, or OpenProject is down;
- the TLS certificate of the server is not trusted: your OpenProject uses a self-signed certificate or one of an internal certificate authority.
Fix: open the URL from the Odoo server (curl -I https://openproject.example.com). For an internal certificate
authority, add it to the trust store of the Odoo server (update-ca-certificates, and for Python's requests
REQUESTS_CA_BUNDLE).
"OpenProject answered with a redirect: check the URL ..."¶
Cause: the address redirects, for example from http:// to https://, or the URL has a path after the host name.
Fix: enter the address as OpenProject shows it in the browser, without a path: https://openproject.example.com.
A path is only right when OpenProject runs under a sub-path of its server.
"OpenProject is rate limiting this token, retry after N seconds"¶
Cause: HTTP 429. OpenProject limits the API requests of a user, and the token's user may also be used by other tools.
Fix: nothing: the next run continues. If it persists, raise Every (Minutes), use a user for Odoo only, or use the webhook and a longer interval.
"OpenProject refused the request (422 ...)" and "OpenProject did not accept the change"¶
Cause: OpenProject rejected the content of a work package: a status that the workflow does not allow from the current status for the roles of the token's user, a required custom field, or a finish date before the start date. For a change of an existing work package Odoo adds a note to the task with OpenProject's reason, and the other tasks go on.
Fix: allow the change in OpenProject (Administration → Work packages → Workflows), or correct the task. The note is the only message: Odoo does not send the change again.
"A sync of ... is already running, try again in a minute."¶
Cause: Sync Now was clicked while the scheduled sync or another user was syncing the same connector.
Fix: wait for the other run to finish.
Work packages do not become tasks¶
- Direction is Odoo to OpenProject.
- The type of the work package is not in Only Types.
- The work package is closed and Import Closed Work Packages is off.
- The connector is archived or Automatic is off: click Sync Now, or use the webhook.
- After changing Only Types, click Restart Import: work packages that were skipped before are only looked at again when they change.
Tasks do not become work packages¶
- Direction is OpenProject to Odoo.
- The task was created before Export Records Created After. Set an earlier date (or clear the field) to export older tasks at the next sync.
- The task is in another project than the connector's, or it is archived.
Changes made in Odoo do not reach OpenProject¶
The OpenProject tab of the task shows Changes to Send to OpenProject until they are sent. If it stays filled, the connector shows an error (see above), or Automatic is off. With Direction OpenProject to Odoo changes are never sent.
Assignees are missing¶
The assignee in OpenProject has no Odoo user with that OpenProject Login (or e-mail address), or the Odoo user has no login filled in (Configuration, step 3). An assignee without a match leaves the task's assignees unchanged. In the other direction, Odoo needs to find the OpenProject user by login or e-mail address, and the user must be a member of the project to be assigned.
The stage does not follow the status¶
The stage is only set when a stage of the Odoo project has the name of the status. Check the spelling (case is ignored) and that the stage belongs to the connector's project.
The webhook fails¶
OpenProject lists every delivery under Administration → API and webhooks → Webhooks → the webhook → Show (Recent events).
| OpenProject shows | Cause | Fix |
|---|---|---|
| Hostname ... has no public ip addresses ... | OpenProject refuses to call a server in a private network | add the network of Odoo to the allowlist of OpenProject: the environment variable OPENPROJECT_SSRF_PROTECTION_IP_ALLOWLIST (e.g. 192.168.0.0/16), or give Odoo a public address |
| HTTP 403 | the signature secret in OpenProject differs from the connector's, or the connector is archived | copy the Webhook Secret again |
| HTTP 404 | the connector was deleted, or the URL points at another Odoo database | copy the Webhook URL again; with several databases on one server, use the database's own domain |
| connection errors, timeouts | OpenProject cannot reach Odoo: the URL uses an internal address, or a firewall blocks it | set web.base.url to the public HTTPS address of Odoo |
HTTP 200 with "status": "error" |
Odoo received the event but could not read the work package | see the connector's Last Error |
The scheduled sync picks up whatever the webhook missed.
Where to look¶
Odoo logs the addon under odoo.addons.openproject_sync_project. For more detail: