starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 13 Packages Projects Releases 10 Wiki Activity

Alpine Node-Red #992

New Issue
Closed
opened 2026-02-04 22:26:39 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-04 22:26:39 +03:00
Owner
Copy Link

Originally created by @m4ll4m on GitHub (May 21, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

alpine-node-red

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/alpine-node-red.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Alpine

📝 Provide a clear and concise description of the issue.

script fails and no autologin / login incorrect

🔄 Steps to reproduce the issue.

just run script

❌ Paste the full error output (if available).

✔️ Created Node-RED User

added 278 packages in 21s

50 packages are looking for funding
run npm fund for details
✔️ Installed Node-RED
Creating Node-RED Service * service nodered added to runlevel default
✔️ Created Node-RED Service
Starting Node-RED * Caching service dependencies ... [ ok ]

  • Starting nodered ...
  • start-stop-daemon: /usr/bin/node-red does not exist
  • Failed to start nodered [ !! ]
  • ERROR: nodered failed to start

[ERROR] in line 52: exit code 1: while executing command $STD service nodered start

/dev/fd/63: line 73: SPINNER_PID: unbound variable

🖼️ Additional context (optional).

No response

Originally created by @m4ll4m on GitHub (May 21, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? alpine-node-red ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/alpine-node-red.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Alpine ### 📝 Provide a clear and concise description of the issue. script fails and no autologin / login incorrect ### 🔄 Steps to reproduce the issue. just run script ### ❌ Paste the full error output (if available). ✔️ Created Node-RED User added 278 packages in 21s 50 packages are looking for funding run `npm fund` for details ✔️ Installed Node-RED Creating Node-RED Service * service nodered added to runlevel default ✔️ Created Node-RED Service Starting Node-RED * Caching service dependencies ... [ ok ] * Starting nodered ... * start-stop-daemon: /usr/bin/node-red does not exist * Failed to start nodered [ !! ] * ERROR: nodered failed to start [ERROR] in line 52: exit code 1: while executing command $STD service nodered start /dev/fd/63: line 73: SPINNER_PID: unbound variable ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 22:26:39 +03:00
OVERLORD commented 2026-02-04 22:26:48 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (May 21, 2025):

done with #4628

@MickLesk commented on GitHub (May 21, 2025): done with #4628
OVERLORD commented 2026-02-04 22:26:54 +03:00
Author
Owner
Copy Link

@m4ll4m commented on GitHub (May 21, 2025):

Script work for installation, the web address is reachable, but no shell is accessible (no login promt, just blinking cursor) and lxc cannot be shut down.

@m4ll4m commented on GitHub (May 21, 2025): Script work for installation, the web address is reachable, but no shell is accessible (no login promt, just blinking cursor) and lxc cannot be shut down.
OVERLORD commented 2026-02-04 22:26:57 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (May 21, 2025):

?

@MickLesk commented on GitHub (May 21, 2025): ?
OVERLORD commented 2026-02-04 22:27:00 +03:00
Author
Owner
Copy Link

@m4ll4m commented on GitHub (May 22, 2025):

✔️ Created Node-RED User
npm warn deprecated multer@1.4.5-lts.1: Multer 1.x is impacted by a number of vulnerabilities, which have been patched in 2.x. You should upgrade to the latest 2.x version.

added 278 packages in 22s

50 packages are looking for funding
run npm fund for details
✔️ Installed Node-RED
✔️ Created /home/nodered
Creating Node-RED Service * service nodered added to runlevel default
✔️ Created Node-RED Service
Starting Node-RED * Caching service dependencies ... [ ok ]

  • Starting nodered ...
    22 May 08:36:41 - [info]

Welcome to Node-RED

22 May 08:36:41 - [info] Node-RED version: v4.0.9
22 May 08:36:41 - [info] Node.js version: v22.13.1
22 May 08:36:41 - [info] Linux 6.8.12-10-pve x64 LE
22 May 08:36:41 - [info] Loading palette nodes
22 May 08:36:41 - [info] Settings file : /home/nodered/.node-red/settings.js
22 May 08:36:41 - [info] Context store : 'default' [module=memory]
22 May 08:36:41 - [info] User directory : /home/nodered/.node-red
22 May 08:36:41 - [warn] Projects disabled : editorTheme.projects.enabled=false
22 May 08:36:41 - [info] Flows file : /home/nodered/.node-red/flows.json
22 May 08:36:41 - [info] Creating new flow file
22 May 08:36:41 - [warn]

Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.

22 May 08:36:41 - [info] Server now running at http://127.0.0.1:1880/
22 May 08:36:41 - [warn] Encrypted credentials not found
22 May 08:36:41 - [info] Starting flows
22 May 08:36:41 - [info] Started flows
^C * nodered: caught SIGINT, aborting

[ERROR] in line 58: exit code 1: while executing command $STD service nodered start

  • start-stop-daemon: caught SIGINT, aborting

Node Red Web Gui is reachable until close the install shell.
LXC Login Promt ask for User and Password.
After reebot no login promt, just blinking cursor.
From then on, no more shutdown possible.

@m4ll4m commented on GitHub (May 22, 2025): ✔️ Created Node-RED User npm warn deprecated multer@1.4.5-lts.1: Multer 1.x is impacted by a number of vulnerabilities, which have been patched in 2.x. You should upgrade to the latest 2.x version. added 278 packages in 22s 50 packages are looking for funding run `npm fund` for details ✔️ Installed Node-RED ✔️ Created /home/nodered Creating Node-RED Service * service nodered added to runlevel default ✔️ Created Node-RED Service Starting Node-RED * Caching service dependencies ... [ ok ] * Starting nodered ... 22 May 08:36:41 - [info] Welcome to Node-RED =================== 22 May 08:36:41 - [info] Node-RED version: v4.0.9 22 May 08:36:41 - [info] Node.js version: v22.13.1 22 May 08:36:41 - [info] Linux 6.8.12-10-pve x64 LE 22 May 08:36:41 - [info] Loading palette nodes 22 May 08:36:41 - [info] Settings file : /home/nodered/.node-red/settings.js 22 May 08:36:41 - [info] Context store : 'default' [module=memory] 22 May 08:36:41 - [info] User directory : /home/nodered/.node-red 22 May 08:36:41 - [warn] Projects disabled : editorTheme.projects.enabled=false 22 May 08:36:41 - [info] Flows file : /home/nodered/.node-red/flows.json 22 May 08:36:41 - [info] Creating new flow file 22 May 08:36:41 - [warn] --------------------------------------------------------------------- Your flow credentials file is encrypted using a system-generated key. If the system-generated key is lost for any reason, your credentials file will not be recoverable, you will have to delete it and re-enter your credentials. You should set your own key using the 'credentialSecret' option in your settings file. Node-RED will then re-encrypt your credentials file using your chosen key the next time you deploy a change. --------------------------------------------------------------------- 22 May 08:36:41 - [info] Server now running at http://127.0.0.1:1880/ 22 May 08:36:41 - [warn] Encrypted credentials not found 22 May 08:36:41 - [info] Starting flows 22 May 08:36:41 - [info] Started flows ^C * nodered: caught SIGINT, aborting [ERROR] in line 58: exit code 1: while executing command $STD service nodered start * start-stop-daemon: caught SIGINT, aborting Node Red Web Gui is reachable until close the install shell. LXC Login Promt ask for User and Password. After reebot no login promt, just blinking cursor. From then on, no more shutdown possible.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#992
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?