Connector stuck on loading screen + existing data source shows "Unknown data source". Anyone Else?

Matomo Looker Studio connector
1

Hi everyone,

Is anyone else currently unable to use the Matomo Connector for Looker Studio? I’m hitting two issues at once:

  1. Existing report components that use a Matomo data source now show: “Unknown data source - The data source that this component belongs could not be loaded…This can happen if data sources have been deleted”
    Nothing has been deleted on my side and the data source still exists and shows “working”
  2. When I try to add the connector again (or reload the configuration), the configuration screen spins indefinitely and then shows: “There was an error fetching the configuration for this add-on” with a “Retry authorization”-button. Retrying doesn’t help, and it never finishes loading.

The second error happens before I even enter a URL or token and both issues reproduce across different Google accounts and browsers – including a fresh account that never used the connector before – so it doesn’t look like my setup. (For reference: self-hosted Matomo 5.11.2)

Is anyone else seeing this right now? And if you ran into it before, did you find a fix?

Thanks!

2 Likes
2

I have exactly the same issue and I have emailed Matomo.

If I get an answer, I’ll let you know.

Anyone else having the same issue?

2 Likes
3

Same here - i think its a problem with the connector itself - data sources i used yesterday are all “unknown” - so dont do anything rash - they probably need to fix the connector.

1 Like
4

I have had the same issue in the past and have it also ATM. Last time, it took a day to restore dashboards, but I didn’t do anything on my side.

1 Like
5

Quick update: this is resolved on my end.

Without any change on my side, the connector is working normally again – the configuration screen loads, the “Unknown data source” error is gone, and my dashboard is back to normal. Since nothing changed in my setup and it had failed across multiple Google accounts and browsers, it looks like it was a temporary issue on the connector/Matomo side that has now been fixed.

Posting this in case anyone else ran into the same thing – if your dashboard suddenly broke with these errors, it may just be worth waiting and retrying. Thanks!

1 Like
6

Same for me thank you!

1 Like