pull down to refresh
node.js is needed for the lightning.pub dashboard and some other things.
Try again to run the installation script.
What OS and hardware architecture? I'll try to reproduce
reply
I just confirmed it's 4GB Ubuntu 24.04.3 LTS Dell XPS 13/9360
reply
Interesting, I may ask you to fetch a log to help figure out where it's failing, will confirm the logging first though on my end
reply
Sure.
reply
Can you try running this? it's a version with an added log
note there's the letter t before deploy (it's in a test branch)
wget -qO- https://tdeploy.lightning.pub | bashafter that runs, if it fails again, run this... it should output a log detailing what happened
cat /tmp/lightning_pub_install.logreply
after `wget -qO- https://tdeploy.lightning.pub | bash'
Script version 0.2.2
2025-11-03 23:02:19 Detected OS: Linux
2025-11-03 23:02:19 Detected ARCH: amd64
2025-11-03 23:02:19 Installing LND...
2025-11-03 23:02:20 LND is already up-to-date. No action needed.
2025-11-03 23:02:21 Checking for Node.js...
2025-11-03 23:02:25 Node.js is not installed. Installing the LTS version...
2025-11-03 23:02:25 Failed to install Node.js.
2025-11-03 23:02:25 ERROR: Failed to install Node.js
2025-11-03 23:02:25 Exiting with status 1
2025-11-03 23:02:25 Cleaning up temporary files...
After I ran
cat /tmp/lightning_pub_install.logI got this:
$ cat /tmp/lightning_pub_install.log cat: /tmp/lightning_pub_install.log: No such file or directoryreply
afterwget -qO- https://tdeploy.lightning.pub | bash
even from a trusted domain, piping from wget or curl into bash directly is a bad habit. I strongly recommend saving the script locally, which gives you the chance to review its steps at your leisure before running them, rather than reconstructing the steps it has already taken in retrospect.
reply
my bad, it pulled from the wrong branch
try that one more time, the script should now say 0.2.3 at the top confirming it's the latest...
reply
It does say 0.2.3, but same result:
Script version 0.2.3 2025-11-03 23:18:04 Detected OS: Linux 2025-11-03 23:18:04 Detected ARCH: amd64 2025-11-03 23:18:04 Installing LND... 2025-11-03 23:18:05 LND is already up-to-date. No action needed. 2025-11-03 23:18:05 Checking for Node.js... 2025-11-03 23:18:11 Node.js is not installed. Installing the LTS version... 2025-11-03 23:18:11 Failed to install Node.js 2025-11-03 23:18:11 ERROR: Failed to install Node.js 2025-11-03 23:18:11 Exiting with status 1 2025-11-03 23:18:11 Cleaning up temporary files... siggy@siggy-XPS-13-9360:~$ cat /tmp/lightning_pub_install.log cat: /tmp/lightning_pub_install.log: No such file or directory
wget -qO- https://tdeploy.lightning.pub | bash
Please don't encourage anyone to develop the habit of piping directly from curl/wget into bash!
Downloading a temporary copy gives the opportunity to look over and possibly customize for your system before running it, and also makes it easier to resume from partway if it failed and needed intervention.
reply
Then we are going bsck to square one where the new user is lost in complex commands.
A single line comnand is much easier for any user.
If you really want to help, take the software and make it a flatpak. We have to make it easier not more complicated.
reply
It's probably worth to define which kind of user are we talking about, because not everyone operate cli and not everyone is comfortable running flatpaks without knowing what's inside.
These are two different scenarios, and LNpub is probably at an early stage still. Feedback like this help the product grow, offering various options for different type of users could be really helpful.
I realise there's a tradeoff, and you're definitely correct about the usability.
Maybe the better approach is a verbal warning, separate from the copy-pasteable command, along the lines of "this command installs a program, don't run it on critical systems" and encouraging that people have separate hardware for critical systems. That's definitely twice as much maintenance, although it is much easier for someone to reason about security considerations when the sensitive system is a physically separate computer.
deleted by author
reply
Thanks, looks like the node installer isn't providing detail
Try this if you would, it's not the pub installation itself but just the nodejs piece, it should be more verbose... and if it just works for some reason the next run of the script will install pub since the dependency will have been met
wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash && export NVM_DIR="$HOME/.nvm" && [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" && nvm install --ltsreply
deleted by author
reply
I also install it on old PC from 2008, with a slow CPU and 4GB RAM.
The only was that was slow in syncing and using it. Took 90% of resources, just LN Pub running.
Was just testing to see how low I can go with PC specs.
reply
Failed to install Node.js.java script isn't needed anyway, correct?
First of all, "javascript" is one word; it's usually possible to distinguish from context between the two unrelated programming languages "java" and "javascript", although the ambiguity should be avoided if possible.
Secondly, Node is used for writing server-side programs in Javascript. Although JS originated as a language for scripts that ran within the client web browser, it is also common as a server-side language. "Node" is the name of the most popular engine for writing server programs in javascript, and you might also see mention of "NPM" or its invocation in scripts; this is "Node Package Manager".
Failed to install Node.js.