This looks like the same error with the dashboard.
Maybe @elek can elaborate if that fix would also fix this error.