app crashed
Version: 0.13.2,
Platform: Ubuntu 22.04.4 LTS
Error report: [nodemon] app crashed - waiting for file changes before starting...
Modify: open from true to false in the config file vite.config.ts
Log:
7 Replies
Hi @TylerBastian. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
The error message "Port 4040 is already in use" indicates that another process is already running on port 4040, which is causing your application to crash. This is likely the reason why you're seeing the message "[nodemon] app crashed - waiting for file changes before starting...".
You have a few options to resolve this issue:
1. You can find the process that's using port 4040 and stop it. You can do this by running the command
lsof -i :4040 in your terminal. This will list all processes using port 4040. You can then stop the process by running kill <PID>, where <PID> is the process ID.
2. You can change the port that your application is using. This would involve changing your application's configuration or code, depending on how the port is set.
Please note that these instructions are general advice for resolving port conflicts and may need to be adapted depending on your specific application and environment.
As for the modification you made in the vite.config.ts file, it's not clear from the provided logs whether this change is related to the issue. If the problem started after this change, you might want to revert it and see if that resolves the issue.
Lastly, it's worth noting that the error message "nodemon] app crashed - waiting for file changes before starting..." is a standard message from nodemon indicating that it's waiting for changes to restart the application. This is not necessarily an error, but rather nodemon's way of saying that it's ready to restart the application when the files change ([source (https://github.com/wasp-lang/wasp/issues/62)).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @TylerBastian, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?@kapa.ai i reboot the system, now it works. And i can access it via browser. But when i try to sign up, it shows "Network Error".
Let me check the knowledge base for you. One moment! :books:
Wohooo @TylerBastian, you just became a Waspeteer level 1!
----------------------
The "Network Error" you're encountering during the signup process could be due to several reasons. Here are a few potential causes and solutions based on the knowledge sources:
1. Server not running: Ensure that your server is running correctly. If the server is not running, the client-side application won't be able to communicate with it, leading to a network error (source (https://discord.com/channels/686873244791210014/1217758453326680095)).
2. Incorrect Environment Variables: Check your
.env.server and .env.client files. Make sure that the WASP_WEB_CLIENT_URL in .env.server matches your client URL, and the REACT_APP_API_URL in .env.client matches your server URL (source (https://discord.com/channels/686873244791210014/1217758453326680095)).
3. CORS issue: If you're using Gitpod or a similar online IDE, you might encounter CORS issues. Make sure to set the correct URLs in your environment variables to avoid this (source (https://discord.com/channels/686873244791210014/1217758453326680095)).
4. Database Connection: Ensure that your application can connect to the database. A network error can occur if the application can't reach the database server (source (https://github.com/wasp-lang/wasp/issues/460)).
If none of these solutions work, you might want to check the console for any error messages that could provide more information about the issue. If you're still having trouble, consider reaching out to the Wasp community or the Wasp team for more specific assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @TylerBastian, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?@kapa.ai i have update the port for server to port 4040 and the port for client to port 8000 by following the solution 1.1 in this guide https://github.com/wasp-lang/wasp/issues/730, but get Network Error and here is the error report from webbrowser console:
GitHub
Issues · wasp-lang/wasp
The fastest way to develop full-stack web apps with React & Node.js. - Issues · wasp-lang/wasp
Let me check the knowledge base for you. One moment! :books:
----------------------
The error message
GET <http://localhost:4040/auth/me> net::ERR_CONNECTION_REFUSED indicates that your browser is unable to establish a connection to your server running on port 4040. This could be due to several reasons:
1. Server not running: Ensure that your server is running and listening on port 4040. If the server is not running or not correctly configured to listen on port 4040, you will get a connection refused error.
2. Incorrect Environment Variables: Check your .env.server and .env.client files. Make sure that the WASP_WEB_CLIENT_URL in .env.server matches your client URL (http://localhost:8000), and the REACT_APP_API_URL in .env.client matches your server URL (http://localhost:4040) as per the solution 1.1 (https://github.com/wasp-lang/wasp/issues/730).
3. Firewall or Network Issue: If your server is running and the environment variables are correctly set, a firewall or network issue could be blocking the connection. Check your firewall settings to ensure that connections to port 4040 are allowed.
If none of these solutions work, you might want to check the server logs for any error messages that could provide more information about the issue. If you're still having trouble, consider reaching out to the Wasp community or the Wasp team for more specific assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @TylerBastian, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?