Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Billy 53 posts 244 karma points c-trib
    Oct 28, 2021 @ 11:31

    uSync dashboard not loading


    I've created a clean Umbraco v9 installation. After that, installed uSync via NuGet (Install-Package uSync).

    When browsing to the dashboard via Settings - uSync the following error in console shows:

    umbraco-backoffice-js.js.v1:152 Error: [$controller:ctrlreg]$controller/ctrlreg?p0=uSyncSettingsDashboardController
        at umbraco-backoffice-js.js.v1:32
        at umbraco-backoffice-js.js.v1:123
        at ea (umbraco-backoffice-js.js.v1:105)
        at p (umbraco-backoffice-js.js.v1:96)
        at g (umbraco-backoffice-js.js.v1:90)
        at umbraco-backoffice-js.js.v1:89
        at (umbraco-backoffice-js.js.v1:326)
        at umbraco-backoffice-js.js.v1:42
        at Ca (umbraco-backoffice-js.js.v1:114)
        at p (umbraco-backoffice-js.js.v1:98) '

    enter image description here

    Any idea how to fix this? Already tried reinstalling. Thanks for the help.

  • Kevin Jump 2317 posts 14746 karma points MVP 8x c-trib
    Oct 28, 2021 @ 11:56
    Kevin Jump


    I would check the app_plugin files have been copied over as part of the build (should happen when you build or run dotnet build).


    There should be a uSync folder in app_plugins e.g

    enter image description here

    if these aren't copying then there probably something broken 😔 your build/package process

    break the cache

    Also you could increment the version for the runtime minification (this will break any caching of the js files that Umbraco might have made)

    In your appsettings.json file. under the "Umbraco" section.

      "RuntimeMinification": {
        "Version" : "2"

    run in debug

    to confirm you could run in debug, and instead of caching the files Umbraco will return them individually.

    again in the "Umbraco" section of the appsettings.json file

      "Hosting": {
        "Debug": true

    if there is anything wrong with the files / code this should at least pinpoint which file is the problem.

  • Billy 53 posts 244 karma points c-trib
    Oct 28, 2021 @ 12:03

    Breaking the cache and running in debug fixed this issue. Thanks a lot!

Please Sign in or register to post replies

Write your reply to: