Client or core fails to start
Startup failures usually have one of four causes: an occupied port, a broken service mode, a config syntax error, or damaged installation files. Checked in order, most cases are identified within minutes.
Checklist
- Read the Logs page (or open the log directory from the tray menu) — the error message usually names the cause.
- bind: address already in use in the log means a port conflict — follow port conflict troubleshooting.
- If you just edited configs, check YAML indentation and syntax; empty the Merge / Script content and retry.
- If the service mode state looks wrong, uninstall and reinstall the service — see the service mode guide.
- Still stuck? Re-download the latest installer from the official channel and reinstall over the top.
Asking for help effectively
If none of that works, bring the log excerpt, your OS version, and the client version to GitHub Issues — search first; most problems already have answers.