SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-24 14:53:58 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Config-File: ENABLE_FUSE: unbound variable" #1171

New Issue
Closed
opened 2025-11-20 05:05:38 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:05:38 -05:00
Owner
Copy Link

Originally created by @Gregor-zbjk on GitHub (May 26, 2025).

Originally assigned to: @michelroegl-brunner on GitHub.

✅ Have you read and understood the above guidelines?

yes

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

Matterbridge

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/matterbridge.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.

Today I discovered that the install script for Matterbridge will fail if you use the config file option, because the section "activate fuse" is not automatically questioned after the automatic config of the "default" options of the installer script.

error:
dev/fd/63: line 1076: ENABLE_FUSE: unbound variable

🔄 Steps to reproduce the issue.

  1. Paste bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/matterbridge.sh)" into Proxmox CLI
  2. Select 4 use config file
  3. start install
  4. error dev/fd/63: line 1076: ENABLE_FUSE: unbound variable

❌ Paste the full error output (if available).

x = REDACTED

/ |/ /___ / // /____ / / ()/ / ____
/ /|/ / __ / __/ __/ _ \/ ___/ __ \/ ___/ / __ / __ / _
/ / / / // / // // / / / // / / / / // / // / __/
// //_,/_/__/_// /.// //_,/__, /__/
/____/
💡 Using Config File on node pve
💡 Using config File: /opt/community-scripts/.settings
🆔 Container ID: 113
📦 Container Type: Unprivileged
🔐 Root Password: *********************
🏠 Hostname: matterbridge
💾 Disk Size: 4 GB
🧠 CPU Cores: 1
🛠️ RAM Size: 1024 MiB
🌉 Bridge: vmbr0
✔️ Using free IP Address: xx.xx.xx.52/24
🌐 Gateway IP Address: xx.xx.xx.1
📡 APT-CACHER IP Address: xxxxxx.proxy
🚫 Disable IPv6: No
⚙️ Interface MTU Size: Default
🔍 DNS Search Domain: Host
📡 DNS Server IP Address: Host
🏷️ Vlan: 100
📡 Tags: ProductionUser-LAN;matter;smarthome
🔑 Root SSH Access: no
🔍 Verbose Mode: no
🚀 Creating a Matterbridge LXC using the above settings
/dev/fd/63: line 1076: ENABLE_FUSE: unbound variable

🖼️ Additional context (optional).

No response

Originally created by @Gregor-zbjk on GitHub (May 26, 2025). Originally assigned to: @michelroegl-brunner on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Matterbridge ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/matterbridge.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📝 Provide a clear and concise description of the issue. Today I discovered that the install script for Matterbridge will fail if you use the `config file` option, because the section "activate fuse" is not automatically questioned after the automatic config of the "default" options of the installer script. error: `dev/fd/63: line 1076: ENABLE_FUSE: unbound variable` ### 🔄 Steps to reproduce the issue. 1. Paste `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/matterbridge.sh)"` into Proxmox CLI 2. Select `4 use config file` 3. start install 4. error `dev/fd/63: line 1076: ENABLE_FUSE: unbound variable` ### ❌ Paste the full error output (if available). **x = REDACTED** __ ___ __ __ __ _ __ / |/ /___ _/ /_/ /____ _____/ /_ _____(_)___/ /___ ____ / /|_/ / __ `/ __/ __/ _ \/ ___/ __ \/ ___/ / __ / __ `/ _ \ / / / / /_/ / /_/ /_/ __/ / / /_/ / / / / /_/ / /_/ / __/ /_/ /_/\__,_/\__/\__/\___/_/ /_.___/_/ /_/\__,_/\__, /\___/ /____/ 💡 Using Config File on node pve 💡 Using config File: /opt/community-scripts/.settings 🆔 Container ID: 113 📦 Container Type: Unprivileged 🔐 Root Password: ********************* 🏠 Hostname: matterbridge 💾 Disk Size: 4 GB 🧠 CPU Cores: 1 🛠️ RAM Size: 1024 MiB 🌉 Bridge: vmbr0 ✔️ Using free IP Address: xx.xx.xx.52/24 🌐 Gateway IP Address: xx.xx.xx.1 📡 APT-CACHER IP Address: xxxxxx.proxy 🚫 Disable IPv6: No ⚙️ Interface MTU Size: Default 🔍 DNS Search Domain: Host 📡 DNS Server IP Address: Host 🏷️ Vlan: 100 📡 Tags: ProductionUser-LAN;matter;smarthome 🔑 Root SSH Access: no 🔍 Verbose Mode: no 🚀 Creating a Matterbridge LXC using the above settings /dev/fd/63: line 1076: ENABLE_FUSE: unbound variable ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:05:38 -05:00
saavagebueno commented 2025-11-20 05:05:39 -05:00
Author
Owner
Copy Link

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

@michelroegl-brunner need to add for config File?

@MickLesk commented on GitHub (May 26, 2025): @michelroegl-brunner need to add for config File?
saavagebueno commented 2025-11-20 05:05:39 -05:00
Author
Owner
Copy Link

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

Maybe as Bugfix: add in your config File:
ENABLE_FUSE=no

@MickLesk commented on GitHub (May 26, 2025): Maybe as Bugfix: add in your config File: ENABLE_FUSE=no
saavagebueno commented 2025-11-20 05:05:39 -05:00
Author
Owner
Copy Link

@Gregor-zbjk commented on GitHub (May 26, 2025):

@MickLesk I have tried you recommended Bugfix.. But the error persists

@Gregor-zbjk commented on GitHub (May 26, 2025): @MickLesk I have tried you recommended Bugfix.. But the error persists
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#1171
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?