3 dots after 6.4 upgrade - and wrong node.js

We are on Ubuntu 22.04.3 LTS on DigitalOcean, and used a SNAP install originally, and it was working great for a long time. But the chat server started having issues with RocketChat around 6.4.x, where we just saw the 3 dots upon trying to login (transferring from the primary wordpress website to the dnr chat server for login). I found many others having this issue, in this forum.

It sounds like version 6.4.3 had the problem, and 6.4.4 works for some, but 6.4.5 causes the problem again? And apparently with snap, every time the server restarts, it attempts an upgrade, so we go right to 6.4.5 upon a restart.

It seems to be relating to the SiteURL being changed by RocketChat back to defaults. Once I used the command below, and restarted, then I was able to get logged in:

sudo snap set rocketchat-server siteurl=https://dnrchat.dnrstudios.com/

But above doesn’t work for everyone, so who knows.

Right now the site is functioning, but I also noticed that it’s not using the correct Node.JS of 14.21.3. Mine is using 14.21.2 - as per what it says under Workspace > Deployment:

Deployment ID
Apps Engine Version
Node Version
Database Migration
303 (November 11, 2023 2:12 PM)
5.0.15 / wiredTiger (oplog Enabled)
Commit Details
HEAD: (xxxxdeleted-on-post)
Branch: HEAD

I tried upgrading to the correct node.js by following “Option 3” on this page - and installing nvm to manage node.js:

But after I clearly updated and ran: nvm install v14.21.3, then ran: nvm list, it shows me I’m running 14.21.3:

→ v14.21.3
default → v14.21.3
iojs → N/A (default)
unstable → N/A (default)
node → stable (-> v14.21.3) (default)
stable → 14.21 (-> v14.21.3) (default)
lts/* → lts/iron (-> N/A)
lts/argon → v4.9.1 (-> N/A)
lts/boron → v6.17.1 (-> N/A)
lts/carbon → v8.17.0 (-> N/A)
lts/dubnium → v10.24.1 (-> N/A)
lts/erbium → v12.22.12 (-> N/A)
lts/fermium → v14.21.3
lts/gallium → v16.20.2 (-> N/A)
lts/hydrogen → v18.18.2 (-> N/A)
lts/iron → v20.9.0 (-> N/A)

But then after doing a reboot of the server, then again confirming that the correct 14.21.3 is loaded, when I then launch rocketchat > workspace > deployment - it STILL shows me 14.21.2 is running?

So maybe I need to do something specific with snap, to get this updated?