Troubl building openSaas Wasp app

Troubleshooting and help
1

I have trouble building a wasp app (the opensaas template).
Below is the log:

Build ready to start ▶️
>> Cloning github.com/samim91/etal.git commit sha e66b64e11289e7a6e5761e62440b772996ec417d into /workspace
Initialized empty Git repository in /workspace/.git/
From https://github.com/samim91/etal
 * branch              e66b64e11289e7a6e5761e62440b772996ec417d -> FETCH_HEAD
HEAD is now at e66b64e1 initial commit
#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 2.31kB done
#1 DONE 0.0s

#2 [internal] load metadata for docker.io/library/node:20
#2 DONE 1.9s

#3 [internal] load .dockerignore
#3 transferring context: 2B done
#3 DONE 0.0s

#4 [base 1/1] FROM docker.io/library/node:20@sha256:48db4f6ea21d134be744207225753a1730c4bc1b4cdf836d44511c36bf0e34d7
#4 resolve docker.io/library/node:20@sha256:48db4f6ea21d134be744207225753a1730c4bc1b4cdf836d44511c36bf0e34d7 done
#4 sha256:f6afe88969eba4306e892513b894c6aa0c5a5af23686a58606b39f1fd919e1f7 446B / 446B 0.1s done
#4 sha256:17076c042f966e11bf108c07b7f4ab88b52c1308c5993e9e7d4486742741b371 0B / 48.15MB 0.2s
#4 sha256:35daf8b1075a994bba8f2d0b52ea74d4f9d7880135db5ac3a8f631143dd8c173 0B / 1.25MB 0.2s
#4 sha256:d01ef74013ddafa2b2e9f13a2af70b9f26bae64cedf4db9b6dd92f94247dd9d3 0B / 3.32kB 0.2s
#4 sha256:17076c042f966e11bf108c07b7f4ab88b52c1308c5993e9e7d4486742741b371 7.34MB / 48.15MB 0.3s
#4 sha256:d01ef74013ddafa2b2e9f13a2af70b9f26bae64cedf4db9b6dd92f94247dd9d3 3.32kB / 3.32kB 0.3s done
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 0B / 211.27MB 0.2s
#4 sha256:35daf8b1075a994bba8f2d0b52ea74d4f9d7880135db5ac3a8f631143dd8c173 1.25MB / 1.25MB 0.4s done
#4 sha256:17076c042f966e11bf108c07b7f4ab88b52c1308c5993e9e7d4486742741b371 16.78MB / 48.15MB 0.5s
#4 sha256:2e66a70da0bec13fb3d492fcdef60fd8a5ef0a1a65c4e8a4909e26742852f0f2 1.05MB / 64.15MB 0.2s
#4 sha256:2e6afa3f266c11e8960349e7866203a9df478a50362bb5488c45fe39d99b2707 0B / 24.05MB 0.2s
#4 sha256:17076c042f966e11bf108c07b7f4ab88b52c1308c5993e9e7d4486742741b371 28.31MB / 48.15MB 0.6s
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 20.97MB / 211.27MB 0.5s
#4 sha256:2e66a70da0bec13fb3d492fcdef60fd8a5ef0a1a65c4e8a4909e26742852f0f2 9.44MB / 64.15MB 0.3s
#4 sha256:2e6afa3f266c11e8960349e7866203a9df478a50362bb5488c45fe39d99b2707 2.10MB / 24.05MB 0.3s
#4 sha256:17076c042f966e11bf108c07b7f4ab88b52c1308c5993e9e7d4486742741b371 39.85MB / 48.15MB 0.8s
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 33.55MB / 211.27MB 0.6s
#4 sha256:2e66a70da0bec13fb3d492fcdef60fd8a5ef0a1a65c4e8a4909e26742852f0f2 16.78MB / 64.15MB 0.5s
#4 sha256:17076c042f966e11bf108c07b7f4ab88b52c1308c5993e9e7d4486742741b371 47.19MB / 48.15MB 0.9s
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 45.09MB / 211.27MB 0.8s
#4 sha256:2e6afa3f266c11e8960349e7866203a9df478a50362bb5488c45fe39d99b2707 5.24MB / 24.05MB 0.5s
#4 sha256:17076c042f966e11bf108c07b7f4ab88b52c1308c5993e9e7d4486742741b371 48.15MB / 48.15MB 1.0s done
#4 sha256:2e66a70da0bec13fb3d492fcdef60fd8a5ef0a1a65c4e8a4909e26742852f0f2 20.97MB / 64.15MB 0.6s
#4 sha256:2e66a70da0bec13fb3d492fcdef60fd8a5ef0a1a65c4e8a4909e26742852f0f2 30.41MB / 64.15MB 0.8s
#4 sha256:2e6afa3f266c11e8960349e7866203a9df478a50362bb5488c45fe39d99b2707 13.63MB / 24.05MB 0.8s
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 61.87MB / 211.27MB 1.1s
#4 sha256:2e66a70da0bec13fb3d492fcdef60fd8a5ef0a1a65c4e8a4909e26742852f0f2 38.80MB / 64.15MB 0.9s
#4 sha256:8cd46d290033f265db57fd808ac81c444ec5a5b3f189c3d6d85043b647336913 1.05MB / 49.56MB 0.2s
#4 sha256:2e6afa3f266c11e8960349e7866203a9df478a50362bb5488c45fe39d99b2707 19.92MB / 24.05MB 0.9s
#4 sha256:8cd46d290033f265db57fd808ac81c444ec5a5b3f189c3d6d85043b647336913 8.43MB / 49.56MB 0.3s
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 77.59MB / 211.27MB 1.4s
#4 sha256:2e66a70da0bec13fb3d492fcdef60fd8a5ef0a1a65c4e8a4909e26742852f0f2 45.09MB / 64.15MB 1.1s
#4 sha256:2e6afa3f266c11e8960349e7866203a9df478a50362bb5488c45fe39d99b2707 24.05MB / 24.05MB 1.0s done
#4 sha256:8cd46d290033f265db57fd808ac81c444ec5a5b3f189c3d6d85043b647336913 12.58MB / 49.56MB 0.5s
#4 sha256:2e66a70da0bec13fb3d492fcdef60fd8a5ef0a1a65c4e8a4909e26742852f0f2 52.43MB / 64.15MB 1.2s
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 91.23MB / 211.27MB 1.5s
#4 sha256:2e66a70da0bec13fb3d492fcdef60fd8a5ef0a1a65c4e8a4909e26742852f0f2 59.77MB / 64.15MB 1.4s
#4 sha256:8cd46d290033f265db57fd808ac81c444ec5a5b3f189c3d6d85043b647336913 26.21MB / 49.56MB 0.8s
#4 sha256:2e66a70da0bec13fb3d492fcdef60fd8a5ef0a1a65c4e8a4909e26742852f0f2 64.15MB / 64.15MB 1.5s done
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 106.95MB / 211.27MB 1.8s
#4 sha256:8cd46d290033f265db57fd808ac81c444ec5a5b3f189c3d6d85043b647336913 49.56MB / 49.56MB 1.0s done
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 119.54MB / 211.27MB 2.0s
#4 extracting sha256:8cd46d290033f265db57fd808ac81c444ec5a5b3f189c3d6d85043b647336913
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 146.80MB / 211.27MB 2.4s
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 158.33MB / 211.27MB 2.6s
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 173.02MB / 211.27MB 2.7s
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 187.70MB / 211.27MB 5.9s
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 198.40MB / 211.27MB 6.0s
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 211.27MB / 211.27MB 6.3s
#4 sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 211.27MB / 211.27MB 6.6s done
#4 extracting sha256:8cd46d290033f265db57fd808ac81c444ec5a5b3f189c3d6d85043b647336913 4.7s done
#4 extracting sha256:2e6afa3f266c11e8960349e7866203a9df478a50362bb5488c45fe39d99b2707
#4 extracting sha256:2e6afa3f266c11e8960349e7866203a9df478a50362bb5488c45fe39d99b2707 0.5s done
#4 extracting sha256:2e66a70da0bec13fb3d492fcdef60fd8a5ef0a1a65c4e8a4909e26742852f0f2
#4 ...

#5 [internal] load build context
#5 transferring context: 327.00MB 8.9s
#5 ...

#4 [base 1/1] FROM docker.io/library/node:20@sha256:48db4f6ea21d134be744207225753a1730c4bc1b4cdf836d44511c36bf0e34d7
#4 extracting sha256:2e66a70da0bec13fb3d492fcdef60fd8a5ef0a1a65c4e8a4909e26742852f0f2 5.0s done
#4 extracting sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81
#4 ...

#5 [internal] load build context
#5 transferring context: 575.60MB 13.7s done
#5 DONE 13.8s

#4 [base 1/1] FROM docker.io/library/node:20@sha256:48db4f6ea21d134be744207225753a1730c4bc1b4cdf836d44511c36bf0e34d7
#4 extracting sha256:1c8ff076d818ad6b8557e03e10c83657cc716ab287c8380054ff91571c8cae81 4.8s done
#4 DONE 17.2s

#4 [base 1/1] FROM docker.io/library/node:20@sha256:48db4f6ea21d134be744207225753a1730c4bc1b4cdf836d44511c36bf0e34d7
#4 extracting sha256:d01ef74013ddafa2b2e9f13a2af70b9f26bae64cedf4db9b6dd92f94247dd9d3 0.0s done
#4 extracting sha256:17076c042f966e11bf108c07b7f4ab88b52c1308c5993e9e7d4486742741b371
#4 extracting sha256:17076c042f966e11bf108c07b7f4ab88b52c1308c5993e9e7d4486742741b371 1.4s done
#4 DONE 18.6s

#4 [base 1/1] FROM docker.io/library/node:20@sha256:48db4f6ea21d134be744207225753a1730c4bc1b4cdf836d44511c36bf0e34d7
#4 extracting sha256:35daf8b1075a994bba8f2d0b52ea74d4f9d7880135db5ac3a8f631143dd8c173 0.0s done
#4 extracting sha256:f6afe88969eba4306e892513b894c6aa0c5a5af23686a58606b39f1fd919e1f7 done
#4 DONE 18.6s

#6 [server-builder  1/11] RUN apt update && apt install --yes build-essential python3 libtool autoconf automake && rm -rf /var/lib/apt/lists/*
#6 ...

#7 [wasp-builder 1/4] WORKDIR /wasp
#7 DONE 1.1s

#6 [server-builder  1/11] RUN apt update && apt install --yes build-essential python3 libtool autoconf automake && rm -rf /var/lib/apt/lists/*
#6 1.133 
#6 1.133 WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
#6 1.133 
#6 1.162 Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]
#6 1.171 Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
#6 1.171 Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
#6 1.234 Get:4 http://deb.debian.org/debian bookworm/main amd64 Packages [8787 kB]
#6 1.325 Get:5 http://deb.debian.org/debian bookworm-updates/main amd64 Packages [2468 B]
#6 1.371 Get:6 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages [182 kB]
#6 2.263 Fetched 9226 kB in 1s (8299 kB/s)
#6 2.263 Reading package lists...
#6 2.748 Building dependency tree...
#6 2.843 Reading state information...
#6 2.854 4 packages can be upgraded. Run 'apt list --upgradable' to see them.
#6 2.858 
#6 2.858 WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
#6 2.858 
#6 2.860 Reading package lists...
#6 3.322 Building dependency tree...
#6 3.430 Reading state information...
#6 3.554 python3 is already the newest version (3.11.2-1+b1).
#6 3.554 python3 set to manually installed.
#6 3.554 libtool is already the newest version (2.4.7-7~deb12u1).
#6 3.554 autoconf is already the newest version (2.71-3).
#6 3.554 automake is already the newest version (1:1.16.5-1.3).
#6 3.554 The following NEW packages will be installed:
#6 3.555   build-essential
#6 3.572 0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
#6 3.572 Need to get 7704 B of archives.
#6 3.572 After this operation, 20.5 kB of additional disk space will be used.
#6 3.572 Get:1 http://deb.debian.org/debian bookworm/main amd64 build-essential amd64 12.9 [7704 B]
#6 3.803 debconf: delaying package configuration, since apt-utils is not installed
#6 3.845 Fetched 7704 B in 0s (544 kB/s)
#6 3.863 Selecting previously unselected package build-essential.
#6 3.863 (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23242 files and directories currently installed.)
#6 3.877 Preparing to unpack .../build-essential_12.9_amd64.deb ...
#6 3.879 Unpacking build-essential (12.9) ...
#6 3.904 Setting up build-essential (12.9) ...
#6 ...

#8 [server-production  1/10] RUN apt update && apt install --yes python3 && rm -rf /var/lib/apt/lists/*
#8 1.133 
#8 1.133 WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
#8 1.133 
#8 1.163 Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]
#8 1.173 Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
#8 1.174 Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
#8 1.234 Get:4 http://deb.debian.org/debian bookworm/main amd64 Packages [8787 kB]
#8 1.359 Get:5 http://deb.debian.org/debian bookworm-updates/main amd64 Packages [2468 B]
#8 1.359 Get:6 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages [182 kB]
#8 2.312 Fetched 9226 kB in 1s (7947 kB/s)
#8 2.312 Reading package lists...
#8 2.812 Building dependency tree...
#8 2.927 Reading state information...
#8 2.939 4 packages can be upgraded. Run 'apt list --upgradable' to see them.
#8 2.942 
#8 2.942 WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
#8 2.942 
#8 2.944 Reading package lists...
#8 3.398 Building dependency tree...
#8 3.505 Reading state information...
#8 3.632 python3 is already the newest version (3.11.2-1+b1).
#8 3.632 python3 set to manually installed.
#8 3.632 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
#8 DONE 4.2s

#6 [server-builder  1/11] RUN apt update && apt install --yes build-essential python3 libtool autoconf automake && rm -rf /var/lib/apt/lists/*
#6 DONE 4.2s

#9 [server-production  2/10] WORKDIR /app
#9 DONE 0.0s

#10 [server-builder  2/11] WORKDIR /app
#10 DONE 0.0s

#11 [wasp-builder 2/4] ADD . .
#11 DONE 4.4s

#12 [wasp-builder 3/4] RUN curl -sSL https://get.wasp-lang.dev/installer.sh | sh
#12 0.930 Installing wasp version 0.14.2 (latest).
#12 0.930 
#12 0.930 /root/.local/share/wasp-lang/0.14.2 does not exist, creating it...
#12 0.933 Downloading binary package to temporary dir and unpacking it there...
#12 0.933 
#12 0.938   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
#12 0.938                                  Dload  Upload   Total   Spent    Left  Speed
#12 0.938 
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
#12 1.977 
 25 77.3M   25 20.0M    0     0  19.2M      0  0:00:04  0:00:01  0:00:03 19.2M
100 77.3M  100 77.3M    0     0  44.1M      0  0:00:01  0:00:01 --:--:-- 80.3M
#12 2.697 
#12 2.697 Installing wasp data to /root/.local/share/wasp-lang/0.14.2.
#12 2.697 
#12 5.108 /root/.local/bin does not exist, creating it...
#12 5.111 Installing wasp executable to /root/.local/bin/wasp.
#12 5.112 
#12 5.112 ==============================================
#12 5.117 
#12 5.117 e[31mWARNINGe[0m: It looks like '/root/.local/bin' is not on your PATH! You will not be able to invoke wasp from the terminal by its name.
#12 5.117   You can add it to your PATH by adding following line into your profile file (~/.profile or ~/.zshrc or ~/.bash_profile or ~/.bashrc or some other, depending on your configuration):
#12 5.117       e[1mexport PATH=$PATH:/root/.local/bine[0m
#12 5.117 
#12 5.117 e[32mwasp has been successfully installed! To create your first app, do:e[0m
#12 5.122  - Add wasp to your PATH as described above.
#12 5.122  - e[1mwasp new MyAppe[0m
#12 5.122 
#12 5.122 Optional:
#12 5.122  - to install bash completion for wasp, run e[1mwasp completione[0m and follow the instructions.
#12 DONE 5.5s

#13 [wasp-builder 4/4] RUN /root/.local/bin/wasp build
#13 0.245 e[33m
#13 0.245 ? --- Clearing the content of the .wasp/out/sdk directory... ---------------------
#13 0.245 e[0m
#13 0.245 e[33m
#13 0.245 ? --- Successfully cleared the contents of the .wasp/out/sdk directory. ----------
#13 0.245 e[0m
#13 0.245 e[33m
#13 0.245 ? --- Building wasp project... ---------------------------------------------------
#13 0.245 e[0m
#13 0.245 e[31m
#13 0.245 
#13 0.245 ? --- [Error] Your wasp project failed to compile: -------------------------------
#13 0.245 
#13 0.245 - Couldn't find the schema.prisma file in the /wasp/ directory. 
#13 0.245 Read more: https://wasp-lang.dev/docs/migrate-from-0-13-to-0-14#migrate-to-the-new-schemaprisma-filee[0m
#13 0.245 e[31m
#13 0.245 
#13 0.245 ? --- [Error] Building of wasp project failed: -----------------------------------
#13 0.245 
#13 0.245 1 errors found.e[0m
#13 ERROR: process "/bin/sh -c /root/.local/bin/wasp build" did not complete successfully: exit code: 1
------
 > [wasp-builder 4/4] RUN /root/.local/bin/wasp build:
0.245 
0.245 ? --- [Error] Your wasp project failed to compile: -------------------------------
0.245 
0.245 - Couldn't find the schema.prisma file in the /wasp/ directory. 
0.245 Read more: https://wasp-lang.dev/docs/migrate-from-0-13-to-0-14#migrate-to-the-new-schemaprisma-filee[0m
0.245 e[31m
0.245 
0.245 ? --- [Error] Building of wasp project failed: -----------------------------------
0.245 
0.245 1 errors found.e[0m
------
Dockerfile:8
--------------------
   6 |     ADD . .
   7 |     RUN curl -sSL https://get.wasp-lang.dev/installer.sh | sh
   8 | >>> RUN /root/.local/bin/wasp build
   9 |     
  10 |     # Build the server
--------------------
error: failed to solve: process "/bin/sh -c /root/.local/bin/wasp build" did not complete successfully: exit code: 1
exit status 1
2

Hello,

Could you give us a small repository to replicate the issue? Your repository is private and without a way to reproduce the issue, I can’t find what’s wrong :confused:

3

I made the repo public!

4

Your build fails locally with the same error message than the one displayed on Koyeb:

 => ERROR [wasp-builder 4/4] RUN /root/.local/bin/wasp build                                                                                                                                                                                                                                                                                                                                                                                                                                                          0.4s
------
 > [wasp-builder 4/4] RUN /root/.local/bin/wasp build:
0.324
0.324 ? --- Clearing the content of the .wasp/out/sdk directory... ---------------------
0.324
0.324
0.324 ? --- Successfully cleared the contents of the .wasp/out/sdk directory. ----------
0.324
0.324
0.324 ? --- Building wasp project... ---------------------------------------------------
0.324
0.324
0.324
0.324 ? --- [Error] Your wasp project failed to compile: -------------------------------
0.324
0.324 - Couldn't find the schema.prisma file in the /wasp/ directory.
0.324 Read more: https://wasp-lang.dev/docs/migrate-from-0-13-to-0-14#migrate-to-the-new-schemaprisma-file
0.324
0.324
0.324 ? --- [Error] Building of wasp project failed: -----------------------------------
0.324
0.324 1 errors found.
------
Dockerfile:8
--------------------
   6 |     ADD . .
   7 |     RUN curl -sSL https://get.wasp-lang.dev/installer.sh | sh
   8 | >>> RUN /root/.local/bin/wasp build
   9 |
  10 |     # Build the server
--------------------
ERROR: failed to solve: process "/bin/sh -c /root/.local/bin/wasp build" did not complete successfully: exit code: 1

View build details: docker-desktop://dashboard/build/desktop-linux/desktop-linux/jlfa8pbvu9n2nh3lmwxnio5f8

The error message gives you a link with the procedure to fix the issue: Migration from 0.13.X to 0.14.X | Wasp

To reproduce locally, run docker run --platform linux/amd64 ..

5

I resolved this by building it from scratch with the newest wasp version.
It builds the app now, However, now I get the following error when deploying:

Instance created. Preparing to start…
Instance is starting. Propagating network configuration…

server@0.0.0 start-production
npm run db-migrate-prod && NODE_ENV=production npm run start
server@0.0.0 db-migrate-prod
prisma migrate deploy --schema=…/db/schema.prisma
Prisma schema loaded from …/db/schema.prisma
Datasource “db”: PostgreSQL database “koyebdb”, schema “public” at “ep-dry-truth-a2kdcgss.eu-central-1.pg.koyeb.app”
1 migration found in prisma/migrations
No pending migrations to apply.
server@0.0.0 start
npm run validate-env && node --enable-source-maps -r dotenv/config bundle/server.js
server@0.0.0 validate-env
node -r dotenv/config ./scripts/validate-env.mjs
:mag: Validating environment variables…
pg-boss failed to start!
:rocket: “Google” auth initialized
:rocket: “Email and password” auth initialized
Starting pg-boss…
error: connection is insecure (try using sslmode=require)
at /app/node_modules/pg-pool/index.js:45:11
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Db.executeSql (/app/node_modules/pg-boss/src/db.js:28:14)
at async Contractor.isInstalled (/app/node_modules/pg-boss/src/contractor.js:32:20)
at async Contractor.start (/app/node_modules/pg-boss/src/contractor.js:37:23)
at async PgBoss.start (/app/node_modules/pg-boss/src/index.js:103:5)
at async startPgBoss (/app/.wasp/out/sdk/wasp/server/jobs/core/pgBoss/pgBoss.ts:63:5)
at async startServer (/app/.wasp/build/server/src/server.ts:14:3) {
length: 73,
severity: ‘ERROR’,
code: ‘XX000’,
detail: undefined,
hint: undefined,
position: undefined,
internalPosition: undefined,
internalQuery: undefined,
where: undefined,
schema: undefined,
table: undefined,
column: undefined,
dataType: undefined,
constraint: undefined,
file: undefined,
line: undefined,
routine: undefined
}
node:internal/process/promises:389
new UnhandledPromiseRejection(reason);
^
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 “#”.
at throwUnhandledRejectionsMode (node:internal/process/promises:389:7)
at processPromiseRejections (node:internal/process/promises:470:17)
at process.processTicksAndRejections (node:internal/process/task_queues:96:32) {
code: ‘ERR_UNHANDLED_REJECTION’
}
Node.js v20.17.0
npm notice
npm notice New patch version of npm available! 10.8.2 → 10.8.3
npm notice Changelog: Release v10.8.3 · npm/cli · GitHub
npm notice To update run: npm install -g npm@10.8.3
npm notice
Server listening on port 8000
server@0.0.0 start-production
npm run db-migrate-prod && NODE_ENV=production npm run start
server@0.0.0 db-migrate-prod
prisma migrate deploy --schema=…/db/schema.prisma
Prisma schema loaded from …/db/schema.prisma
Datasource “db”: PostgreSQL database “koyebdb”, schema “public” at “ep-dry-truth-a2kdcgss.eu-central-1.pg.koyeb.app”
1 migration found in prisma/migrations
No pending migrations to apply.
server@0.0.0 start
npm run validate-env && node --enable-source-maps -r dotenv/config bundle/server.js
server@0.0.0 validate-env
node -r dotenv/config ./scripts/validate-env.mjs
:mag: Validating environment variables…
:rocket: “Google” auth initialized
:rocket: “Email and password” auth initialized
Starting pg-boss…
pg-boss failed to start!
Server listening on port 8000
error: connection is insecure (try using sslmode=require)
at /app/node_modules/pg-pool/index.js:45:11
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Db.executeSql (/app/node_modules/pg-boss/src/db.js:28:14)
at async Contractor.isInstalled (/app/node_modules/pg-boss/src/contractor.js:32:20)
at async Contractor.start (/app/node_modules/pg-boss/src/contractor.js:37:23)
at async PgBoss.start (/app/node_modules/pg-boss/src/index.js:103:5)
at async startPgBoss (/app/.wasp/out/sdk/wasp/server/jobs/core/pgBoss/pgBoss.ts:63:5)
at async startServer (/app/.wasp/build/server/src/server.ts:14:3) {
length: 73,
severity: ‘ERROR’,
code: ‘XX000’,
detail: undefined,
hint: undefined,
position: undefined,
internalPosition: undefined,
internalQuery: undefined,
where: undefined,
schema: undefined,
table: undefined,
column: undefined,
dataType: undefined,
constraint: undefined,
file: undefined,
line: undefined,
routine: undefined
}
node:internal/process/promises:389
new UnhandledPromiseRejection(reason);
^
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 “#”.
at throwUnhandledRejectionsMode (node:internal/process/promises:389:7)
at processPromiseRejections (node:internal/process/promises:470:17)
at process.processTicksAndRejections (node:internal/process/task_queues:96:32) {
code: ‘ERR_UNHANDLED_REJECTION’
}
Node.js v20.17.0
npm notice
npm notice New patch version of npm available! 10.8.2 → 10.8.3
npm notice Changelog: Release v10.8.3 · npm/cli · GitHub
npm notice To update run: npm install -g npm@10.8.3
npm notice
Application exited with code 1. This usually indicates an application failure. Check that the command used to launch your application is correct.
Instance stopped
Instance created. Preparing to start…

6

The message says the connection is insecure, and it is an error.

Can you try to append ?sslmode=require to your connection string?