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.@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 -
@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.
-
@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 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. -
@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. -
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.
-
It seems nodejs is incorrect on the server. Can you run
cloudron-support --troubleshooton the server? It will tell you if the node version is correct or not. -
I'm starting to think giving Dokploy a spin may be worth it. Sounds more complicated than Cloudron, but then Cloudron is unstable.
This is either the third or fourth time I've lost my entire Nextcloud. It's just not worth the hassle with Cloudron.
That said, if you have any insights given my reply, please let me know. It seems to me this is unlikely to be rectified. If that's the case I'd prefer to just take the hit now rather than spend days troubleshooting to no avail.
-
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.
@scooke I appreciate the honesty. I probably should reach out to Hostinger. Unfortunately, I think paid help is outside the question.
My problem. Well, I suppose if Dokploy or the regular Nextcloud image fails as well, then I'll just let my sub lapse.
It's either something I'm doing or it's Hostinger. Maybe I just don't belong anywhere near a VPS...
-
Not sure how this is related to Nextcloud, as all apps run within their own sandbox and are not related do nodejs versions on the host. Maybe to come back to the nodejs problem, did you run those node commands within an app container or the host system?
-
@scooke I appreciate the honesty. I probably should reach out to Hostinger. Unfortunately, I think paid help is outside the question.
My problem. Well, I suppose if Dokploy or the regular Nextcloud image fails as well, then I'll just let my sub lapse.
It's either something I'm doing or it's Hostinger. Maybe I just don't belong anywhere near a VPS...
@SunDevil I'll keep sharing... I've tried Nextcloud on several different platforms, including JUST Nextcloud. It ALWAYS conks out on me. Always. So, my 2 cents, you'll have the same issue on Dokploy.
EDIT: Have you even checked out Dokploy??? I just watched their intro video. They install their software on your VPS from their servers! What?? Sorry, I'm not letting some third party have that access to my data. You create your ssh key on their system!!! You have to create a db separate from your app!!! Good luck keeping track of all those deets. Holy smokes, the number of steps needed to get this thing running is exactly why most of us have come to Cloudron. This Dokploy is so at the opposite spectrum of Cloudron. I can't imagine anyone thinking it will be "better".
-
J joseph has marked this topic as solved on
