How to Get Unstuck and Fix Common Issues

I know the feeling of hitting a wall when you are right in the middle of a project. One minute everything is running fine, and the next, an error message blocks your progress. I have spent too much time chasing down configuration bugs that should have been simple fixes. When things break, you want a clear path to get back to coding without wasting your afternoon.

What You’ll Need

Before you start digging into the logs, make sure you have these basics covered:

• Node.js and npm installed.
• Your PATH environment variables correctly configured.

Quick Start

If you need to fix your environment quickly, follow these two steps to find the root cause:

1. Check your environment: Run a sanity check on your Node and npm installation to make sure your PATH is set up correctly.
2. Run Repairs: Use the doctor tool to automatically find and fix issues with your gateway.

Troubleshooting

Here are the most common areas to check when something goes wrong:

• Installation Sanity: If the tools won’t start, verify your Node, npm, and PATH settings. Most issues stem from the environment not recognizing the installed packages.
• Gateway Issues: If you encounter gateway-specific errors, refer to the gateway troubleshooting guide or use the repair tool.
• Logging: Check the general logs and gateway logs. These files contain the specific error details you need to identify what actually broke.
• Conceptual Questions: If nothing is broken but you are confused about how a feature works, check the FAQ for conceptual explanations.

If you need more help, try the AI Setup Assistant.

What’s Next

• FAQ (concepts)
• Logging