wbjb
WWasp
•Created by wbjb on 1/19/2025 in #🙋questions
email send error
@kapa.ai ahh im still in developemtn. that makes sense. I was trying to test the flow before deploying. Ill check it after. Thnaks
10 replies
WWasp
•Created by wbjb on 1/5/2025 in #🙋questions
Server not listening
@kapa.ai @Filip nevermind im an idiot. I forgot to run the cp env file on the new install. it works now
38 replies
WWasp
•Created by wbjb on 1/5/2025 in #🙋questions
Server not listening
@Filip @kapa.ai [ Server!] Error: Env var STRIPE_API_KEY is undefined
[ Server!] at requireNodeEnvVar (/home/brad/haystack30/app/src/server/utils.ts:4:10)
[ Server!] at <anonymous> (/home/brad/haystack30/app/src/payment/stripe/stripeClient.ts:4:34)
[ Server!] at ModuleJob.run (node:internal/modules/esm/module_job:271:25)
[ Server!] at async onImport.tracePromise.proto (node:internal/modules/esm/loader:547:26)
[ Server!] at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:116:5)
[ Server!]
[ Server!] Node.js v22.12.0
[ Server ] [nodemon] app crashed - waiting for file changes before starting...
[ Client!] (node:6951) ExperimentalWarning: CommonJS module /home/brad/haystack30/app/.wasp/out/web-app/tailwind.config.cjs is loading ES Module /home/brad/haystack30/app/.wasp/out/sdk/wasp/dist/dev/index.js using require().
[ Client!] Support for loading ES Module in require() is an experimental feature and might change at any time
[ Client!] (Use
node --trace-warnings ...
to show where the warning was created)38 replies
WWasp
•Created by wbjb on 1/5/2025 in #🙋questions
Server not listening
@Filip @kapa.ai it started happening again. This time it wont work no matter what i do this is the error i get. This is a fresh open saas file that I cloned after my app failed. 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 ]
[ 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
[ Client ] 🔍 Validating environment variables...
[ 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 v6.0.7 ready in 590 ms
[ Client ]
[ Client ] ➜ Local: http://localhost:3000/
[ Client ] ➜ Network: http://192.168.2.30:3000/
[ Client ] ➜ Network: http://172.17.0.1: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!] /home/brad/haystack30/app/src/server/utils.ts:4
[ Server!] throw new Error(
Env var ${name} is undefined`);
[ Server!] ^
[ Server!]
[ Server!]38 replies
WWasp
•Created by wbjb on 1/5/2025 in #🙋questions
Server not listening
@sodic No idea. My working theory is that something was up with my machine where the ports wouldn't open. I had tried several restarts and a new complete shutdowns and I ran the fuser kill a few times too. In the end, I did another complete shutdown and walked away for a bit and it worked. The worst part of all of this was that I was trouble shooting some problems with API calls and I was pulling my hair out until I realized I wasn't even communicating with the server.
38 replies
WWasp
•Created by wbjb on 1/5/2025 in #🙋questions
Server not listening
@kapa.ai I was able to resolve this. It appears it was my machine. I shut it down completely instead of just restarting and that seems to have reset whatever was going on. I had tried that before. But whatever. Pg boss is now working and it's listening on the correct port
38 replies
WWasp
•Created by wbjb on 1/5/2025 in #🙋questions
Server not listening
@kapa.ai thats not it. It was working perfectly fine before the server stopped responding and no changes were made to that file. COuld it be a problem with my machine?
38 replies
WWasp
•Created by wbjb on 1/5/2025 in #🙋questions
Server not listening
Server ] > [email protected] bundle
[ Server ] > rollup --config --silent
[ Server ]
[ Client ]
[ Client ] VITE v6.0.7 ready in 710 ms
[ Client ]
[ Client ] ➜ Local: http://localhost:3000/
[ Client ] ➜ Network: http://192.168.2.30:3000/
[ Client ] ➜ Network: http://172.17.0.1:3000/
[ Client ] ➜ press h + enter to show help
[ Server ] > [email protected] start
[ Server ] > npm run validate-env && node --enable-source-maps -r dotenv/config bundle/server.js
[ Server ] > [email protected] validate-env
[ Server ] > node -r dotenv/config ./scripts/validate-env.mjs
[ Server ] 🔍 Validating environment variables...
[ Server!] /home/brad/haystack22/app/src/server/utils.ts:4
[ Server!] throw new Error(
Env var ${name} is undefined
);
[ Server!] Error: Env var STRIPE_API_KEY is undefined
[ Server!] at requireNodeEnvVar (/home/brad/haystack22/app/src/server/utils.ts:4:11)
[ Server!] at <anonymous> (/home/brad/haystack22/app/src/payment/stripe/stripeClient.ts:4:34)
[ Server!] at ModuleJob.run (node:internal/modules/esm/module_job:271:25)
[ Server!] at async onImport.tracePromise.proto (node:internal/modules/esm/loader:547:26)
[ Server!] at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:116:5)
[ Server!]
[ Server!] Node.js v22.12.0
[ Server ] [nodemon] app crashed - waiting for file changes before starting...
@kapa.ai @Wasp Team38 replies
WWasp
•Created by wbjb on 1/5/2025 in #🙋questions
Server not listening
[ Server ] > [email protected] watch
[ Server ] > nodemon --exec 'npm run bundle-and-start exit 1'
[ Server ]
[ Client ] > [email protected] start
[ Client ] > npm run validate-env && vite
[ Client ]
[ 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`
[ Client ]
[ Client ] > [email protected] validate-env
[ Client ] > node -r dotenv/config ./scripts/validate-env.mjs
[ Client ]
[ Client ] 🔍 Validating environment variables...
[ Server ]
[ Server ] > [email protected] bundle-and-start
[ Server ] > npm run bundle && npm run start
[ Server ]
[ Server ]38 replies
WWasp
•Created by wbjb on 1/5/2025 in #🙋questions
Suddenly no Apps including new files can access server
@kapa.ai this is a local version. That's the issue it won't load the demo app
11 replies
WWasp
•Created by wbjb on 12/31/2024 in #🙋questions
Failed to load resource: net::ERR_CONNECTION_REFUSEDUnderstand this errorAI:3001/auth/me:1
Hey! Thanks for offering. I've got everything figured out from the docs and the help from kapa. I'll tag you the next time though!
23 replies
WWasp
•Created by wbjb on 12/31/2024 in #🙋questions
Failed to load resource: net::ERR_CONNECTION_REFUSEDUnderstand this errorAI:3001/auth/me:1
@kapa.ai can you please elaborate on this answer you geve me. which file does this go in ----------------------
This error message indicates that you're encountering a CORS (Cross-Origin Resource Sharing) issue in your Wasp application. Let's address this based on the information provided in the knowledge sources:
1. CORS Configuration in Wasp:
Wasp includes CORS middleware by default, as mentioned in the Middleware Configuration documentation (https://wasp-lang.dev/docs/advanced/middleware-config). However, sometimes additional configuration might be needed for specific endpoints.
2. API Namespace and CORS:
For custom API endpoints, you might need to use the
apiNamespace
feature to ensure CORS is properly configured. As explained in the Custom HTTP API Endpoints documentation (https://wasp-lang.dev/docs/advanced/apis#making-sure-cors-works), you can define an apiNamespace
in your main.wasp
file:
Then, in your implementation file:
This should enable CORS for all APIs under the "/api" path, including your "/api/analyzeFunnel" endpoint.
3. Global Middleware Customization:
If you want to modify CORS settings globally, you can customize the global middleware as shown in the Configuring Middleware documentation (https://wasp-lang.dev/docs/advanced/middleware-config#1-customize-global-middleware):
23 replies
WWasp
•Created by wbjb on 12/31/2024 in #🙋questions
Failed to load resource: net::ERR_CONNECTION_REFUSEDUnderstand this errorAI:3001/auth/me:1
Access to fetch at 'http://localhost:3001/api/analyzeFunnel' from origin 'http://localhost:3000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled @kapa.ai
23 replies
WWasp
•Created by wbjb on 12/31/2024 in #🙋questions
Failed to load resource: net::ERR_CONNECTION_REFUSEDUnderstand this errorAI:3001/auth/me:1
@kapa.ai what is the correct api url in the opensaas template
23 replies
WWasp
•Created by wbjb on 12/28/2024 in #🙋questions
demo app wont load
@Filip not really. The app wouldn't load because after I changed. The port it kept looking for auth at 3001. In the end i just decided to start with a fresh clone and everything is fine now. I'm not sure what the issue was. It was probably on my end though. Everything was working great when I was running a Linux VM but I switched to a dedicated linux machine and after that it wasn't working. I think there was probably something up with my machine. Either way I'm back up and running now so no big deal
24 replies
WWasp
•Created by wbjb on 12/28/2024 in #🙋questions
demo app wont load
@kapa.ai what you have at step 2 is probabaly the issue but I'm using the open saas template and it doesnt seem to have a .env.client
24 replies
WWasp
•Created by wbjb on 12/28/2024 in #🙋questions
demo app wont load
@kapa.ai this worked but now i'm getting an error in console in the app and I cant load any of the demo app fucntions here is the error ypeError: Cannot read properties of undefined (reading 'length')
at onAccept (Config.ts:62:38)
at oe (vanilla-cookieconsent.js?v=14504875:168:57)
at Module.Xe (vanilla-cookieconsent.js?v=14504875:704:137)
onAccept @ Config.ts:78Understand this errorAI
:3001/auth/me:1
Failed to load resource: net::ERR_CONNECTION_REFUSEDUnderstand this errorAI :3001/auth/me:1
Failed to load resource: net::ERR_CONNECTION_REFUSEDUnderstand this errorAI :3001/auth/me:1
Failed to load resource: net::ERR_CONNECTION_REFUSEDUnderstand this errorAI @tanstack_react-query.js?v=14504875:947 AxiosError onError @ @tanstack_react-query.js?v=14504875:947Understand this errorAI :3001/auth/me:1
Failed to load resource: net::ERR_CONNECTION_REFUSEDUnderstand this errorAI
Failed to load resource: net::ERR_CONNECTION_REFUSEDUnderstand this errorAI :3001/auth/me:1
Failed to load resource: net::ERR_CONNECTION_REFUSEDUnderstand this errorAI :3001/auth/me:1
Failed to load resource: net::ERR_CONNECTION_REFUSEDUnderstand this errorAI @tanstack_react-query.js?v=14504875:947 AxiosError onError @ @tanstack_react-query.js?v=14504875:947Understand this errorAI :3001/auth/me:1
Failed to load resource: net::ERR_CONNECTION_REFUSEDUnderstand this errorAI
24 replies
WWasp
•Created by wbjb on 12/28/2024 in #🙋questions
demo app wont load
@kapa.ai [ Server!] Port 3001 is already in use
24 replies
WWasp
•Created by wbjb on 12/27/2024 in #🙋questions
sdk build failed
@kapa.ai and after all of that it works. Thanks!
46 replies
WWasp
•Created by wbjb on 12/27/2024 in #🙋questions
sdk build failed
🐝 --- Compiling wasp project... --------------------------------------------------
❌ --- [Error] Your wasp project failed to compile: -------------------------------
- Error: Dependency conflict for user dependency (@tsconfig/node18, ^18.2.4): Version must be set to the exactly the same version as the one wasp is using: latest
❌ --- [Error] Compilation of wasp project failed: --------------------------------
1 errors found
brad@brad-UX461UA:~/haystack9/app$ node -v
v18.20.5
@kapa.ai now im getting this
46 replies