client not working when visit port 3000
Hello all! Just learning NextJS, coming from Astro. Decided to give this stack a shot based on research and all the features. I got Docker running on a Ubuntu VPS. After running “wasp start” everything starts fine. When I visit my IP:3000, it’s just a blank page that does not load and I get connection timed out. Any ideas?
9 Replies
Hi @Jonah. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the information provided, there could be a few reasons why you're experiencing this issue. Here are some steps you can take to troubleshoot:
1. Check the Ports: Wasp uses port 3000 for the frontend and port 3001 for the backend. Make sure these ports are not being used by other services. If they are, you'll need to terminate those services and restart your app. If the ports are already taken,
wasp start will fail. You can check this by running fuser -k 3000/tcp and fuser -k 3001/tcp in your terminal (source (https://github.com/wasp-lang/wasp/issues/198)).
2. Check for Errors: Look for any error messages in your terminal where you ran wasp start. Also, open your browser's developer tools console and check for any errors there. These could provide clues about what's going wrong (source (https://discord.com/channels/686873244791210014/1213958217537814640)).
3. Try Cleaning and Restarting: Try quitting the main wasp process with ctrl+c, then run wasp clean and then when it's finished run wasp start again (source (https://discord.com/channels/686873244791210014/1213958217537814640)).
4. Check Your Network: If you're running this on a VPS, ensure that your VPS provider isn't blocking the ports you're trying to use. You might need to configure your firewall settings to allow traffic through these ports.
5. Check Your Code: If you generated an app using Mage, there might be some mistakes in the generated code. You can share the generated app with the Wasp team for them to take a look at the generated code (source (https://discord.com/channels/686873244791210014/1213958217537814640)).
If none of these steps resolve the issue, it would be helpful to have more information about your setup and any error messages you're seeing.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Jonah, 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?Do you see any errors in the browser console? Do you see any errors in the server logs?
No errors in browner console or my docker console! I’ll have to check again later tonight when I get home!
Okay so for my console when I start wasp all I get is a error for invalid stripe creds because I haven’t edited the env yet
No errors in browser console tho
Silly question, did you follow the step of cp .env.server.example .env.server? It sounds like what happened to me when I didn't actually have a .env.server file. the sample project setup starts without stripe being set up.
I do indeed have the .env.server! I do not have a .env.client tho
Wohooo @Jonah, you just became a Waspeteer level 1!
Well, .env.server is where your stripe key goes so that's what it's complaining about, I think. At any rate I'm a complete hack and that was my only idea. Good luck!
Let me add dev test keys to the stripe in the env and see if it works
I had a problem and it is that I did not have
env.client created, (it was just with the Stripe customer portal).
I say this because at that time the client was working fine without having .env.client.
Ps: In one of my Chrome profiles I have an extension that basically when I enter a site “accepts” cookies (I don't care about cookies), and this often causes the cookie banner to be buggy and the page goes blank (it has happened to me with some other website and the OpenSaas template).
Ps2: I did the Stripe integration at the end so I was working with the .env files without the Stripe keys and it worked (I think I would rule out the option of missing environment variables).Chrome Web Store
Add new features to your browser and personalize your browsing experience.