[GH-ISSUE #10953] Peanut LXC // latest versione does not work #2345

Closed
opened 2026-02-26 12:52:07 +03:00 by kerem · 4 comments
Owner

Originally created by @papperone on GitHub (Jan 19, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10953

Originally assigned to: @vhsdream on GitHub.

Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

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

Peanut (LXC)

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

9.1.2 (cluster of 4 nodes)

📝 Provide a clear and concise description of the issue.

deploying Peanut LXC containers seems to complete successfully but tool cannot be accessed with http://IP:3000
I have Peanut running since long time, current container is working with version 5.17.0
I tried to upgrade the existing container and ended up with the issue, the link I used to use to access the web GUI does not work (unreachable page) then I created a new container with the script but same issue, all ok, no error at the end but web page does not show up

🔄 Steps to reproduce the issue.

use the script to upgrade an existing container with older version or to create a new container

Paste the full error output (if available).

no error on the console but the web GUI at http://IP:3000 is not reacheable, with older version (which I restored of course) all is working

🖼️ Additional context (optional).

not sure which log you may need, but issue seems easily replicable on my setup, I tried to upgrade the existing container or deploy a new container, even on different nodes of my cluster, all with the very same results

Originally created by @papperone on GitHub (Jan 19, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10953 Originally assigned to: @vhsdream on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? Peanut (LXC) ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/peanut.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 9.1.2 (cluster of 4 nodes) ### 📝 Provide a clear and concise description of the issue. deploying Peanut LXC containers seems to complete successfully but tool cannot be accessed with http://IP:3000 I have Peanut running since long time, current container is working with version 5.17.0 I tried to upgrade the existing container and ended up with the issue, the link I used to use to access the web GUI does not work (unreachable page) then I created a new container with the script but same issue, all ok, no error at the end but web page does not show up ### 🔄 Steps to reproduce the issue. use the script to upgrade an existing container with older version or to create a new container ### ❌ Paste the full error output (if available). no error on the console but the web GUI at http://IP:3000 is not reacheable, with older version (which I restored of course) all is working ### 🖼️ Additional context (optional). not sure which log you may need, but issue seems easily replicable on my setup, I tried to upgrade the existing container or deploy a new container, even on different nodes of my cluster, all with the very same results
kerem 2026-02-26 12:52:07 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@MickLesk commented on GitHub (Jan 19, 2026):

systemctl status peanut ?

<!-- gh-comment-id:3768569240 --> @MickLesk commented on GitHub (Jan 19, 2026): systemctl status peanut ?
Author
Owner

@vhsdream commented on GitHub (Jan 19, 2026):

I believe the port changed from 3000 to 8080 - check 8080 and I bet it's running.

<!-- gh-comment-id:3769004935 --> @vhsdream commented on GitHub (Jan 19, 2026): I believe the port changed from 3000 to 8080 - check 8080 and I bet it's running.
Author
Owner

@papperone commented on GitHub (Jan 20, 2026):

I believe the port changed from 3000 to 8080 - check 8080 and I bet it's running.

thanks, I see the script was updated and now at the end reports the right port 8080, yesterday it was still 3000 so I was unable to guess this changes as not mentioned anywhere!

<!-- gh-comment-id:3772790558 --> @papperone commented on GitHub (Jan 20, 2026): > I believe the port changed from 3000 to 8080 - check 8080 and I bet it's running. thanks, I see the script was updated and now at the end reports the right port 8080, yesterday it was still 3000 so I was unable to guess this changes as not mentioned anywhere!
Author
Owner

@MickLesk commented on GitHub (Jan 20, 2026):

We didn't know anything about that either. Normally, ports are not changed; that was a decision made by upstream. We are not the project owners; we only provide it for you.

<!-- gh-comment-id:3772815863 --> @MickLesk commented on GitHub (Jan 20, 2026): We didn't know anything about that either. Normally, ports are not changed; that was a decision made by upstream. We are not the project owners; we only provide it for you.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#2345
No description provided.