Unable to connect Canva to On-perm xibo

Hi team,

I am hitting the same issue as Canva not linking to Xibo - #2 by natasha

My Xibo is running on HTTPS (letsencrypt) and is publicbly avail.

Xibo logs does not log the attempt to login from canva/canva.xibosignage.com

url:
https:// xibo (dot) dechanz (dot) com

Error:

We have tried that address, but something is not right. Address not reachable

@Nadz are you able to comment on what this error message specifically might relate to please?

I tested this with our CMS and it worked fine, so I’m not sure how to reproduce the issue at the moment. From what I can see in the code, it might be failing to fetch the CMS version. I’ll need a bit more time to investigate this further.

Hi @dca, it looks like the issue happens when the CMS version check fails, which triggers the “address not reachable” message. We’ve checked your CMS’s /about endpoint which provides the CMS version and confirmed that it’s reachable and responding correctly. The issue might have been a temporary network problem or something specific to the environment at the time.

Could you please try connecting again and let us know if the issue still occurs?

its the same issue, I just tried:

1 Like

@Nadz yep still the same still

Hi @dca, sorry for the delay.

We’ve pushed an update to the system that adds more detailed logging for the CMS connection process. Since we’re not able to reproduce the issue on our side, this should help us finally see what’s causing the problem.

Could you please try connecting your CMS to the Canva app again and take note of the exact time you attempted it? Once you let us know the time, we can check the logs on our end and continue investigating.

Thank you for your patience.

I just tried again, and I tried in between

now it doesn’t even show the error this is the enitre screen:

there isn’t anything below now

thanks @Nadz! Hope we can identify the issue

Hi @dca,

Thanks for the update earlier. I wanted to follow up on the issue you mentioned. I tried connecting to your CMS on my side as well, just to check whether the Registration form appears. In my case, the Registration form shows up just below the Address field, as shown in the screenshot:

When you saw that screen earlier, do you remember if you were able to scroll down the page? It’s possible the Registration form was displayed further down, so I just want to confirm what you saw on your end.

I was, the register your cms section disappears after entering the credentials and no further errors are shown

@nadz I think this new behaviour matched up with after you guys enabled the extra logging, does seem a little strange

Hi @dca,

Just to be clear about what you mentioned. After entering the credentials and the “Register your CMS” section disappeared, did it not move to the next step where it should ask you to grant permission? That prompt should normally appear right after submitting the credentials.

The extra logging we added shouldn’t change the behaviour at all since it doesn’t modify any of the logic or process. I just want to confirm what happened after the form disappeared on your side.

Can you try it one more time and let us know the exact time you attempted it? We’ll check the logs on our end and hopefully identify what’s causing the issue. Thank you.

Here is what I experience right now:

I’ve cleared cache and deleted cookies, even using a different browser (firefox vs chrome) it looks the same

Happy new year!

Looks like no change so far @Nadz

I’m also experiencing the same issue:

@Nadz @dan Can you please roll out a fix?

Hi @AlexDev404,

We previously added more detailed logging around the CMS connection process to help track cases like this. Since we haven’t been able to reproduce the issue on our side, those logs should help us understand what’s happening during your attempt.

Could you please try connecting your CMS to the Canva app again and let us know the exact date and time of your attempt? We’ll review the logs and continue investigating from there.

I pressed the connect button at 4.07pm Singapore time, 20 Feb 2026
the error is now “We have tried that address, but something is not right. Address not reachable”

Hi @Nadz , thanks for replying. Here is all the relevant information you requested, along with the HTTP headers:

TIMESTAMP: Sat, 21 Feb 2026 00:21:37 GMT


HTTP Headers:

## GENERAL

Request URL
https://canva.xibosignage.com/register

Request Method
POST

Status Code
422 Unprocessable Content

Remote Address
[2001:41d0:800:a0::]:443

Referrer Policy
strict-origin-when-cross-origin

-----------------------------------------------------------------

## RESPONSE HEADERS
----------------------

cache-control
no-store, no-cache, must-revalidate

content-length
132

content-security-policy
frame-ancestors 'self'

content-type
application/json

date
Sat, 21 Feb 2026 00:21:37 GMT

expires
Thu, 19 Nov 1981 08:52:00 GMT

pragma
no-cache

referrer-policy
strict-origin-when-cross-origin

server
nginx

strict-transport-security
max-age=31536000; includeSubDomains

strict-transport-security
max-age=31536000

x-content-type-options
nosniff

x-frame-options
SAMEORIGIN

-----------------------------------------------------------------

## REQUEST HEADERS
----------------------

:authority
canva.xibosignage.com

:method
POST

:path
/register

:scheme
https

accept
*/*

accept-encoding
gzip, deflate, br, zstd

accept-language
en-US,en;q=0.9,en-GB;q=0.8

cache-control
no-cache

content-length
415

content-type
application/x-www-form-urlencoded; charset=UTF-8

cookie
__cf_bm=l_9fZHrboUAXhErHomO6dztvVmgDQTT9TZIFA3T5LSg-1771632866-1.0.1.1-CYhiMemFDYKDld8sFZvHrnXgLomAJZGRmLEStXCU9zMHDQTj3HPSekmdPF6CVkI1U9.jbVH60sl4G.dK5DcvyeR.kicc1D4JHb7hby8ts1k; _cfuvid=iFZ1zPUcHg.lPI7QHHFHSXpAbT3QeeYsx9SZ.2VFG1Q-1771632866582-0.0.1.1-604800000; CanvaSession=<REDACTED>

origin
https://canva.xibosignage.com

pragma
no-cache

priority
u=1, i

referer
https://canva.xibosignage.com/authenticate?
user=AVpssAvFZ19VRO6Z6mFKfZRWP5uL8o-4UYGi3wbs558%3D%7Cv2&brand=AVpssAsmsgGLsIrP0y-jF65XDghPiqEANARKkeKK1Cg%3D%7Cv2&extensions=PUBLISH&time=1771633278&state=eKdK4TDxgzBs63_7d9sjf5nJBq5BL0hrUgsYgh09UDU_LCTEjNOQTK07aq-eGGilIg3XIInRzVSrsrBUxE82j4CoNDTDGU-qxvlBLlnbDuwy5UkKnfHivJn1WdwDcLNWpYVfeGAgyzc7hMw64R8sic6V4oHhd9lbLbMU4v9IX_9fGoRxXVBzJNRShhFvXjYPKW-x3OiAcW1a7ftYrSXQOhh_X-kP15lfyMYaQugIJW3Sveb7YjK-fuK806Czj0vASQ0iCBwoXskBxie9o70S34dpii1m_RGBbz0-xYotbarxY2Yxp9j5y1MebibjCkza25d9XA&signatures=7bf52679086bd766e5bdae6e16650905590dc6f3e8fec01f90b5e57c4c70f8dd&nonce=7a2cae4c647dd9ea53d4e30b0d9784a9

sec-ch-ua
"Not:A-Brand";v="99", "Microsoft Edge";v="145", "Chromium";v="145"

sec-ch-ua-mobile
?0

sec-ch-ua-platform
"Windows"

sec-fetch-dest
empty

sec-fetch-mode
cors

sec-fetch-site
same-origin

user-agent
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0

x-requested-with
XMLHttpRequest