Error codes

The agent rejected the project settings: a nolay.toml or form field, a name, a key or a value. The error text lists the fields.

What to do. Fix the listed fields in nolay.toml or in the project form and deploy again.

The code source failed validation: a wrong repository address or branch, or an empty archive or one over 200 MB.

What to do. Check the address and branch, or upload the archive again.

The agent cannot do this: it is older than the panel, the stack was not recognized, or the action is not available for this source.

What to do. Update the agent by running the install command again. If the stack was not recognized, add a Dockerfile or pick a builder by hand.

Unexpected agent error while running the command.

What to do. Retry. If it happens again, send journalctl -u nolay-agent -n 100 output to support.

The agent does not know this project yet: the desired state has not reached the server.

What to do. Wait a minute and retry. If the server is offline, bring it back online first.

Deploy refused: the project is suspended. The reason is in the error text.

What to do. Pay for the plan, free up room within the limit, or resume the project in the panel.

The agent could not fetch the code: the repository or archive is unreachable.

What to do. Check the repository address and the server outgoing network, upload the archive again.

No access to the repository.

What to do. For GitHub, connect the Nolay app to the repository. For other Git hosts add the NOLAY_GIT_TOKEN (HTTPS) or NOLAY_GIT_SSH_KEY (SSH) secret.

Branch or tag not found. The error text names the default branch.

What to do. Fix the branch in the project settings.

The repository has no commits.

What to do. Push the first commit and deploy again.

The agent could not stream logs: there are no containers or Docker is not answering.

What to do. Check that the project is running and open the logs again.

Backups are unavailable: the agent could not reach Docker at startup.

What to do. Check systemctl status docker and restart the agent: systemctl restart nolay-agent.

The agent secrets encryption key is not available on the server.

What to do. Run the install command again: it restores /etc/nolay/agent.key if it is missing.

This service key cannot be shown or changed.

What to do. The action is not available for this service.

The service is not running, so the password cannot be changed.

What to do. Start the service and retry.

The password change command inside the service failed, the old password still works.

What to do. Details are in the server events.

The agent has not started this service yet.

What to do. Wait for the service to start and retry.

Removing the service failed.

What to do. Retry. If it does not help, check Docker on the server.

The agent is not connected, the command was not sent.

What to do. Check the server: systemctl status nolay-agent. Retry once it is back online.

The agent did not accept the command.

What to do. Retry in a minute.

The agent did not answer in time.

What to do. Retry in a minute. If it keeps happening, check the server load and network.

This agent version cannot do this action.

What to do. Update the agent by running the install command again.

The current state does not allow the action, for example the tunnel is blocked by staff.

What to do. See the error text; for a block, contact support.

The agent connected with a wrong or revoked token.

What to do. Delete the server in the panel, create it again and run the new install command.

Too many connections from this address, the hub refuses for a while.

What to do. The agent reconnects on its own after a pause, nothing to do.

The server was deleted in the panel and the hub closed the connection.

What to do. If it was deleted by mistake, add it again and run the new install command.

Another agent connected with the same ID.

What to do. Make sure the install command was not run on two servers. Each server has its own command.

The token does not match the agent or was revoked.

What to do. Create the server in the panel again and run the new install command.

The tunnel is not enabled for this server.

What to do. Turn on the tunnel in the server settings.

The agent did not introduce itself in time or cannot keep up reading messages.

What to do. The agent reconnects on its own. If it repeats, check the server load.

The archive is larger than 200 MB.

What to do. Remove builds and dependencies such as node_modules from the archive.

The archive format is not supported. RAR and 7z are not accepted.

What to do. Pack the code as zip or tar.gz.

The file is empty.

What to do. Choose an archive with the project code.

Three uploads are already in progress.

What to do. Wait for the previous archive to deploy or retry later.

The upload storage has no room right now.

What to do. Try again in a few minutes.

Only organization owners and admins can upload archives.

What to do. Ask the owner for the admin role.

The connection dropped during the upload.

What to do. Check the network and upload again.

The project is suspended: it is over the plan limit.

What to do. Move to a bigger plan or delete extra projects.

The project is suspended: the subscription is not paid.

What to do. Pay for the plan in Billing, the project resumes.

The project was stopped by Nolay staff.

What to do. Contact support.

The deploy failed, the previous version keeps running.

What to do. Open the build log in the deploy window: the last error line usually names the cause.

The readiness check failed, the new version is not switched on.

What to do. Check the application port (run.port) and the health.path.

The container exited abnormally.

What to do. Open the project logs: the cause is in the last lines.

A background process failed to start.

What to do. Check the workers.cmd command and the project logs.

A scheduled job was skipped: the previous run is still going.

What to do. Make the interval longer or the job faster.

The backup failed.

What to do. Check the NOLAY_S3_* secrets and the server access to the storage.

Restore from backup failed.

What to do. Details are in the project events.

A catalog service failed to start.

What to do. Check free memory and disk on the server.

The server disk is over 85 percent full.

What to do. Remove old images with docker image prune or grow the disk.

Server memory is over 90 percent used.

What to do. Lower project limits or move to a server with more memory.

The agent has not answered for over 90 seconds. Projects keep running.

What to do. Check that the server is on and run systemctl status nolay-agent.

The installer was run without root.

What to do. Run the command with sudo.

The CPU architecture is not supported.

What to do. Use an x86_64 server.

The server is ARM. An aarch64 build exists but is not tested live.

What to do. Prefer an x86_64 server.

The server has no systemd.

What to do. Use an Ubuntu LTS or Debian 12 image.

The operating system is not supported.

What to do. Reinstall the server with Ubuntu LTS or Debian 12 or newer.

The OS version is too old.

What to do. Use Ubuntu 22.04 or newer, or Debian 12 or newer.

Less than 1 GB of memory.

What to do. Pick a VPS plan with 1 GB of memory or more.

Less than 5 GB free on /var/lib.

What to do. Free up space or grow the disk.

Port 80 or 443 is held by a Docker container.

What to do. Stop that container: ports 80 and 443 are needed by the Nolay proxy.

Port 80 or 443 is held by a web server. Apache and others get the same kind of code: port-apache2, port-httpd.

What to do. Stop and disable that web server, or run the installer with --fix.

Another hosting panel was found. The others get the same kind of code: panel-dokploy, panel-caprover, panel-plesk, panel-cpanel, panel-ispmanager, panel-aapanel, panel-hestiacp.

What to do. Nolay does not install next to another panel. Use a clean server.

No access to api.nolay.ru.

What to do. Allow outgoing connections to port 443. The agent installs but stays offline until access works.