[GH-ISSUE #4958] Error in script nextcloudpi.sh #1062

Closed
opened 2026-02-26 12:47:35 +03:00 by kerem · 2 comments
Owner

Originally created by @shahab-cl on GitHub (Jun 4, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/4958

Have you read and understood the above guidelines?

yes

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

ct/nextcloudpi.sh

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📝 Provide a clear and concise description of the issue.

This is a folowup to #4817

I dont think this is related to DNS. Here is the output when I select "Advanced setting" from the menu.

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

_   __          __  ________                ______  _ 
/ | / /__ _ / // / / __ / / __ ()
/ |/ / _ | |// __/ / / / __ / / / / __ / // / /
/ /| / __/> </ // // / // / // / // / __/ /
// |/_//||_/_//_/_,/_,// //

🧩 Using Advanced Settings on node pve
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
🔐 Root Password: ********
🆔 Container ID: 101
🏠 Hostname: nextcloudpi
💾 Disk Size: 8 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🌉 Bridge: vmbr0
📡 IP Address: dhcp
🌐 Gateway IP Address: Default
📡 APT-Cacher IP Address: Default
🚫 Disable IPv6: no
⚙️ Interface MTU Size: Default
🔍 DNS Search Domain: Host
📡 DNS Server IP Address: Host
🏷️ Vlan: Default
📡 Tags: community-script;cloud
🔑 Root SSH Access: no
🗂️ Enable FUSE Support: no
🔍 Verbose Mode: no
🚀 Creating a NextCloudPi LXC using the above advanced settings
✔️ Using local for Template Storage.
✔️ Using local-lvm for Container Storage.
✔️ Updated LXC Template List
✔️ LXC Template is ready to use.
✔️ LXC Container 101 was successfully created.
✔️ Started LXC Container
✔️ Set up Container OS
✔️ Network Connected: 2600:4040:2883:da00:be24:11ff:fe89:d8c
✖️ IPv4 Internet Not Connected
✔️ IPv6 Internet Connected
✖️ DNS Lookup Failure
✔️ Updated Container OS
⠸/dev/stdin: line 72: curl: command not found

[ERROR] in line 51: exit code 0: while executing command "$@" > /dev/null 2>&1
/dev/stdin: line 84: post_update_to_api: command not found
/dev/stdin: line 218: pop_var_context: head of shell_variables not a function context
/dev/stdin: line 14: pop_var_context: head of shell_variables not a function context
/dev/fd/63: line 74: SPINNER_PID: unbound variable
root@pve:~#

And Here is the output when I select "Default Settings"

_   __          __  ________                ______  _ 
/ | / /__ _ / // / / __ / / __ ()
/ |/ / _ | |// __/ / / / __ / / / / __ / // / /
/ /| / __/> </ // // / // / // / // / __/ /
// |/_//||_/_//_/_,/_,// //

⚙️ Using Default Settings on node pve
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
💾 Disk Size: 8 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🆔 Container ID: 101
🚀 Creating a NextCloudPi LXC using the above default settings

✔️ Using local for Template Storage.
✔️ Using local-lvm for Container Storage.
✔️ Updated LXC Template List
✔️ LXC Template is ready to use.
✔️ LXC Container 101 was successfully created.
✔️ Started LXC Container
✔️ Set up Container OS
✔️ Network Connected: 192.168.1.191 2600:4040:2883:da00:be24:11ff:fe12:88fc
✔️ IPv4 Internet Connected
✔️ IPv6 Internet Connected
✔️ DNS Resolved github.com to 140.82.113.4
✔️ Updated Container OS
✔️ Core dependencies installed
✔️ Installed NextCloudPi
✔️ Customized Container
✔️ Cleaned
✔️ Completed Successfully!

🚀 NextCloudPi setup has been successfully initialized!
💡 Access it using the following URL:
🌐 http://192.168.1.191/
root@pve:~#

This is installed on the same PVE server. Only difference is the Default vs advanced settings.

🔄 Steps to reproduce the issue.

Tried the script with default settings (no user input) and it works as expected. And then tried it with "Advanced setting" and the script fails. The same server is used for both cases so there is no issue with DNS on the "Default settings"

Paste the full error output (if available).

`/ | / /__ _ / // / / __ / / __ ()
/ |/ / _ | |// __/ / / / __ / / / / __ / // / /
/ /| / __/> </ // // / // / // / // / __/ /
// |///||////,/,// //

🧩 Using Advanced Settings on node pve
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
🔐 Root Password: ********
🆔 Container ID: 101
🏠 Hostname: nextcloudpi
💾 Disk Size: 8 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🌉 Bridge: vmbr0
📡 IP Address: dhcp
🌐 Gateway IP Address: Default
📡 APT-Cacher IP Address: Default
🚫 Disable IPv6: no
⚙️ Interface MTU Size: Default
🔍 DNS Search Domain: Host
📡 DNS Server IP Address: Host
🏷️ Vlan: Default
📡 Tags: community-script;cloud
🔑 Root SSH Access: no
🗂️ Enable FUSE Support: no
🔍 Verbose Mode: no
🚀 Creating a NextCloudPi LXC using the above advanced settings
✔️ Using local for Template Storage.
✔️ Using local-lvm for Container Storage.
✔️ Updated LXC Template List
✔️ LXC Template is ready to use.
✔️ LXC Container 101 was successfully created.
✔️ Started LXC Container
✔️ Set up Container OS
✔️ Network Connected: 2600:4040:2883:da00:be24:11ff:fe89:d8c
✖️ IPv4 Internet Not Connected
✔️ IPv6 Internet Connected
✖️ DNS Lookup Failure
✔️ Updated Container OS
⠸/dev/stdin: line 72: curl: command not found

[ERROR] in line 51: exit code 0: while executing command "$@" > /dev/null 2>&1
/dev/stdin: line 84: post_update_to_api: command not found
/dev/stdin: line 218: pop_var_context: head of shell_variables not a function context
/dev/stdin: line 14: pop_var_context: head of shell_variables not a function context
/dev/fd/63: line 74: SPINNER_PID: unbound variable
root@pve:~#`

🖼️ Additional context (optional).

No response

Originally created by @shahab-cl on GitHub (Jun 4, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/4958 ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? ct/nextcloudpi.sh ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nextcloudpi.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📝 Provide a clear and concise description of the issue. This is a folowup to #4817 I dont think this is related to DNS. Here is the output when I select "Advanced setting" from the menu. bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nextcloudpi.sh)" ``` _ __ __ ________ ______ _ / | / /__ _ / // / / __ / / __ () / |/ / _ | |// __/ / / / __ / / / / __ / // / / / /| / __/> </ // // / // / // / // / __/ / // |/_//||_/_//_/_,/_,// // 🧩 Using Advanced Settings on node pve 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 🔐 Root Password: ******** 🆔 Container ID: 101 🏠 Hostname: nextcloudpi 💾 Disk Size: 8 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🌉 Bridge: vmbr0 📡 IP Address: dhcp 🌐 Gateway IP Address: Default 📡 APT-Cacher IP Address: Default 🚫 Disable IPv6: no ⚙️ Interface MTU Size: Default 🔍 DNS Search Domain: Host 📡 DNS Server IP Address: Host 🏷️ Vlan: Default 📡 Tags: community-script;cloud 🔑 Root SSH Access: no 🗂️ Enable FUSE Support: no 🔍 Verbose Mode: no 🚀 Creating a NextCloudPi LXC using the above advanced settings ✔️ Using local for Template Storage. ✔️ Using local-lvm for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Template is ready to use. ✔️ LXC Container 101 was successfully created. ✔️ Started LXC Container ✔️ Set up Container OS ✔️ Network Connected: 2600:4040:2883:da00:be24:11ff:fe89:d8c ✖️ IPv4 Internet Not Connected ✔️ IPv6 Internet Connected ✖️ DNS Lookup Failure ✔️ Updated Container OS ⠸/dev/stdin: line 72: curl: command not found [ERROR] in line 51: exit code 0: while executing command "$@" > /dev/null 2>&1 /dev/stdin: line 84: post_update_to_api: command not found /dev/stdin: line 218: pop_var_context: head of shell_variables not a function context /dev/stdin: line 14: pop_var_context: head of shell_variables not a function context /dev/fd/63: line 74: SPINNER_PID: unbound variable root@pve:~# ``` And Here is the output when I select "Default Settings" ``` _ __ __ ________ ______ _ / | / /__ _ / // / / __ / / __ () / |/ / _ | |// __/ / / / __ / / / / __ / // / / / /| / __/> </ // // / // / // / // / __/ / // |/_//||_/_//_/_,/_,// // ⚙️ Using Default Settings on node pve 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 💾 Disk Size: 8 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🆔 Container ID: 101 🚀 Creating a NextCloudPi LXC using the above default settings ✔️ Using local for Template Storage. ✔️ Using local-lvm for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Template is ready to use. ✔️ LXC Container 101 was successfully created. ✔️ Started LXC Container ✔️ Set up Container OS ✔️ Network Connected: 192.168.1.191 2600:4040:2883:da00:be24:11ff:fe12:88fc ✔️ IPv4 Internet Connected ✔️ IPv6 Internet Connected ✔️ DNS Resolved github.com to 140.82.113.4 ✔️ Updated Container OS ✔️ Core dependencies installed ✔️ Installed NextCloudPi ✔️ Customized Container ✔️ Cleaned ✔️ Completed Successfully! 🚀 NextCloudPi setup has been successfully initialized! 💡 Access it using the following URL: 🌐 http://192.168.1.191/ root@pve:~# ``` This is installed on the same PVE server. Only difference is the Default vs advanced settings. ### 🔄 Steps to reproduce the issue. Tried the script with default settings (no user input) and it works as expected. And then tried it with "Advanced setting" and the script fails. The same server is used for both cases so there is no issue with DNS on the "Default settings" ### ❌ Paste the full error output (if available). `/ | / /__ _ / // / / __ / / __ () / |/ / _ | |// __/ / / / __ / / / / __ / // / / / /| / __/> </ // // / // / // / // / __/ / // |/_//||_/_//_/_,/_,// // 🧩 Using Advanced Settings on node pve 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 🔐 Root Password: ******** 🆔 Container ID: 101 🏠 Hostname: nextcloudpi 💾 Disk Size: 8 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🌉 Bridge: vmbr0 📡 IP Address: dhcp 🌐 Gateway IP Address: Default 📡 APT-Cacher IP Address: Default 🚫 Disable IPv6: no ⚙️ Interface MTU Size: Default 🔍 DNS Search Domain: Host 📡 DNS Server IP Address: Host 🏷️ Vlan: Default 📡 Tags: community-script;cloud 🔑 Root SSH Access: no 🗂️ Enable FUSE Support: no 🔍 Verbose Mode: no 🚀 Creating a NextCloudPi LXC using the above advanced settings ✔️ Using local for Template Storage. ✔️ Using local-lvm for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Template is ready to use. ✔️ LXC Container 101 was successfully created. ✔️ Started LXC Container ✔️ Set up Container OS ✔️ Network Connected: 2600:4040:2883:da00:be24:11ff:fe89:d8c ✖️ IPv4 Internet Not Connected ✔️ IPv6 Internet Connected ✖️ DNS Lookup Failure ✔️ Updated Container OS ⠸/dev/stdin: line 72: curl: command not found [ERROR] in line 51: exit code 0: while executing command "$@" > /dev/null 2>&1 /dev/stdin: line 84: post_update_to_api: command not found /dev/stdin: line 218: pop_var_context: head of shell_variables not a function context /dev/stdin: line 14: pop_var_context: head of shell_variables not a function context /dev/fd/63: line 74: SPINNER_PID: unbound variable root@pve:~#` ### 🖼️ Additional context (optional). _No response_
kerem 2026-02-26 12:47:35 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@MickLesk commented on GitHub (Jun 4, 2025):

You got massive Network Errors.

First: you cannot Install curl (lol)

Second: you cannot reach anything in GitHub.

Reboot your node.

<!-- gh-comment-id:2938294551 --> @MickLesk commented on GitHub (Jun 4, 2025): You got massive Network Errors. First: you cannot Install curl (lol) Second: you cannot reach anything in GitHub. Reboot your node.
Author
Owner

@shahab-cl commented on GitHub (Jun 4, 2025):

Why would advances settings always fail but default work every time. The
runs I provided were done minutes after the other.

Shahab Khan
Cubicle Logic
Main: 571-636-1200
Cell: +1-703-861-6397
Email: @.***

Bringing people and technology together

PLEASE CONSIDER OUR ENVIRONMENT BEFORE PRINTING

On Tue, Jun 3, 2025, 11:37 PM CanbiZ @.***> wrote:

Closed #4958 https://github.com/community-scripts/ProxmoxVE/issues/4958
as not planned.


Reply to this email directly, view it on GitHub
https://github.com/community-scripts/ProxmoxVE/issues/4958#event-17972663482,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE64ZTNT2KI47XIOUGLRPL3BZSYZAVCNFSM6AAAAAB6RLNBPSVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJXHE3TENRWGM2DQMQ
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

<!-- gh-comment-id:2939662615 --> @shahab-cl commented on GitHub (Jun 4, 2025): Why would advances settings always fail but default work every time. The runs I provided were done minutes after the other. Shahab Khan Cubicle Logic Main: 571-636-1200 Cell: +1-703-861-6397 Email: ***@***.*** Bringing people and technology together ----------------------------- PLEASE CONSIDER OUR ENVIRONMENT BEFORE PRINTING On Tue, Jun 3, 2025, 11:37 PM CanbiZ ***@***.***> wrote: > Closed #4958 <https://github.com/community-scripts/ProxmoxVE/issues/4958> > as not planned. > > — > Reply to this email directly, view it on GitHub > <https://github.com/community-scripts/ProxmoxVE/issues/4958#event-17972663482>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAE64ZTNT2KI47XIOUGLRPL3BZSYZAVCNFSM6AAAAAB6RLNBPSVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJXHE3TENRWGM2DQMQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.*** > com> >
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#1062
No description provided.