Bug
Chronos Power-Up fails to initialize in Trello due to CORS error
Environment
- Browsers: Chrome, Safari
- OS: macOS, Windows
- Chronos version: unknown
Description
Since April 8, 2026 around 5:00 PM (France time), Chronos no longer loads in Trello.
It affects:
- all users in the workspace
- all boards
- at least two Trello accounts
- Chrome and Safari
- macOS and Windows
Trello works normally. Only Chronos fails to load.
Steps to reproduce
- Open a Trello board with Chronos enabled
- Wait for the board to finish loading
- Chronos does not render
- Click
Remove personal settings
- Reconnect
- Chronos still does not load
Actual behavior
Chronos does not load at all. No UI is rendered.
Expected behavior
Chronos should initialize and load normally inside Trello.
Console error
Access to XMLHttpRequest at 'https://api.chronos.it-pal.net/api/trello/initialize' from origin 'https://chronos.it-pal.net' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
AxiosError: ERR_NETWORK
POST https://api.chronos.it-pal.net/api/trello/initialize net::ERR_FAILED
Troubleshooting tried
- hard refresh
- logout/login
- incognito
- different browser
- different computer
- disabled extensions
- cleared cache/cookies
- reauthorize / Remove personal settings
None of the above changed the behavior.
Impact
This blocks the entire team from using Chronos in Trello.
Please confirm whether this is a backend/configuration issue and whether there is any workaround.
Thanks!
Bug
Chronos Power-Up fails to initialize in Trello due to CORS error
Environment
Description
Since April 8, 2026 around 5:00 PM (France time), Chronos no longer loads in Trello.
It affects:
Trello works normally. Only Chronos fails to load.
Steps to reproduce
Remove personal settingsActual behavior
Chronos does not load at all. No UI is rendered.
Expected behavior
Chronos should initialize and load normally inside Trello.
Console error
Troubleshooting tried
None of the above changed the behavior.
Impact
This blocks the entire team from using Chronos in Trello.
Please confirm whether this is a backend/configuration issue and whether there is any workaround.
Thanks!