search

small-tech / site.js

[Moved to Codeberg] Develop, test, and deploy your secure static or dynamic personal web site with zero configuration.
GNU Affero General Public License v3.0
474 stars 20 forks source link

site enable --owncast gives error #46

Open mroberts1 opened 3 years ago

mroberts1 commented 3 years ago

I installed an Owncast instance on Linode and installed Site.js successfully. I then tried to install Owncast per the instructions on the site, but when I run site enable --owncast the server doesn't launch and I get the error below. I'm very unfamiliar with servers so any suggestions as to what the problem is would be appreciated.

✨ ❨site.js❩ Launching server… (node:5811) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'index' of null at /usr/local/bin/bin/commands/enable.js:315:63 at processTicksAndRejections (internal/process/task_queues.js:97:5) (node:5811) UnhandledPromiseRejectionWarning: Unhandled promise rejection. 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(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2) (node:5811) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

aral commented 3 years ago

Ah, darn, looks like it’s failing on an assumption with an error message so we don’t know what the actual error is.

What OS is your instance running?

Worst case scenario, would you be up for giving me access to the server so I can ssh in and poke around?

mroberts1 commented 3 years ago

My Linode instance is Debian 10 because it supports one-click install of Owncast. It appears that the instance comes packaged with Owncast and Caddy as the SSL reverse proxy server, which is automatically enabled on port 80.

I was already able to stream video with the default setup but have had a lot of trouble configuring the VPS server - I don't know anything about FQDNs, DNS addresses, domains, etc. so that's probably why after installing Site.js it generates an error.

I can share the SSH public key if you want to login and have a look but would need a more secure way to do that than just posting it here!