Snowdevil Comments - Answer Overflow

Topics

Snowdevil

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

Not yet, was busy last week with work and appointments, then wife's bday over the weekend xD This week I don't have much going on so will be revisiting it. It's gotta work eventually and when it does we can get a gist thrown together on steps it took to do so 🙂

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

Yeah i just haven't had the time in the past couple days to get to the pc

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

Will do, thank you!

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

I'll see if there are any similarities with that setup and working with Digital Ocean to see if I can fix the issues I'm having. I enjoy DO a lot as it has a lot of convenient automation features built in, and scaling is easy. Worst case scenario I suck and can't get it to work through all methods, I'll follow that with a VPS rather than the app deployment module xD @Killshot

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

This is the error I get anytime I try to run any command in the deploy phase on the digital ocean server. The database is working fine, and I'm able to connect to it and migrate object model changes in the build phase.

2025-03-12T21:28:21.946084387Z /layers/heroku_nodejs/profile/profile.d/WEB_CONCURRENCY.sh: line 35: cat: command not found
2025-03-12T21:28:21.950239008Z /layers/heroku_nodejs/profile/profile.d/WEB_CONCURRENCY.sh: line 35: / 1048576: syntax error: operand expected (error token is "/ 1048576")
2025-03-12T21:28:22.041401617Z /layers/heroku_nodejs/profile/profile.d/cnb_shim_symlink.sh: line 1: readlink: command not found
2025-03-12T21:28:22.051169816Z /layers/heroku_nodejs/profile/profile.d/cnb_shim_symlink.sh: line 1: readlink: command not found
2025-03-12T21:28:22.062458680Z /cnb/lifecycle/launcher: line 4: exec: bash: not found
2025-03-12T21:28:12.823104650Z /layers/heroku_nodejs/profile/profile.d/WEB_CONCURRENCY.sh: line 35: cat: command not found
2025-03-12T21:28:12.828661611Z /layers/heroku_nodejs/profile/profile.d/WEB_CONCURRENCY.sh: line 35: / 1048576: syntax error: operand expected (error token is "/ 1048576")
2025-03-12T21:28:12.905493539Z /layers/heroku_nodejs/profile/profile.d/cnb_shim_symlink.sh: line 1: readlink: command not found
2025-03-12T21:28:12.961860416Z /layers/heroku_nodejs/profile/profile.d/cnb_shim_symlink.sh: line 1: readlink: command not found
2025-03-12T21:28:12.992322782Z /cnb/lifecycle/launcher: line 4: exec: bash: not found

2025-03-12T21:28:21.946084387Z /layers/heroku_nodejs/profile/profile.d/WEB_CONCURRENCY.sh: line 35: cat: command not found
2025-03-12T21:28:21.950239008Z /layers/heroku_nodejs/profile/profile.d/WEB_CONCURRENCY.sh: line 35: / 1048576: syntax error: operand expected (error token is "/ 1048576")
2025-03-12T21:28:22.041401617Z /layers/heroku_nodejs/profile/profile.d/cnb_shim_symlink.sh: line 1: readlink: command not found
2025-03-12T21:28:22.051169816Z /layers/heroku_nodejs/profile/profile.d/cnb_shim_symlink.sh: line 1: readlink: command not found
2025-03-12T21:28:22.062458680Z /cnb/lifecycle/launcher: line 4: exec: bash: not found
2025-03-12T21:28:12.823104650Z /layers/heroku_nodejs/profile/profile.d/WEB_CONCURRENCY.sh: line 35: cat: command not found
2025-03-12T21:28:12.828661611Z /layers/heroku_nodejs/profile/profile.d/WEB_CONCURRENCY.sh: line 35: / 1048576: syntax error: operand expected (error token is "/ 1048576")
2025-03-12T21:28:12.905493539Z /layers/heroku_nodejs/profile/profile.d/cnb_shim_symlink.sh: line 1: readlink: command not found
2025-03-12T21:28:12.961860416Z /layers/heroku_nodejs/profile/profile.d/cnb_shim_symlink.sh: line 1: readlink: command not found
2025-03-12T21:28:12.992322782Z /cnb/lifecycle/launcher: line 4: exec: bash: not found

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

I think I got the connection working with the SSL stuff. But I'm noticing since the beginning of all this, even with the db stuff fixed, I'm still not able to deploy the web server on digital ocean. When running wasp start in the build phase, it starts the wasp package properly, but gets stuck in the build phase when it needs to finish the build phase and move to deploy/run phase for DO. When I run wasp start in the deploy phase, I keep getting errors no matter what I've done so far. I think the end of the build phase in docker containerizes the build, and then I'm unable to launch any wasp commands in that build.

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

Digital Ocean

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

I'll dm you the database information and see if you have any luck.

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

It seems maybe there's something wrong with a SSL certificate

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

[ Server!]     at async startPgBoss (/home/snowdevil/repo/granite-main/saas-service-booking/granite-scheduling-main/app/.wasp/out/sdk/wasp/dist/server/jobs/core/pgBoss/pgBoss.js:54:9)
[ Server!]     at async startServer (/home/snowdevil/repo/granite-main/saas-service-booking/granite-scheduling-main/app/.wasp/out/server/src/server.ts:14:3) {
[ Server!]   code: 'SELF_SIGNED_CERT_IN_CHAIN'
[ Server!] }
[ Server ] Server listening on port 3001
[ Server!] node:internal/process/promises:392
[ Server!]       new UnhandledPromiseRejection(reason);
[ Server!]       ^
[ Server!] 
[ Server!] UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "#<PgBoss>".
[ Server!]     at throwUnhandledRejectionsMode (node:internal/process/promises:392:7)
[ Server!]     at processPromiseRejections (node:internal/process/promises:475:17)
[ Server!]     at process.processTicksAndRejections (node:internal/process/task_queues:106:32) {
[ Server!]   code: 'ERR_UNHANDLED_REJECTION'
[ Server!] }
[ Server!] 
[ Server!] Node.js v23.9.0
[ Server ] [nodemon] app crashed - waiting for file changes before starting...^C

[ Server!]     at async startPgBoss (/home/snowdevil/repo/granite-main/saas-service-booking/granite-scheduling-main/app/.wasp/out/sdk/wasp/dist/server/jobs/core/pgBoss/pgBoss.js:54:9)
[ Server!]     at async startServer (/home/snowdevil/repo/granite-main/saas-service-booking/granite-scheduling-main/app/.wasp/out/server/src/server.ts:14:3) {
[ Server!]   code: 'SELF_SIGNED_CERT_IN_CHAIN'
[ Server!] }
[ Server ] Server listening on port 3001
[ Server!] node:internal/process/promises:392
[ Server!]       new UnhandledPromiseRejection(reason);
[ Server!]       ^
[ Server!] 
[ Server!] UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "#<PgBoss>".
[ Server!]     at throwUnhandledRejectionsMode (node:internal/process/promises:392:7)
[ Server!]     at processPromiseRejections (node:internal/process/promises:475:17)
[ Server!]     at process.processTicksAndRejections (node:internal/process/task_queues:106:32) {
[ Server!]   code: 'ERR_UNHANDLED_REJECTION'
[ Server!] }
[ Server!] 
[ Server!] Node.js v23.9.0
[ Server ] [nodemon] app crashed - waiting for file changes before starting...^C

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

I do get the error below though even though the app still runs locally. And still not able to get it running on Digital ocean to a similar issue.

[ Client ]   VITE v6.2.1  ready in 505 ms
[ Client ] 
[ Client ]   ➜  Local:   http://localhost:3000/
[ Client ]   ➜  Network: http://172.28.19.131:3000/
[ Client ]   ➜  press h + enter to show help
[ Server ] 
[ Server ] > [email protected] start
[ Server ] > node --enable-source-maps -r dotenv/config bundle/server.js
[ Server ] 
[ Server ] 🚀 "Email and password" auth initialized
[ Server ] Starting pg-boss...
[ Server!] pg-boss failed to start!
[ Server!] Error: self-signed certificate in certificate chain
[ Server!]     at /home/snowdevil/repo/granite-main/saas-service-booking/granite-scheduling-main/app/node_modules/pg-pool/index.js:45:11
[ Server!]     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
[ Server!]     at async Db.executeSql (/home/snowdevil/repo/granite-main/saas-service-booking/granite-scheduling-main/app/node_modules/pg-boss/src/db.js:28:14)
[ Server!]     at async Contractor.isInstalled (/home/snowdevil/repo/granite-main/saas-service-booking/granite-scheduling-main/app/node_modules/pg-boss/src/contractor.js:32:20)
[ Server!]     at async Contractor.start (/home/snowdevil/repo/granite-main/saas-service-booking/granite-scheduling-main/app/node_modules/pg-boss/src/contractor.js:37:23)
[ Server!]     at async PgBoss.start (/home/snowdevil/repo/granite-main/saas-service-booking/granite-scheduling-main/app/node_modules/pg-boss/src/index.js:103:5)

[ Client ]   VITE v6.2.1  ready in 505 ms
[ Client ] 
[ Client ]   ➜  Local:   http://localhost:3000/
[ Client ]   ➜  Network: http://172.28.19.131:3000/
[ Client ]   ➜  press h + enter to show help
[ Server ] 
[ Server ] > [email protected] start
[ Server ] > node --enable-source-maps -r dotenv/config bundle/server.js
[ Server ] 
[ Server ] 🚀 "Email and password" auth initialized
[ Server ] Starting pg-boss...
[ Server!] pg-boss failed to start!
[ Server!] Error: self-signed certificate in certificate chain
[ Server!]     at /home/snowdevil/repo/granite-main/saas-service-booking/granite-scheduling-main/app/node_modules/pg-pool/index.js:45:11
[ Server!]     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
[ Server!]     at async Db.executeSql (/home/snowdevil/repo/granite-main/saas-service-booking/granite-scheduling-main/app/node_modules/pg-boss/src/db.js:28:14)
[ Server!]     at async Contractor.isInstalled (/home/snowdevil/repo/granite-main/saas-service-booking/granite-scheduling-main/app/node_modules/pg-boss/src/contractor.js:32:20)
[ Server!]     at async Contractor.start (/home/snowdevil/repo/granite-main/saas-service-booking/granite-scheduling-main/app/node_modules/pg-boss/src/contractor.js:37:23)
[ Server!]     at async PgBoss.start (/home/snowdevil/repo/granite-main/saas-service-booking/granite-scheduling-main/app/node_modules/pg-boss/src/index.js:103:5)

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

It works! I just had to disable trusted sources to allow anyone to access. Now to create a new trusted source and go back to just trusted source connections and such. But at least everything runs so a foundation is officially set to build upon 🙂 Thanks for your help! https://prnt.sc/Hj-S9pb2uEjL

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

With digital ocean as well?

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

I appreciate it! I'll check back tonight with good or bad news xD

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

Your probably right, my first time setting up a host. I've only ever done local development

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

Ok I can give it a shot after work. If it's not accessible, then I'm guessing i would have to work with DO on it as it would be an access issue. I've spent a few hours tinkering around with a million settings and setups last night lkl

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

It would just throw a generic error saying it couldn't connect to the database when running wasp start locally

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

I used the string parameter from the managed db which includes the url,pw,port,etc.

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

I tried doing that last part with the ENV variable for the database url, but it still isn't able to find it

59 replies

•Created by Snowdevil on 3/11/2025 in #🙋questions

Set-up Hosting SAAS Wasp on Digital Ocean

The issue I believe is not being able to connect to a db. I have a managed PostGre database setup in digital ocean, and when attempting to start the app locally, it won't connect to it.

59 replies