Wasp•4mo ago

signup Network Error

I'm trying to sign-up locally with the Dummy Provider. After entering an email and password, the page says Network Error in red. The terminal logs don't show anything. The browser console logs show login.ts:7 POST http://localhost:3001/auth/email/login net::ERR_CONNECTION_REFUSED. Did I miss a step in the docs? I'm using WSL and on Wasp version 0.16.4

6 Replies

kapa.ai•4mo ago

Hi @kingmaker. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- Based on your description and the knowledge sources, the error message net::ERR_CONNECTION_REFUSED when trying to POST to <http://localhost:3001/auth/email/login> suggests that your Wasp backend server is not running or is not accessible at that address. Here are some steps and checks based on similar issues and community advice: 1. Ensure the Wasp server is running
Make sure you have started your Wasp app with wasp start and that there are no errors in the terminal. The backend should be listening on port 3001 by default. If the server is not running, the frontend will not be able to reach it, resulting in a connection refused error. 2. Check for port conflicts
Confirm that nothing else is running on port 3001, and that your WSL environment allows connections to that port. Sometimes, WSL networking can be tricky, especially if you are accessing from Windows to WSL or vice versa. If you are running both frontend and backend in WSL, this should generally work, but double-check your setup. 3. Verify environment variables
If you are running in a cloud IDE or a non-localhost environment (like Gitpod), you need to set the correct environment variables (WASP_WEB_CLIENT_URL in .env.server and REACT_APP_API_URL in .env.client) to point to the correct URLs. For local development, these should default to localhost, but if you have changed them, make sure they are correct. This is a common source of issues in cloud environments, but less so for local WSL unless you have customized your setup.
See related discussion 4. Dummy Provider setup
For local development with the Dummy Provider, your main.wasp should include:

   app myApp {
     // ...
     emailSender: {
       provider: Dummy,
     }
   }

   app myApp {
     // ...
     emailSender: {
       provider: Dummy,
     }
   }

This only affects email sending, not the server connection itself, but make sure this is set up as per the docs if you are using email auth.
See docs 5. No terminal logs
If the terminal shows nothing when you attempt to sign up, it strongly suggests the backend is not running or not receiving the request at all. 6. WSL-specific issues
There can be networking issues with WSL, especially if you are trying to access the server from Windows rather than within WSL. Make sure you are accessing localhost:3001 from within the same WSL environment where the server is running.
See related advice Summary:
The most likely cause is that your Wasp backend server is not running or not accessible at localhost:3001. Double-check that wasp start is running successfully and that you are accessing the app from the correct environment. If you continue to have issues, try restarting WSL and your app, and ensure no other process is using port 3001. If you have checked all of the above and the issue persists, please provide more details about your setup and any additional error messages you see. Let me know if you need more help! ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @kingmaker, 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?

kingmakerOP•4mo ago

turns out I had .env instead of .env.server so the backend had crashed. this was pretty obvious from the terminal logs. I was still able to navigate around the app though, which is why I had overlooked this. signing up works now

Rangeki•4mo ago

how your signup works? i just fresh install opensaas and in env i just have, default .env.server

Rangeki•4mo ago

did i need to make changes on it ? @kapa.ai i just deploy wasp opensaas in local, got network error in sign up

kapa.ai•4mo ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- If you deployed Wasp OpenSaaS locally and are getting a "Network Error" when trying to sign up, this is a common issue that has been discussed in the community. Here are the most relevant troubleshooting steps based on the knowledge sources: 1. Check if the backend server is running
The error Network Error often means the frontend cannot reach the backend server. Make sure you have started your Wasp app with wasp start and that there are no errors in the terminal. If the backend is not running, the frontend will not be able to communicate with it, resulting in this error. Also, check that nothing else is using port 3001, which is the default for the Wasp server. 2. Environment variables
For local development, ensure your environment variables are set correctly. In particular, check that: - .env.server contains WASP_WEB_CLIENT_URL=<http://localhost:3000> - .env.client contains REACT_APP_API_URL=<http://localhost:3001> These should match your local setup. If you are running in a cloud IDE or a different environment, you may need to adjust these URLs accordingly.
See discussion for Gitpod and env vars 3. No terminal logs
If you see no logs in the terminal when you attempt to sign up, it suggests the backend is not receiving the request. Double-check that the server is running and accessible. 4. CORS issues
If you are running frontend and backend on different hosts or ports, make sure CORS is not blocking your requests. For local development with default settings, this should not be an issue, but if you have customized your setup, review your CORS configuration. 5. Database connectivity
If you are using an external database, ensure it is running and accessible. Problems with the database can sometimes manifest as network errors on the frontend if the backend fails to start or crashes on requests.
See related issues with DB connectivity 6. OpenSaaS template specifics
Some users have reported that OpenSaaS may require additional setup for environment variables, especially if running in environments like Gitpod. For local development, the default values should work, but double-check your .env files if you have made changes. If you have checked all of the above and the issue persists, please provide more details about your setup, any error messages in the browser console, and any output from your terminal. Let me know if you need more help! ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @Rangeki, 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?

toticozeni•4mo ago

Hey @Rangeki, the env example files should hole explanation for each key-value pair. Do you have problems with something?

Gaming

Programming

signup Network Error

Did you find this page helpful?