hi getting a [ Server ] POST /operations/stripe-payment 500 44.007 ms .
How to run wasp with more debug messages, also analyzing errors ?. like adding debug.log etc
MWhat do you see in the terminal? 
Rwell nothing much
MWohooo @ramkumar9226, you just became a Waspeteer level 1!
Rthat is why i wanted to see if there is a way to debug this
Myou should be getting full error messages, everything that comes from React & Node is forwarded!
M500 tells us something is off 
for this you should get some logs
for this you should get some logs
Nsame here. im getting a tax error issue which is werid i have this stripe acct working on other apps and never seen this
N"message": "Stripe Tax has not been activated on your account. Please visit https://stripe.com/docs/tax/set-up to get started."
M@Vinny (@Wasp) please take a look at this one 
Vdo you have the stripe webhook forward to port 3001? >> https://docs.opensaas.sh/guides/stripe-testing/
OpenSaaS.sh
Open SaaS is a free, open-source, full-stack SaaS starter kit for React + NodeJS.
Vmaybe check your API version numbers. what version/date are you running in your other apps?
VAnother user had the same issue and they were able to fix it by going to their tax dashboard:
"...i fixed the tax stuff on stripe dashboard: https://dashboard.stripe.com/tax/setup"
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Nno i was able to fix it. u have the stripe tax flag in code set to true. u should set it to false cause not all accts have it enabled and it prevents the stripe integraton from working
N@Vinny (@Wasp) can u tell me how we can connect this to a flask backend ? and how can we build on top of the existing app ? its nice to get the initial login/stripe/HP but what if we want to add custom pages that fetch some data from a flask app or a python websocet ? how do we build on top of this app ?
Vjust call those endpoints in your frontend code
Vset it to false cause not all accts have it enabled and it prevents the stripe integraton from workingcool thanks for the tip
Ncan u elaborate more pls ?to add new /custom pages we should just create react components in client dir ?
Vto create new pages and client routes check out these docs here > https://wasp-lang.dev/docs/tutorial/pages
In the default main.wasp file created by wasp new, there is a page and a route declaration:
Nwill do tnx !
also @Vinny (@Wasp) sry for bombaring u with multiple Q's haha but the admin panel doesnt work for some reason. we get this :
also @Vinny (@Wasp) sry for bombaring u with multiple Q's haha but the admin panel doesnt work for some reason. we get this :
MWohooo @noamico, you just became a Waspeteer level 1!
Nevent though we have 5 registred users, and stripe revenue
Vthe cron job runs every hour so maybe that;s why
Nthis has been up fpr 24 hrs already
Nwhy does it need cron to do this ? cant it just query stripe/PG when needed ?
Vyou can move it to a
queryhow do i debug this to make it work
Nhow do i make sure the cron is running ?
Ncause the Daily stats tbl is empty
VI would change the cron schedule in the main.wasp to run every minute and check that it’s pulling stats and saving to your db.
VIt starts automatically when you run wasp start
Ntbl is empty
Nso something not working there ...
Nok i think i know the issue
Nu guys should rly go over the defualy settings u have set for the project. my hunch is if we dont have plausible analystics set the script fails
Vyes this is could be why
Vyou need to use either plausible or google
Vhttps://github.com/wasp-lang/open-saas/blob/main/app/src/server/workers/calculateDailyStats.ts#L3-L4
GitHub
A free, open-source SaaS app starter for React & Node.js with superpowers. Production-ready. Community-driven. - wasp-lang/open-saas
Vcheck your Logs, too. If the calculateDailyStats job fails, it will save a log to the DB
Ni added plausible
MWohooo @noamico, you just became a Waspeteer level 2!
Nbut not working
Vdid you look at the Logs in your DB?
Vfirst try that. next would be debugging the function
Vto do that, I would change the job to run every minute in the main.wasp file
MOr, call them from the server code! Whatever makes more sense.
VYes, that's true! Btw, let me know how things go once you've done some more debugging @noamico -- I'm keen to get your problem resolved, so let me know what happens or if you get stuck / have any more questions
N[ Server ] POST /operations/get-daily-stats 500 5.622 ms - 724
[ Server!] NotFoundError: No DailyStats found
[ Server!] at /Users/noamico/dev/wasp-demo/app/node_modules/@prisma/client/runtime/library.js:162:12389
[ Server!] at async /Users/noamico/dev/wasp-demo/app/node_modules/@prisma/client/runtime/library.js:162:12328
[ Server!] at getDailyStats$2 (/Users/noamico/dev/wasp-demo/app/src/server/queries.ts:78:22)
[ Server!] at <anonymous> (/Users/noamico/dev/wasp-demo/app/.wasp/out/server/src/middleware/operations.ts:13:24)
[ Server!] at <anonymous> (/Users/noamico/dev/wasp-demo/app/.wasp/out/sdk/wasp/server/utils.ts:31:5)
[ Server!] Error calculating daily stats: Error: HTTP error! Status: 404
[ Server!] at getTotalPageViews (/Users/noamico/dev/wasp-demo/app/src/server/workers/plausibleAnalyticsUtils.ts:46:11)
[ Server!] at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[ Server!] at getDailyPageViews (/Users/noamico/dev/wasp-demo/app/src/server/workers/plausibleAnalyticsUtils.ts:28:22)
[ Server!] at calculateDailyStats (/Users/noamico/dev/wasp-demo/app/src/server/workers/calculateDailyStats.ts:44:55)
[ Server!] at async resolveWithinSeconds (/Users/noamico/dev/wasp-demo/app/node_modules/pg-boss/src/manager.js:34:14)
[ Server!] at async /Users/noamico/dev/wasp-demo/app/node_modules/p-map/index.js:57:22
[ Server!] NotFoundError: No DailyStats found
[ Server!] at /Users/noamico/dev/wasp-demo/app/node_modules/@prisma/client/runtime/library.js:162:12389
[ Server!] at async /Users/noamico/dev/wasp-demo/app/node_modules/@prisma/client/runtime/library.js:162:12328
[ Server!] at getDailyStats$2 (/Users/noamico/dev/wasp-demo/app/src/server/queries.ts:78:22)
[ Server!] at <anonymous> (/Users/noamico/dev/wasp-demo/app/.wasp/out/server/src/middleware/operations.ts:13:24)
[ Server!] at <anonymous> (/Users/noamico/dev/wasp-demo/app/.wasp/out/sdk/wasp/server/utils.ts:31:5)
[ Server!] Error calculating daily stats: Error: HTTP error! Status: 404
[ Server!] at getTotalPageViews (/Users/noamico/dev/wasp-demo/app/src/server/workers/plausibleAnalyticsUtils.ts:46:11)
[ Server!] at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[ Server!] at getDailyPageViews (/Users/noamico/dev/wasp-demo/app/src/server/workers/plausibleAnalyticsUtils.ts:28:22)
[ Server!] at calculateDailyStats (/Users/noamico/dev/wasp-demo/app/src/server/workers/calculateDailyStats.ts:44:55)
[ Server!] at async resolveWithinSeconds (/Users/noamico/dev/wasp-demo/app/node_modules/pg-boss/src/manager.js:34:14)
[ Server!] at async /Users/noamico/dev/wasp-demo/app/node_modules/p-map/index.js:57:22
Ncan u give some more info on how to utilize a flaks backend which has a websocket ? @martinsos
MSo there are two main ways to utilize that flask backend, either from the client code (React) or server code (NodeJS).
Websocket or not, this wouldn't really be Wasp specific -> but React / NodeJS specific. For example, if your Flask server has HTTP routes, you can access though using from your React or Node code. So again, nothing Wasp specific here really.
Websockets -> well again, similar thing, you would not be using though, but another library which is a better fit for websockets -> maybe https://socket.io .
Wasp does have some support for the websockets out of the box (https://wasp-lang.dev/docs/advanced/web-sockets), but this is to help you with connecting Wasp client and server code. If you want to use websockets with your Flask project, then you should set that up on your own, and it should be quite doable.
Now, what I can't know, is if you want to connect from Wasp client directly to the Flask backend via websocket(s), or you want to connect from Wasp client to Wasp server via websockets and then from there to Flask backend via websockets also. Depends if the data from Flask backend is public or not.
If it is private, and you want to first authenticate user and check if they have access, then I would advise going Wasp client -> Wasp server (does the auth and stuff) -> Flask server (produces data). On Flask server side, you could have a secret that only Wasp server knows and uses to connect to Flask server, so nobody else can access it. And Wasp server does the auth and so on, so it can decide what it forwards from Flask server to the Wasp client.
Btw, that Flask server, you will need to get that running on your own, it is a standalone service / microservice.
I hope this helps, the thing this is quite custom so I can't so easily offer more information without knowing more, but you can always ask us for more help as you go along.
Btw, would you be able to share a bit more about what you are building? Do you already have an existing Flask code? How do you imagine complete architecture of the app -> Wasp app as the main piece of the code, and some Flask code in the background doing somethign specific? Why Flask code, why not write it direclty in Wasp via Node? Because you need some Python libraries? Anything you can share helps!
Websocket or not, this wouldn't really be Wasp specific -> but React / NodeJS specific. For example, if your Flask server has HTTP routes, you can access though using from your React or Node code. So again, nothing Wasp specific here really.
Websockets -> well again, similar thing, you would not be using though, but another library which is a better fit for websockets -> maybe https://socket.io .
Wasp does have some support for the websockets out of the box (https://wasp-lang.dev/docs/advanced/web-sockets), but this is to help you with connecting Wasp client and server code. If you want to use websockets with your Flask project, then you should set that up on your own, and it should be quite doable.
Now, what I can't know, is if you want to connect from Wasp client directly to the Flask backend via websocket(s), or you want to connect from Wasp client to Wasp server via websockets and then from there to Flask backend via websockets also. Depends if the data from Flask backend is public or not.
If it is private, and you want to first authenticate user and check if they have access, then I would advise going Wasp client -> Wasp server (does the auth and stuff) -> Flask server (produces data). On Flask server side, you could have a secret that only Wasp server knows and uses to connect to Flask server, so nobody else can access it. And Wasp server does the auth and so on, so it can decide what it forwards from Flask server to the Wasp client.
Btw, that Flask server, you will need to get that running on your own, it is a standalone service / microservice.
I hope this helps, the thing this is quite custom so I can't so easily offer more information without knowing more, but you can always ask us for more help as you go along.
Btw, would you be able to share a bit more about what you are building? Do you already have an existing Flask code? How do you imagine complete architecture of the app -> Wasp app as the main piece of the code, and some Flask code in the background doing somethign specific? Why Flask code, why not write it direclty in Wasp via Node? Because you need some Python libraries? Anything you can share helps!
M@noamico what exactly would you suggest we modify regarding the default settings?