[RESOLVED] http://localhost:3000/ is just blank page? Everything on installed seemed fine?
I installed and followed the openSaaS installation guide carefully, I'm on an M2 Mac, when I run "wasp start" in my app directory, it just navigates me to a blank page. I think I did everything right? The example blog seems to be working.. Any help much appreciated lol.
11 Replies
Hi @Treeleafbark. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry to hear that you're having trouble with your Wasp app. There could be a few reasons why you're seeing a blank page at
<http://localhost:3000/.> Here are a few things you can try:
1. Check the terminal for errors: When you run wasp start, make sure to check the terminal for any error messages. If there are any, they might give you a clue as to what's going wrong.
2. Check the browser console for errors: Open the developer tools in your browser (usually by pressing F12 or right-clicking on the page and selecting "Inspect") and check the console for any error messages.
3. Try running wasp clean and then wasp start again: Sometimes, there can be issues with the build process that can be resolved by cleaning the build directory and starting again. You can do this by running wasp clean in your terminal, and then running wasp start again.
4. Check your code for errors: Make sure that all of your code is correct and that there are no syntax errors or missing imports. If you're using an IDE like VS Code, it should highlight any syntax errors for you.
5. Check if the backend server is running: The backend server runs on port 3001. Make sure that this port is not being used by another service. If it is, terminate that service and try running wasp start again.
If none of these steps help, it would be helpful if you could provide more information about your setup and any error messages you're seeing. This will make it easier to diagnose the problem.
For more detailed instructions on how to get started with Wasp, you can check out the Quick Start guide (https://wasp-lang.dev/docs/quick-start#installation) in the Wasp documentation.
If you're still having trouble, don't hesitate to ask for help on the Wasp Discord server (https://discord.com/channels/686873244791210014/1213958217537814640). The community there is very helpful and might be able to provide more specific advice based on your situation.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Treeleafbark, 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?Here is my npm install
[ Wasp ] Starting npm install
[ Wasp !] npm warn deprecated [email protected]: Use your platform's native atob() and btoa() methods instead
[ Wasp !] npm warn deprecated [email protected]: Use your platform's native DOMException instead
[ Wasp ]
[ Wasp ] added 792 packages, and audited 794 packages in 4s
[ Wasp ]
[ Wasp ] 139 packages are looking for funding
[ Wasp ] run
npm fund for details
[ Wasp ]
[ Wasp ] 1 moderate severity vulnerability
[ Wasp ]
[ Wasp ] To address all issues, run:
[ Wasp ] npm audit fix --force
[ Wasp ]
[ Wasp ] Run npm audit for details.
[ Client ] Starting npm install
[ Server ] Starting npm install
[ Client ]
[ Client ] added 109 packages, and audited 110 packages in 4s
[ Client ]
[ Client ] 14 packages are looking for funding
[ Client ] run npm fund for details
[ Client ]
[ Client ] found 0 vulnerabilities
[ Server ] Still installing npm dependencies!
[ Server!] npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
[ Server!] npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/config-array instead
[ Server!] npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
[ Server!] npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
[ Server!] npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/object-schema instead
[ Server ]
[ Server ] added 365 packages, and audited 366 packages in 7s
[ Server ]
[ Server ] 120 packages are looking for funding
[ Server ] run npm fund for details
[ Server ]
[ Server ] 4 vulnerabilities (1 moderate, 3 high)
[ Server ]
[ Server ] To address all issues (including breaking changes), run:
[ Server ] npm audit fix --force
[ Server ]
[ Server ] Run npm audit for details.
-----------------
here is my server startup
------------
[ Client ] > [email protected] start
[ Client ] > npm run validate-env && vite
[ Client ]
[ Server ] > [email protected] watch
[ Server ] > nodemon --exec 'npm run bundle-and-start exit 1'
[ Server ]
[ Client ]
[ Client ] > [email protected] validate-env
[ Client ] > node -r dotenv/config ./scripts/validate-env.mjs
[ Client ]
[ Client ] 🔍 Validating environment variables...
[ Server ] [nodemon] 2.0.22
[ Server ] [nodemon] to restart at any time, enter rs
[ Server ] [nodemon] watching path(s): src//* ../../../src//* .env
[ Server ] [nodemon] watching extensions: ts,mts,js,mjs,json
[ Server ] [nodemon] starting `npm run bundle-and-start exit 1
[ Server ]
[ Server ] > [email protected] bundle-and-start
[ Server ] > npm run bundle && npm run start
[ Server ]
[ Server ]
[ Server ] > [email protected] bundle
[ Server ] > rollup --config --silent
[ Server ]
[ Client ]
[ Client ] VITE v5.4.2 ready in 524 ms
[ Client ]
[ Client ] ➜ Local: http://localhost:3000/
[ Client ] ➜ Network: http://192.168.1.253:3000/
[ Client ] ➜ press h + enter to show help
[ Server ]
[ Server ] > [email protected] start
[ Server ] > npm run validate-env && node --enable-source-maps -r dotenv/config bundle/server.js
[ Server ]
[ Server ]
[ Server ] > [email protected] validate-env
[ Server ] > node -r dotenv/config ./scripts/validate-env.mjs
[ Server ]
[ Server ] 🔍 Validating environment variables...
[ Server ] 🚀 "Email and password" auth initialized
[ Server ] Starting pg-boss...
[ Server!] (node:38553) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
[ Server!] (Use node --trace-deprecation ...` to show where the warning was created)
[ Server ] pg-boss started!
[ Server ] Server listening on port 3001
----
not really sure whats going on, no real errors as far as I can tell? but the page is totally blank lolHey @Treeleafbark, What does the devtools console say?
Hi Sodic, sorry for the delay in replying. I reinstall macOS to make sure it wasn't a problem with my development computers operating system
I'm currently searching the documentation for how to access the devtools console
Wohooo @Treeleafbark, you just became a Waspeteer level 1!
There we are..
Interesting
It appears to have been ublockorigin
totally blocked it
I disabled it, and it appears to be working now
Thank you for your suggestion and it helping me troubleshoot this
No problem, glad I could help! Remember to check the devtools console in the future. When I see a blank screen, that's always my first step!
thanks, did you find a way to fix this?
This happens for any crash happening on the client @iRazvan2745, you have to open the dev tools in your browser and look at the console log. If you don't understand the error, feed everything + context into a LLM. The bot here can help, it knows the documentation better than the frontier models.
Wohooo @Conspyre, you just became a Waspeteer level 4!