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

wireguard LXC with WGDashboard cannot update #1873

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

Originally created by @nalabrie on GitHub (Sep 8, 2025).

✅ Have you read and understood the above guidelines?

yes

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

WireGuard

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve)

📝 Provide a clear and concise description of the issue.

After installing the WireGuard LXC and answering yes to installing the WGDashboard, running update in the container will fail.

🔄 Steps to reproduce the issue.

  1. Install wireguard LXC from helper script
  2. Allow the script to install the WGDashboard
  3. Open a terminal in the container
  4. Run update and choose verbose output
  5. Watch it fail :(

❌ Paste the full error output (if available).

 _       ___                                      __
| |     / (_)_______  ____ ___  ______ __________/ /
| | /| / / / ___/ _ \/ __ `/ / / / __ `/ ___/ __  / 
| |/ |/ / / /  /  __/ /_/ / /_/ / /_/ / /  / /_/ /  
|__/|__/_/_/   \___/\__, /\__,_/\__,_/_/   \__,_/   
                   /____/                           

Hit:1 http://security.debian.org bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
=================================================================================
+          <WGDashboard> by Donald Zou - https://github.com/donaldzou           +
=================================================================================
[WGDashboard] OS: debian
[WGDashboard] ✅ Python is installed
[WGDashboard] ✅ Found compatible version of Python. Will be using Python 3.11.2 to install WGDashboard.
[WGDashboard] 💿 Installing Python Virtual Environment
[WGDashboard] ✅ Python Virtual Environment is installed
[WGDashboard] ✅ Python Package Manager (PIP) is installed
[WGDashboard] Are you sure you want to update to the v4.2.5? (Y/N): y
[WGDashboard] Shutting down WGDashboard
[WGDashboard] Stopping WGDashboard w/ Gunicorn on PID 41785
[WGDashboard] Stopping WGDashboard w/ Gunicorn on PID 42575
[WGDashboard] WGDashboard is stopped.
[WGDashboard] Downloading v4.2.5 from GitHub..../wgd.sh: line 547: git: command not found
./wgd.sh: line 547: git: command not found
chmod: cannot access './wgd.sh': No such file or directory
sudo: ./wgd.sh: command not found
[WGDashboard] Update completed!
---------------------------------------------------------------------------------
environment: line 37: ./wgd.sh: No such file or directory

[ERROR] in line 37: exit code 0: while executing command ./wgd.sh start

🖼️ Additional context (optional).

After the above failure occurs, running update again produces this output:

 _       ___                                      __
| |     / (_)_______  ____ ___  ______ __________/ /
| | /| / / / ___/ _ \/ __ `/ / / / __ `/ ___/ __  / 
| |/ |/ / / /  /  __/ /_/ / /_/ / /_/ / /  / /_/ /  
|__/|__/_/_/   \___/\__, /\__,_/\__,_/_/   \__,_/   
                   /____/                           

Hit:1 http://security.debian.org bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
environment: line 36: ./wgd.sh: No such file or directory

[ERROR] in line 36: exit code 0: while executing command ./wgd.sh update

It no longer asks Are you sure you want to update to the v4.2.5? (Y/N), it just goes straight to failing. I tested this on two containers and both have the same issue.

Originally created by @nalabrie on GitHub (Sep 8, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? WireGuard ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/wireguard.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve) ### 📝 Provide a clear and concise description of the issue. After installing the WireGuard LXC and answering yes to installing the WGDashboard, running `update` in the container will fail. ### 🔄 Steps to reproduce the issue. 1. Install wireguard LXC from helper script 2. Allow the script to install the WGDashboard 3. Open a terminal in the container 4. Run `update` and choose verbose output 5. Watch it fail :( ### ❌ Paste the full error output (if available). ``` _ ___ __ | | / (_)_______ ____ ___ ______ __________/ / | | /| / / / ___/ _ \/ __ `/ / / / __ `/ ___/ __ / | |/ |/ / / / / __/ /_/ / /_/ / /_/ / / / /_/ / |__/|__/_/_/ \___/\__, /\__,_/\__,_/_/ \__,_/ /____/ Hit:1 http://security.debian.org bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ================================================================================= + <WGDashboard> by Donald Zou - https://github.com/donaldzou + ================================================================================= [WGDashboard] OS: debian [WGDashboard] ✅ Python is installed [WGDashboard] ✅ Found compatible version of Python. Will be using Python 3.11.2 to install WGDashboard. [WGDashboard] 💿 Installing Python Virtual Environment [WGDashboard] ✅ Python Virtual Environment is installed [WGDashboard] ✅ Python Package Manager (PIP) is installed [WGDashboard] Are you sure you want to update to the v4.2.5? (Y/N): y [WGDashboard] Shutting down WGDashboard [WGDashboard] Stopping WGDashboard w/ Gunicorn on PID 41785 [WGDashboard] Stopping WGDashboard w/ Gunicorn on PID 42575 [WGDashboard] WGDashboard is stopped. [WGDashboard] Downloading v4.2.5 from GitHub..../wgd.sh: line 547: git: command not found ./wgd.sh: line 547: git: command not found chmod: cannot access './wgd.sh': No such file or directory sudo: ./wgd.sh: command not found [WGDashboard] Update completed! --------------------------------------------------------------------------------- environment: line 37: ./wgd.sh: No such file or directory [ERROR] in line 37: exit code 0: while executing command ./wgd.sh start ``` ### 🖼️ Additional context (optional). After the above failure occurs, running `update` again produces this output: ``` _ ___ __ | | / (_)_______ ____ ___ ______ __________/ / | | /| / / / ___/ _ \/ __ `/ / / / __ `/ ___/ __ / | |/ |/ / / / / __/ /_/ / /_/ / /_/ / / / /_/ / |__/|__/_/_/ \___/\__, /\__,_/\__,_/_/ \__,_/ /____/ Hit:1 http://security.debian.org bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. environment: line 36: ./wgd.sh: No such file or directory [ERROR] in line 36: exit code 0: while executing command ./wgd.sh update ``` It no longer asks `Are you sure you want to update to the v4.2.5? (Y/N)`, it just goes straight to failing. I tested this on two containers and both have the same issue.
saavagebueno added the bug label 2025-11-20 05:19:00 -05:00
saavagebueno commented 2025-11-20 05:19:01 -05:00
Author
Owner
Copy Link

@nalabrie commented on GitHub (Sep 8, 2025):

Installing git before the first invocation of update does not help:

=================================================================================
+          <WGDashboard> by Donald Zou - https://github.com/donaldzou           +
=================================================================================
[WGDashboard] OS: debian
[WGDashboard] ✅ Python is installed
[WGDashboard] ✅ Found compatible version of Python. Will be using Python 3.11.2 to install WGDashboard.
[WGDashboard] 💿 Installing Python Virtual Environment
[WGDashboard] ✅ Python Virtual Environment is installed
[WGDashboard] ✅ Python Package Manager (PIP) is installed
[WGDashboard] Are you sure you want to update to the v4.2.5? (Y/N): y
[WGDashboard] Shutting down WGDashboard
[WGDashboard] Stopping WGDashboard w/ Gunicorn on PID 41750
[WGDashboard] Stopping WGDashboard w/ Gunicorn on PID 42602
[WGDashboard] WGDashboard is stopped.
[WGDashboard] Downloading v4.2.5 from GitHub...fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
chmod: cannot access './wgd.sh': No such file or directory
sudo: ./wgd.sh: command not found
[WGDashboard] Update completed!
---------------------------------------------------------------------------------
environment: line 37: ./wgd.sh: No such file or directory

[ERROR] in line 37: exit code 0: while executing command ./wgd.sh start

Also might be worth mentioning that when the update fails the entire dashboard goes offline and the web UI cannot be accessed.

@nalabrie commented on GitHub (Sep 8, 2025): Installing git before the first invocation of `update` does not help: ``` ================================================================================= + <WGDashboard> by Donald Zou - https://github.com/donaldzou + ================================================================================= [WGDashboard] OS: debian [WGDashboard] ✅ Python is installed [WGDashboard] ✅ Found compatible version of Python. Will be using Python 3.11.2 to install WGDashboard. [WGDashboard] 💿 Installing Python Virtual Environment [WGDashboard] ✅ Python Virtual Environment is installed [WGDashboard] ✅ Python Package Manager (PIP) is installed [WGDashboard] Are you sure you want to update to the v4.2.5? (Y/N): y [WGDashboard] Shutting down WGDashboard [WGDashboard] Stopping WGDashboard w/ Gunicorn on PID 41750 [WGDashboard] Stopping WGDashboard w/ Gunicorn on PID 42602 [WGDashboard] WGDashboard is stopped. [WGDashboard] Downloading v4.2.5 from GitHub...fatal: not a git repository (or any of the parent directories): .git fatal: not a git repository (or any of the parent directories): .git chmod: cannot access './wgd.sh': No such file or directory sudo: ./wgd.sh: command not found [WGDashboard] Update completed! --------------------------------------------------------------------------------- environment: line 37: ./wgd.sh: No such file or directory [ERROR] in line 37: exit code 0: while executing command ./wgd.sh start ``` Also might be worth mentioning that when the update fails the entire dashboard goes offline and the web UI cannot be accessed.
saavagebueno commented 2025-11-20 05:19:01 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 9, 2025):

@donaldzou can you take a short Look? Why do you need an fix .git folder?

@MickLesk commented on GitHub (Sep 9, 2025): @donaldzou can you take a short Look? Why do you need an fix .git folder?
saavagebueno commented 2025-11-20 05:19:01 -05:00
Author
Owner
Copy Link

@donaldzou commented on GitHub (Sep 9, 2025):

Hmmmmmmmmm so basically WGDasboard relies on Git to do release management... does the community script download directly and not doing a git clone?

@donaldzou commented on GitHub (Sep 9, 2025): Hmmmmmmmmm so basically WGDasboard relies on Git to do release management... does the community script download directly and not doing a git clone?
saavagebueno commented 2025-11-20 05:19:01 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 9, 2025):

Hmmmmmmmmm so basically WGDasboard relies on Git to do release management... does the community script download directly and not doing a git clone?

yes since over 1 month. We crawl the tarball with the function "fetch_and_deploy_gh_release "wgdashboard" "donaldzou/WGDashboard" "tarball" "latest" "/etc/wgdashboard""
Or do you think its better - to use the git clone instead of this? We removed git at several projects

@MickLesk commented on GitHub (Sep 9, 2025): > Hmmmmmmmmm so basically WGDasboard relies on Git to do release management... does the community script download directly and not doing a git clone? yes since over 1 month. We crawl the tarball with the function "fetch_and_deploy_gh_release "wgdashboard" "donaldzou/WGDashboard" "tarball" "latest" "/etc/wgdashboard"" Or do you think its better - to use the git clone instead of this? We removed git at several projects
saavagebueno commented 2025-11-20 05:19:01 -05:00
Author
Owner
Copy Link

@donaldzou commented on GitHub (Sep 9, 2025):

Ah I see, yes I think the best to use git so we don’t need to do extra cases for Community Script — less chance to break haha

Best,

Donald Zou

From: CanbiZ @.>
Sent: Tuesday, September 9, 2025 2:30:35 PM
To: community-scripts/ProxmoxVE @.>
Cc: Donald Zou @.>; Mention @.>
Subject: Re: [community-scripts/ProxmoxVE] wireguard LXC with WGDashboard cannot update (Issue #7496)

[https://avatars.githubusercontent.com/u/47820557?s=20&v=4]MickLesk left a comment (community-scripts/ProxmoxVE#7496)https://github.com/community-scripts/ProxmoxVE/issues/7496#issuecomment-3269073314

Hmmmmmmmmm so basically WGDasboard relies on Git to do release management... does the community script download directly and not doing a git clone?

yes since over 1 month. We crawl the tarball with the function "fetch_and_deploy_gh_release "wgdashboard" "donaldzou/WGDashboard" "tarball" "latest" "/etc/wgdashboard""
Or do you think its better - to use the git clone instead of this? We removed git at several projects

—
Reply to this email directly, view it on GitHubhttps://github.com/community-scripts/ProxmoxVE/issues/7496#issuecomment-3269073314, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGARNUK4PWDQWGZ73OLTC5L3RZXYXAVCNFSM6AAAAACF7BIT4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENRZGA3TGMZRGQ.
You are receiving this because you were mentioned.Message ID: @.***>

@donaldzou commented on GitHub (Sep 9, 2025): Ah I see, yes I think the best to use git so we don’t need to do extra cases for Community Script — less chance to break haha Best, Donald Zou ________________________________ From: CanbiZ ***@***.***> Sent: Tuesday, September 9, 2025 2:30:35 PM To: community-scripts/ProxmoxVE ***@***.***> Cc: Donald Zou ***@***.***>; Mention ***@***.***> Subject: Re: [community-scripts/ProxmoxVE] wireguard LXC with WGDashboard cannot update (Issue #7496) [https://avatars.githubusercontent.com/u/47820557?s=20&v=4]MickLesk left a comment (community-scripts/ProxmoxVE#7496)<https://github.com/community-scripts/ProxmoxVE/issues/7496#issuecomment-3269073314> Hmmmmmmmmm so basically WGDasboard relies on Git to do release management... does the community script download directly and not doing a git clone? yes since over 1 month. We crawl the tarball with the function "fetch_and_deploy_gh_release "wgdashboard" "donaldzou/WGDashboard" "tarball" "latest" "/etc/wgdashboard"" Or do you think its better - to use the git clone instead of this? We removed git at several projects — Reply to this email directly, view it on GitHub<https://github.com/community-scripts/ProxmoxVE/issues/7496#issuecomment-3269073314>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGARNUK4PWDQWGZ73OLTC5L3RZXYXAVCNFSM6AAAAACF7BIT4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENRZGA3TGMZRGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>
saavagebueno commented 2025-11-20 05:19:02 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 9, 2025):

@tremor021

@MickLesk commented on GitHub (Sep 9, 2025): @tremor021
saavagebueno commented 2025-11-20 05:19:02 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Sep 9, 2025):

@donaldzou you use github api for version checking, if i'm reading wgd.sh correctly, same as we do. We store the version tag inside ~/.AppName which would be ~/.wgdashboard in this case and we use that for our own version checking for all of update scripts.

Your only check would be to compare the version you fetch with gh api with the version we store. If that file exists, that would mean WGDashboard is installed inside LXC, so it would basically be just one IF block.

Anyway, i can revert to the way it worked before, with git and stuff, just saying its not a point of possible breakage since you check same stuff as we do.

PR incoming

@tremor021 commented on GitHub (Sep 9, 2025): @donaldzou you use github api for version checking, if i'm reading `wgd.sh` correctly, same as we do. We store the version tag inside `~/.AppName` which would be `~/.wgdashboard` in this case and we use that for our own version checking for all of update scripts. Your only check would be to compare the version you fetch with gh api with the version we store. If that file exists, that would mean WGDashboard is installed inside LXC, so it would basically be just one IF block. Anyway, i can revert to the way it worked before, with git and stuff, just saying its not a point of possible breakage since you check same stuff as we do. PR incoming
saavagebueno commented 2025-11-20 05:19:02 -05:00
Author
Owner
Copy Link

@donaldzou commented on GitHub (Sep 9, 2025):

Hi @tremor021,

Yes I do use the GitHub API to check for new version, the issue here is I use git pull --new version to actually updating the code, which is why it broke for @nalabrie since the community script tarballed the code.

Best,
Donald

@donaldzou commented on GitHub (Sep 9, 2025): Hi @tremor021, Yes I do use the GitHub API to check for new version, the issue here is I use `git pull --new version` to actually updating the code, which is why it broke for @nalabrie since the community script tarballed the code. Best, Donald
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#1873
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?