Troubleshooting

Fixes for common issues: the plugin failing to load on Unreal 5.8 (GetLastError 126, module could not be loaded), bridge unreachable, wrong editor targeted, license or activation problems, and plugin version mismatches.

Most issues come down to a handful of things: the plugin will not load, the editor is not open, you reached the wrong editor, the licence needs a sign-in, or an install is on an old build. Each has its own page below with the full fix.

Common fixes

Plugin failed to load (GetLastError 126)The editor stops at startup saying the module could not be loaded, with a missing UnrealEditor-WorldStreamingInsights.dll. Fixed by updating past 1.2.44.Bridge unreachable, editor not respondingA command cannot reach the editor. Usually it is not open yet, still compiling, or the plugin is disabled for that project.A command landed in the wrong projectMore than one editor is open and the CLI reached a different one. List them and pick the one you mean.The panel does not show ActiveSign-in, seats, offline grace, trial and subscription states, and what each one means in the editor panel.Version mismatch after an updateOdd behaviour, an unknown flag, or a missing command. Get the CLI and every engine install onto the same build.

Start here either way

These three answer most questions before you need any of the pages above. They tell you whether an editor is reachable, which one you are driving, and what is installed where.

Confirm the bridge is up and see which editor you reached:

bash

cfa health_check

Check this machine's sign-in and expiry:

bash

cfa whoami

See what is installed where and whether it is current:

bash

cfa plugin status

Tip

Still stuck? Email contact@codefizz.dev with the command you ran and its output.

Loading…

PreviousFAQ NextFor AI Agents