Troubleshooting
Most problems fall into a handful of buckets. Start with the preflight check, then work down this list.
Start with doctor
On the greffer host, the preflight check catches the common environment problems (Docker missing or not running, the Docker Compose plugin missing, no connectivity to the Manager):
greffer doctorWhen a greffer won’t register
If a freshly installed greffer never appears in the dashboard, it usually can’t reach the Manager, or the greffer ID is wrong. Check that the machine has outbound network to your Manager URL, and that the ID you passed to greffer up --id matches the one you created in the dashboard.
The worker runs your greffons as containers. If Docker Engine (or Docker Desktop) isn’t running, registration and deploys will fail — greffer doctor flags this.
Stuck on “pending”
A greffer that registered but stays pending is waiting for you. Open the dashboard and accept it — that’s when the certificate is issued and it comes online.
Greffon won’t start
If an instance reports stopped or unknown right after you start it, the app’s containers failed to come up. Common causes: a bad configuration value, an image that can’t be pulled, or a port conflict on the host. Re-check the greffon’s configuration, and confirm the greffer can pull images.
Bring the details — greffer OS, what greffer doctor and greffer status report, and which greffon — to the community on GitHub.