Get GrandNode

Where to start when something is wrong

Most problems have one of a handful of causes. Before you dig deeper, go through this routine - it solves or narrows down the majority of cases.

The routine

  1. Read the System information warnings. System → System information checks the store URL, primary currencies, weight and dimension, and payment methods. Fix anything that is not green.
  2. Read the log. GrandNode logs through .NET logging - the console, docker logs, the IIS stdout log or Application Insights, depending on hosting. An exception message names the cause far more often than the symptom suggests. See Maintenance tools and logs.
  3. Clear the cache. Gear menu → Clear memory cache, especially after changing data outside the admin.
  4. Check the store scope. On a multi-store installation, a setting saved for one store overrides the shared value for the whole settings group. Look at the setting with that store selected.
  5. Restart (gear menu → Restart application) after installing plugins, editing appsettings.json or changing scheduled tasks.
  6. Reproduce in a private window, to rule out the browser cache and your own customer session.
System information with version, environment, server time, paths and the Warnings list
System → System information: the warnings at the bottom are the first thing to check.

Reporting a problem

When you ask for help - in GitHub Discussions or from your support provider - include:

  • the GrandNode version and git commit from System information, and the hosting (Docker, IIS, Linux);
  • exact steps to reproduce and what you expected;
  • the full error from the log, not a screenshot of the error page;
  • which plugins and theme are active.

Question not answered here? Ask the community on GitHub Discussions ↗