Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error by starting main #220

Closed
ThugJarno opened this issue Jan 4, 2021 · 15 comments
Closed

Error by starting main #220

ThugJarno opened this issue Jan 4, 2021 · 15 comments

Comments

@ThugJarno
Copy link

image

@hugmanrique
Copy link
Contributor

hugmanrique commented Jan 4, 2021

You're most likely running an ancient (unsupported) Node version. Minetrack requires v12.4.0+, and the current LTS is recommended. You can check your version with node -v.

@ThugJarno
Copy link
Author

image

@hugmanrique
Copy link
Contributor

sudo might be using a different path (https://superuser.com/questions/709515/command-not-found-when-using-sudo) and thus a different node binary. Minetrack itself doesn't require root privileges (in fact, doing so is insecure). If you want to bind Minetrack on a privileged port, reverse proxy it through Nginx, Apache, etc.

@ThugJarno
Copy link
Author

image

@hugmanrique
Copy link
Contributor

The SQLite dependency cannot find itself, does npm install (no sudo) return successfully? If so, try starting Minetrack again. If this doesn't fix it, I suspect this might be a permissions-related issue. Try cloning Minetrack on your home dir.

@ThugJarno
Copy link
Author

image
image
NPM audit fix doesn't fix it.

@hugmanrique
Copy link
Contributor

hugmanrique commented Jan 7, 2021

There's some potential fixes on their repo: try TryGhost/node-sqlite3#906 (comment), TryGhost/node-sqlite3#906 (comment), (other) in that order, while checking if the app starts after each solution.
Other than that, this is an SQLite 3 problem and how its node package is bundled. There's not much we can do.

@ThugJarno
Copy link
Author

Thanks it works! Next problem...

image

@ThugJarno
Copy link
Author

I'm using apache2. I tried something. New error.
image
image

@hugmanrique
Copy link
Contributor

#194

@ThugJarno
Copy link
Author

Thanks for you fast reply. But it doesn't work for me.
image
image

@hugmanrique
Copy link
Contributor

hugmanrique commented Jan 8, 2021

You're not supposed to serve Minetrack files directly (you're currently exposing your config files publicly). Move the Minetrack directory to your home dir, and setup the Apache virtual host as a reverse proxy to the Minetrack address (running on another port) as the previously mentioned issue suggests. Your config doesn't look like it, so that's why it isn't working. Minetrack runs its own HTTP and WebSocket server.

Other than that, this isn't an Apache support channel, so I can't provide much help other than that (I personally prefer Nginx over it, but that's off topic).

@ThugJarno
Copy link
Author

Is HTTPS needed?

@hugmanrique
Copy link
Contributor

Minetrack doesn't provide HTTPS support, but your Apache/Nginx/Cloudflare proxy can add/require HTTPS support.

@ThugJarno
Copy link
Author

I'm stuck for days...

image
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants