BUG - Latest Update Has These issues with meshcentral when updating Meshcentral Server

[LPJon]

Update.sh Script output at end of update for Meshcentral. Looks Like a problem with NPM
Default documentation installation using Debian 10
TacticalRMM Update from 0.14.6 -->0.14.7

Running migrations:
  No migrations to apply.
  Your models in app(s): 'agents', 'core' have changes that are not yet reflected in a migration, and so won't be applied.
  Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.
All web tokens have been deleted!

33 static files copied to '/rmm/api/tacticalrmm/static'.
Reloading NATs configuration...
NATs configuration reloaded
Chocos saved to db
Checking if installer user has been created...
Installer user already exists
Creating configuration for nats-api...
Configuration for nats-api created successfully
Running post update tasks
Adding new community script: Winget - Install, Uninstall and Upgrade Software
Adding new community script: Check IIS Certs for Expiry
Post update tasks finished
Turning off redis aof
OK
OK
Starting nats service
Starting nats-api service
Starting rmm service
Starting daphne service
Starting celery service
Starting celerybeat service
Starting nginx service
Updating meshcentral from 1.0.60 to 1.0.72
npm ERR! code ERR_SSL_DECRYPTION_FAILED_OR_BAD_RECORD_MAC
npm ERR! 139957186127808:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac:../deps/openssl/openssl/ssl/record/ssl3_record.c:677:
npm ERR! 

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/managementrmm/.npm/_logs/2022-08-23T07_27_47_140Z-debug-0.log
Update finished!

This is after a force update for a second time from the first update which failed to install .

Running migrations:
  No migrations to apply.
  Your models in app(s): 'agents', 'core' have changes that are not yet reflected in a migration, and so won't be applied.
  Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.
All web tokens have been deleted!

33 static files copied to '/rmm/api/tacticalrmm/static'.
Reloading NATs configuration...
NATs configuration reloaded
Chocos saved to db
Checking if installer user has been created...
Installer user already exists
Creating configuration for nats-api...
Configuration for nats-api created successfully
Running post update tasks
Post update tasks finished
Turning off redis aof
OK
OK
Starting nats service
Starting nats-api service
Starting rmm service
Starting daphne service
Starting celery service
Starting celerybeat service
Starting nginx service
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module './package.json'
Require stack:
- /meshcentral/node_modules/meshcentral/[eval]
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at [eval]:1:1
    at Script.runInThisContext (node:vm:129:12)
    at Object.runInThisContext (node:vm:305:38)
    at node:internal/process/execution:76:19
    at [eval]-wrapper:6:22
    at evalScript (node:internal/process/execution:75:60) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/meshcentral/node_modules/meshcentral/[eval]' ]
}
Updating meshcentral from  to 1.0.72

added 171 packages, and audited 172 packages in 25s

11 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
Update finished!

[wh1te909]

I just tested on Debian 10 and not able to reproduce. Try googling this error npm ERR! code ERR_SSL_DECRYPTION_FAILED_OR_BAD_RECORD_MAC and try to fix

[LPJon]

@wh1te909 I did as you suggested and googled the error and came up with this article which seems to handle the issue. Simply running the two commands and updating NPM seems to work. My suggestion is that you integrate this update for NPM into your update script as you explicitly state in your documentation to NOT do ANYTHING independently of that script.

The commands are:
sudo npm config set ca=""
sudo npm install npm -g --ca=null

Please note that I ran those commands as the configured user for TacticalRMM service and NOT root.

[LPJon]

@wh1te909 Okay, so after the last update relating to this issue, I ran the commands above. This created a file named .npmrc in the home directory of the tacticalrmm service user with contents of ca=. This would set the CA (Certificate Authority) value to null for NPM. With the latest update (0.14.8) I have to remove that file before the update or it would fail to get all of the NPM packages required for the update. I think originally what happened was that somehow the NPM website URL was having certificate issues and setting that setting to null allowed the update to continue. Anyways, this issue appears to have resolved itself. Those are always the best ones.