Skip to content

Troubleshooting

Luthfi Yufajjiru edited this page Oct 27, 2026 · 1 revision

Troubleshooting

Message Meaning / fix
... requires elevation: run it with sudo ... or from an Administrator terminal You ran init on a system install without elevation. Use sudo, or set MORROW_HOME for a per-user install
this needs more access to Morrow's files than you have The command changes something (or reads a secret) on a system install. Use sudo / an Administrator terminal
Morrow is not initialized. Please run 'morrow init' first. No database for the current mode. Check MORROW_HOME; system installs need sudo morrow init
cannot decrypt secured variable X: ... You cannot read the master key (not root/Administrator), or it was replaced. See Keys, backups and recovery
master key not found at ... The key file is missing. Restore it, or see Keys, backups and recovery
application X is already running with PID N It really is running. If the process died, Morrow notices and shows it as stopped
My app got -w DIR as an argument / the working directory was not set Morrow flags must come before the app name; everything after the executable goes to your app: morrow create -w DIR app exe --port 8080
... has no grant to submit X for Y An admin must run sudo morrow grant <you> --app Y --vars X
you cannot write to the inbox ... Ask an admin to add you to morrow-deploy / "Morrow Deployers", then log in again
the inbox is not enabled on this install An admin must run sudo morrow init --enable-inbox
X can make programs run other code, so it cannot be granted That name is on the denylist by design. Use a different variable name in your app
Submission shows rejected in morrow inbox The reason is in the last column: format, grant, replay, file type, etc.

← Uninstalling · FAQ →

Clone this wiki locally