Troubleshooting and FAQ

Start with the operation’s visible error and the selected installation’s diagnostics. Record the FluxPlugs version, Fluxer version, operating system, and steps that reproduce the problem.

No installation was found

Add the installation root and choose Scan for installs again. Check that you selected the Electron desktop installation rather than a browser shortcut, plugin directory, or source checkout.

FluxPlugs is missing in Fluxer

Confirm you launched the same installation shown in the injector. Choose Check status. A Fluxer update may have replaced the injection; follow the update guide.

Fluxer will not close

Close Fluxer requests a graceful shutdown and leaves it closed. If it is still running after 20 seconds, the injector can offer a separate force-quit confirmation. Force quit may discard unsaved work. Injection and restoration manage stopping and relaunching themselves.

A preview or backup was rejected

A stale preview requires another review. An invalid backup requires resolving the reported condition, not another attempt to force restoration. See restoration.

A plugin cannot import or enable

Use the author’s packaged ZIP, not an archive of their entire source tree. Check the manifest, API compatibility, integrity error, and requested capabilities. Reimported code always requires fresh approval.

If ZIP selection is unavailable, update the injected runtime. If an image fails, use an accepted public HTTPS PNG; private hosts and unsupported formats are rejected.

Frequently asked questions

Must the injector stay open? No. Plugins run inside Fluxer’s runtime after injection.

Does a hash mean a plugin is safe? No. It identifies code; it does not establish author trust.

Does Remove erase all data? No. Separate plugin storage is retained.

Can I use this on macOS or the web client? Not in this beta.

For unresolved problems, open an issue. Include diagnostics, but remove credentials, signed attachment URLs, and personal paths.