Cancelled Deployment = Cannot Deploy Anything - UnhandledPromiseRejectionWarning

[engagit]

I am using Strider 1.11.0 and decided to cancel a deployment that was running using the cancel button.

When I tried to re-deploy the project I had cancelled, I get a black screen with no prepare/deploy output as expected, and the cancel button is not displaying at all now.

When I try to deploy other projects by clicking the deploy button, nothing happens.

I have tried restarting strider, rebooting the server itself, and even deleting the project and re-creating it. Nothing worked.

Here is the error I am seeing in my logs when I restart strider:

2020-01-22T18:02:36.761Z strider:load-extensions   - gitlab
2020-01-22T18:02:36.761Z strider:load-extensions   - hg
2020-01-22T18:02:36.761Z strider:load-extensions Found basic plugins:
2020-01-22T18:02:36.761Z strider:load-extensions   - buildbadge
2020-01-22T18:02:36.763Z strider:load-extensions initialized static directories
2020-01-22T18:02:36.855Z strider:routes:api:config loaded config pages
2020-01-22T18:02:36.864Z strider:routes:api:config loaded account config pages
2020-01-22T18:02:36.900Z strider:routes:api:config loaded plugin status blocks
2020-01-22T18:02:36.900Z strider:load-extensions loaded plugins
2020-01-22T18:02:36.923Z - error: (node:10617) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): SyntaxError: Unexpected token ...

It stops at the unexpected token error.

Any ideas how to fix this without having to reinstall strider from scratch?

[knownasilya]

Sounds like the version of NodeJS doesn't match. It should be v10 or greater.

[engagit]

Thank you SO much, that is exactly it. The deployment that I cancelled has to change node version to install some packages, but switches back at the end of the deployment. Because I cancelled it, this did not happen, and meant Strider could not work with the current node version.

Thank you again!