Collection

Troubleshooting

Work from a symptom to a focused check and a verified fix.

Choose the task that matches what you need to do. The pages explain the relevant workflow and link to related guides and reference material. Examples use the local site garden; use your own site name and check the command’s scope before running it.

In this section

  1. 1A site does not startRun bin/zotonic status to distinguish an unavailable node from a stopped or failing site. Inspect the relevant startup log before repeatedly restarting it.
  2. 2A module is missing from the adminCheck that the module is an Erlang application in a discovered project directory. Confirm the application name, .app.src, main mod_... module, and successful compilation.
  3. 3A module is discovered but not activeOpen module management for the correct site. Check whether the module is disabled, waiting for a dependency, or failing during startup.
  4. 4A saved change does not appearCheck each stage in order: the edited file, build output, loaded application, active module, selected template, and browser response.
  5. 5A URL reaches the wrong pageConfirm the hostname, site, and path from the actual request. Use the dispatch trace to see the selected rule and any rewritten path.
  6. 6A model returns an error or no valueCheck the requested path and compare its binary segments with the model callback patterns. Confirm that the callback returns the unused path in the required result structure.
  7. 7An uploaded image does not displayCheck whether the resource has an original file and whether its media information describes that file correctly. Then inspect the preview request in the browser network panel.
  8. 8A page is slowMeasure one representative request and identify whether time is spent in the browser, network, or server. Compare an initial request with a repeated request to see the effect of caches.