Troubleshooting · Beta
Troubleshoot a project recipe
A practical checklist for Abotlogixfile.json, supported tools, service commands, SQL initialization, and named Cloudflare tunnels.
Recipe file
| Check | What to do |
|---|---|
| Incorrect filename capitalization | Use exactly Abotlogixfile.json. |
| File is not in the project root | Move the recipe into the selected project's root folder. |
| Invalid JSON | Check commas, brackets, quotation marks, and array structure. |
| Unsupported field name | Use only the current parser's public snake_case fields. |
| CamelCase field | Use project_name, app_url, setup_commands, delay_after_start_ms, init_scripts, and optional tool_id—not Kotlin-only camelCase names. |
Commands and services
| Symptom | Check |
|---|---|
| Command is stored as one string | Use one array item for the executable and one item for every argument. |
| Missing executable | Confirm the first command item identifies a supported executable and install it through Global Tools Manager or the terminal workflow. |
| Unsupported tool name | Confirm the executable name is a supported catalog item, or use the optional advanced tool_id override only when required. |
| Setup command fails | Run and inspect the tested command manually, then correct its array, path, or prerequisites. Do not assume every failure automatically stops later work. |
| Service exits immediately | Test the executable and arguments in VPServ, then compare them with the recipe command array. |
Paths, ports, and SQL
| Symptom | Check |
|---|---|
| Incorrect path | Use {home} or an exact '.' argument for the selected project folder; use {usr} where the runtime's internal usr path is needed. |
| Application port mismatch | Make the service command and optional app_url agree with the URL you expect to open. |
| SQL file not found | Keep the referenced .sql file in the project root and use its project-root-relative filename in init_scripts. |
| SQL did not initialize as expected | Use the MariaDB initialization path; init_scripts does not provide a generic script runner. |
Named Cloudflare tunnel
| Symptom | Check |
|---|---|
| Tunnel token is invalid or expired | Use a current named tunnel token and rotate it if it may have been exposed. |
| Tunnel domain is misconfigured | Confirm the enabled named tunnel has the intended configured domain and token. VPServ does not automatically configure DNS for you. |
| A local project does not need public access | Omit tunnel entirely rather than adding empty tunnel values. |
The project works manually but not through Run Environment
- 01
Verify Abotlogixfile.json is in the selected project root and uses current snake_case keys.
- 02
Compare the manually tested executable and arguments with every service command array.
- 03
Move one-time work into optional setup_commands and long-running processes into services.
- 04
Confirm a setup-only tool is already available if no service executable identifies it.
- 05
Check {home}, {usr}, {bin}, and '.' usage against the supported placeholder locations.
- 06
Review available output and logs, then retest the prepared project from a clean VPServ installation when possible.