Troubleshooting

Loading or authentication issues

When loading Streetmix, the screen is stuck on the loading spinner indefinitely, or I only see the “We’re having trouble loading Streetmix. (Error RM1)” error message.

If Streetmix is stuck on the initial loading spinner screen, try to open a “private mode” window in your browser. Normally, this mode is used to prevent browsers from saving history, and it also means you can start with a “clean slate” when browsing the web. Here are resources for the two most common browsers.

If Streetmix works in private mode, this means something in your browser cache has become corrupted. You will want to reset your browser back to a “clean slate.”

If Streetmix does not work in private mode, or still does not work after clearing your browser’s cache, please ensure that you are using the latest version of Chrome or Firefox. If you still need help, please contact us.

Error codes

Warning

This section is a work in progress.

These are error codes that may occur while using Streetmix.

Error code Reason Suggested fix
9B Data error: The server sent street data that had no data in it. Load a different street.
RM1 Authentication error: The user attempted to load Streetmix with remembered credentials which have become corrupted. Reset cache and site data for the site.

Development issues

While developing Streetmix, here are solutions to some problems that may arise.

Strategies for resolving most common issues

Check which version of Node.js you are using and make sure it matches the versions listed in package.json.

If you’re still running into problems, try this first!:

  • Update your global node and npm versions to the latest versions.
  • Remove the node_modules and .cache folders, if present, and reinstall (Installing Streetmix).
  • Ensure that you are installing and running Streetmix with npm, not yarn.

Specific issues

This section is for troubleshooting specific issues.

  • The server keeps restarting in a loop with the EADDRINUSE error code. We have documented a solution in GitHub issue #983.