Bitnami Install Died

So, I’m getting an error I can’t find any info on fixing, and the logs are basically worthless.

Background info:

Site: nextgenwar.info
OS: Debian GNU/Linux, v10
Node Version: v14.17.0
Ghost Version: 4.22.3
Ghost-CLI Version: 1.17.1
Environment: production
Browser: N/A

I run this command:
‘ghost start -V’

[02:54:02] Checking system Node.js version [started]
[02:54:02] Checking system Node.js version - found v14.17.0 [title changed]
[02:54:02] Checking system Node.js version - found v14.17.0 [completed]
[02:54:02] Ensuring user is not logged in as ghost user [started]
[02:54:02] Ensuring user is not logged in as ghost user [skipped]
[02:54:02] Checking if logged in user is directory owner [started]
[02:54:02] Checking if logged in user is directory owner [skipped]
[02:54:02] Checking current folder permissions [started]
[02:54:02] Checking current folder permissions [completed]
[02:54:02] Validating config [started]
[02:54:02] Validating config [completed]
[02:54:02] Checking memory availability [started]
[02:54:02] Checking memory availability [completed]
[02:54:02] Checking binary dependencies [started]
[02:54:02] Checking binary dependencies [completed]
:heavy_multiplication_x: Starting Ghost: 10-240-0-88
A GhostError occurred.

Message: Ghost was able to start, but errored during boot with: We detected a misuse. Please read the stack trace.
Stack: Error: Ghost was able to start, but errored during boot with: We detected a misuse. Please read the stack trace.
at ChildProcess. (/opt/bitnami/apps/ghost/lib/node_modules/ghost-cli/lib/utils/local-process.js:75:35)
at ChildProcess.emit (events.js:376:20)
at emit (internal/child_process.js:910:12)
at processTicksAndRejections (internal/process/task_queues.js:83:21)

Debug Information:
OS: Debian GNU/Linux, v10
Node Version: v14.17.0
Ghost Version: 4.22.3
Ghost-CLI Version: 1.17.1
Environment: production
Command: ‘ghost start -V’

Additional log info available in: /home/bitnami/.ghost/logs/ghost-cli-debug-2021-11-16T02_54_06_997Z.log

The log contains the exact same thing as the above with the ChildProcess data.

I can’t for the life of me figure out what’s wrong.

Any help?

Just in case anyone else gets this…

Even though I use a rewrite rule in Apache to force all transactions to be https, because my config.production.json had the old http://site:80 in the url field, the stripe connection was failing because it would refuse to work with a non-encrypted site.

I merely changed the URL field to https://site (and removed the port number) and everything worked.