box service keeps restarting, SyntaxError: Unexpected token '.'
-
@SunDevil that is interesting indeed. I wonder how that is possible given that yellowtent is actually a disabled yser (you cannot do
su - yellowtent). Cloudron has also never used that specific version of node, so I am not sure where it's coming from.Can you debug further with
sudo -u yellowtent which nodeetc and remove that node? Maybeapt remove nodejs? The system node /usr/bin/node should be a symlink to /usr/local/node-20.18.0/bin/node .sudo -u yellowtent bashwill give you a bash with yellowtent user and then you can check where that node is coming from as well. -
@SunDevil said in box service keeps restarting, SyntaxError: Unexpected token '.':
learned my lesson about running apt upgrade long ago, so I have no idea how that's possible.
Sounds like your snapshots are all using whatever borked-up state the system was at when it was made. So, of course any restores to these snapshots are going to continue to not work. If you can indeed reinstall fresh, do that. I'm not familiar with how Hostinger offers its VPSes, but those extra node versions, Docker, etc., all got installed "somehow". If it isn't Hostinger...
-
@scooke Of course you're right. The only conclusion I can come up with is that simply adding the Docker PPA results in an
apt updateANDapt upgrade. The update is visible, but there's no indication it's runningapt upgrade.Node is more complicated. I'll double check, but I don't recall installing fnm or anything. I may have to reach out to Hostinger about these issues.
-
@girish I'm even more confused. To the best of my knowledge, I haven't messed with the Node version.
It's using
/usr/bin/node, which oddly enough seems to be the only package not symlinked. The first command you gave me shows Node v20.18.0. The second command shows Node v12.22.9. The latter appears to be a default package included with Ubuntu 24.04.1 LTS.Full Data:
Listing of /usr/bin, scoped to
grep nodeListing of installed packages, scoped to
grep node -
@SunDevil Perhaps Hostinger provides "non-fresh" servers to its customers with a variety of programs already installed to save you time. Normally a fresh server would not come with Docker, node, etc., at all. Cloudron needs the fresh server because it needs to follow it's own install script. Sounds like Hostinger has maybe gotten the two "fresh" settings overlapped.
-
@SunDevil it seems there is a whole bunch of node modules installed via apt on the system. Cloudron doesn't install these. Cloudron installs the node version it wants under /usr/local/node-20.18.0/ and then creates a symlink. Something like this:
apt remove nodejs ln -sf /usr/local/node-20.18.0/bin/node /usr/bin/nodeAfter this, node should be 20.18.0 . Then, you can
systemctl restart boxand it will start with the correct node. -
I checked out Hostinger... its Cloudron image can be installed AFTER the initial server is provisioned. One reason for the errors @SunDevil is having is if they installed the Cloudron image after provisioning the server, and the server had been "managed" prior to the Cloudron installation. I don't think asking them to run normal troubleshooting is going to work here with their experience level. I recommend @SunDevil get more direct professional help to try to undo whatever was previously installed, even if that is paid-help from the Cloudron team. I don't think they'll be better off just going the Nextcloud route as, if the same conditions persist/repeat, Nextcloud is also going to start acting wonky and good luck getting THAT solved! Paying for ssh-access-level-help is your best way forward and let a techy person clear out all that extraneous stuff. Good luck.
