Joseph Huckaby

I do apologize, but Cronicle v1 really doesn't support HTTPS, even through a proxy. The live log watcher is one of the casualties. You can check out Mike's fork over...

I assure you this is a false positive. LogAlert is 100% open source, and the EXE was packaged by the widely used and trusted [pkg](https://www.npmjs.com/package/pkg) system made by [Vercel](https://vercel.com/). It...

Released [LogAlert v1.0.4](https://github.com/jhuckaby/logalert/releases/tag/v1.0.4) with everything rebuilt on Node.js v18 (LTS), and latest pkg (v5.8.1). Maybe this will make your virus scanner happy? I honestly don't know 🤷🏻‍♂️

Looks like this kind of thing happens a lot. See [pkg issue #1715](https://github.com/vercel/pkg/issues/1715) and [pkg issue #1540](https://github.com/vercel/pkg/issues/1540). Maybe we can try to report the LogAlert EXE as a false positive...

I'm so sorry, I have absolutely no idea how to compile this for ARM. You could try installing it from source. All you need is to have Node.js installed (they...

Please explain what "does not work" means. Are you seeing an error? Does the binary not launch? What is the output on the Terminal? It's possible that LogAlert cannot interpret...

You didn't offend me at all. I am not sure why LogAlert isn't working for you, however. That is really strange. Can you get it to work on a different...

Please check the Cronicle logs after a reboot, to see if systemd attempted to start it and failed, or didn't attempt it at all. Specifically this log: `/opt/cronicle/logs/Cronicle.log` And also...

Hmm, I don't know what else to try. What does `systemctl status cronicle` output for you?

As long as node exists in one of the standard locations like `/usr/bin/node` you should be fine.