SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Node-Red no LXC login and slow shutdown #1175

New Issue
Open
opened 2025-11-20 05:05:45 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 05:05:45 -05:00
Owner
Copy Link

Originally created by @m4ll4m on GitHub (May 27, 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.

nach #4627 kann ich es "installieren".
Die Node Red Web GUI ist erreichbar, bis ich den pve install shell schließe.
Beim öffnen der LXC Shell werde ich nach User und Passwort gefragt, die ich nicht kenne. Das Debain Node-Red LXC hat autologin.
Nach Reboot kommt kein Login Promt mehr, nur der weiße Cursor Block auf schwarzem Hintergrund.
Ab da an dauert das Herunterfahren nur dieses laufenden LXC über 3 Minuten.

🔄 Steps to reproduce the issue.

After #4627 i'm able to "install".
Node Red Web Gui is reachable until I close the install shell.
LXC Login Promt ask for User and Password, I did not know. (The Debain LXC has autologin)
After reebot no login promt, just white cursor on black screen.
From then on, LXC Shutdown needs 3 Minutes (only running this one LXC)

❌ Paste the full error output (if available).

✔️ 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

🖼️ Additional context (optional).

No response

Originally created by @m4ll4m on GitHub (May 27, 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. nach #4627 kann ich es "installieren". Die Node Red Web GUI ist erreichbar, bis ich den pve install shell schließe. Beim öffnen der LXC Shell werde ich nach User und Passwort gefragt, die ich nicht kenne. Das Debain Node-Red LXC hat autologin. Nach Reboot kommt kein Login Promt mehr, nur der weiße Cursor Block auf schwarzem Hintergrund. Ab da an dauert das Herunterfahren nur dieses laufenden LXC über 3 Minuten. ### 🔄 Steps to reproduce the issue. After #4627 i'm able to "install". Node Red Web Gui is reachable until I close the install shell. LXC Login Promt ask for User and Password, I did not know. (The Debain LXC has autologin) After reebot no login promt, just white cursor on black screen. From then on, LXC Shutdown needs 3 Minutes (only running this one LXC) ### ❌ Paste the full error output (if available). ✔️ 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 ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:05:45 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1175
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?