Skip to content

Troubleshooting & Common Issues

If your updates aren’t appearing on the live site:

  1. Go to your repository’s Actions tab.
  2. Check for a yellow circle (in progress) or red cross (failed).
  3. Click a failed run to see the error log.

Common Cause: Invalid YAML. Paste your config into a YAML Validator to check for syntax errors.

Cause: Hugo’s module cache is corrupted.

  1. Clear Cache (Recommended) Run this command to clear the module cache:

    Terminal window
    hugo mod clean --all
  2. Manual Delete (If above fails) Delete the hugo_cache folder manually.

    • Mac/Linux: $TMPDIR/hugo_cache/
    • Windows: %TMP%\hugo_cache\

Cause: Missing Module Output

If you disabled a module (like Netlify) but left its outputs in hugo.yaml (e.g., headers, redirects), Hugo will fail. Remove the unused outputs from your configuration.

This usually means Hugo can’t download or find the required modules.

Terminal window
# Try clearing cache and updating modules
hugo mod clean
hugo mod get -u ./...
hugo server

HugoBlox requires Hugo Extended, which depends on Go.

  1. Ensure Go is installed.
  2. Ensure you are using Hugo Extended version.

You are likely using the standard version of Hugo. You must install Hugo Extended. View Installation Guide

You have a syntax error in a Front Matter or Config file. The error message usually provides a line number.

  • Check indentation (YAML is strict about spaces).
  • Ensure strings with special characters are quoted.

Hugo requires a valid date format.

  • Correct: date: 2023-12-25
  • Incorrect: date: 12/25/2023

Hugo is multi-threaded, which can sometimes cause race conditions on complex sites. Try running in single-worker mode:

Terminal window
HUGO_NUMWORKERMULTIPLIER=1 hugo server
  • Check your internet connection.
  • If you are in China, configure a Go Proxy.