starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 13 Packages Projects Releases 10 Wiki Activity

wireguard script fails when updating wgdashboard #1748

New Issue
Closed
opened 2026-02-05 02:09:21 +03:00 by OVERLORD · 13 comments
OVERLORD commented 2026-02-05 02:09:21 +03:00
Owner
Copy Link

Originally created by @samwathegreat on GitHub (Oct 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?

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

9.0.10

📝 Provide a clear and concise description of the issue.

update fails when attempting to update wgdashboard (some kind of git error)

Looks like there is a closed issue for something similar, but this is broken again

https://github.com/community-scripts/ProxmoxVE/issues/7496

🔄 Steps to reproduce the issue.

type "update" in the console of an existing, working, installation.

❌ Paste the full error output (if available).

Processing triggers for dbus (1.14.10-1~deb12u1) ...
Processing triggers for debianutils (5.7-0.5~deb12u1) ...
Processing triggers for initramfs-tools (0.142+deb12u3) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-40-rt-amd64
=================================================================================
+          <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.3.0.1? (Y/N): y
[WGDashboard] Shutting down WGDashboard
[WGDashboard] Stopping WGDashboard w/ Gunicorn on PID 377
[WGDashboard] Stopping WGDashboard w/ Gunicorn on PID 132557
[WGDashboard] WGDashboard is stopped.
[WGDashboard] Downloading v4.3.0.1 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 43: ./wgd.sh: No such file or directory

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

root@wireguard:~#

🖼️ Additional context (optional).

No response

Originally created by @samwathegreat on GitHub (Oct 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? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 9.0.10 ### 📝 Provide a clear and concise description of the issue. update fails when attempting to update wgdashboard (some kind of git error) Looks like there is a closed issue for something similar, but this is broken again https://github.com/community-scripts/ProxmoxVE/issues/7496 ### 🔄 Steps to reproduce the issue. type "update" in the console of an existing, working, installation. ### ❌ Paste the full error output (if available). ``` Processing triggers for dbus (1.14.10-1~deb12u1) ... Processing triggers for debianutils (5.7-0.5~deb12u1) ... Processing triggers for initramfs-tools (0.142+deb12u3) ... update-initramfs: Generating /boot/initrd.img-6.1.0-40-rt-amd64 ================================================================================= + <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.3.0.1? (Y/N): y [WGDashboard] Shutting down WGDashboard [WGDashboard] Stopping WGDashboard w/ Gunicorn on PID 377 [WGDashboard] Stopping WGDashboard w/ Gunicorn on PID 132557 [WGDashboard] WGDashboard is stopped. [WGDashboard] Downloading v4.3.0.1 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 43: ./wgd.sh: No such file or directory [ERROR] in line 43: exit code 0: while executing command ./wgd.sh start root@wireguard:~# ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 02:09:21 +03:00
OVERLORD commented 2026-02-05 02:09:26 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Oct 8, 2025):

how did you update? you need to use "our" update function, not the built in.
for that just type update in the lxc shell

@michelroegl-brunner commented on GitHub (Oct 8, 2025): how did you update? you need to use "our" update function, not the built in. for that just type update in the lxc shell
OVERLORD commented 2026-02-05 02:09:27 +03:00
Author
Owner
Copy Link

@samwathegreat commented on GitHub (Oct 8, 2025):

how did you update? you need to use "our" update function, not the built in. for that just type update in the lxc shell

@michelroegl-brunner Indeed. That is exactly what I did. If you check my report it says that. Unfortunately, it fails.

I'm not even sure what you mean by the "built in".

@samwathegreat commented on GitHub (Oct 8, 2025): > how did you update? you need to use "our" update function, not the built in. for that just type update in the lxc shell @michelroegl-brunner Indeed. That is exactly what I did. If you check my report it says that. Unfortunately, it fails. I'm not even sure what you mean by the "built in".
OVERLORD commented 2026-02-05 02:09:30 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Oct 8, 2025):

oh my bad, i missed that! I look into it.

@michelroegl-brunner commented on GitHub (Oct 8, 2025): oh my bad, i missed that! I look into it.
OVERLORD commented 2026-02-05 02:09:31 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Oct 8, 2025):

One qestion though, when did you install the lxc? we had a time where we did not git clone, so that might be the issue here.
@tremor021 changed some things around a month or two back

@michelroegl-brunner commented on GitHub (Oct 8, 2025): One qestion though, when did you install the lxc? we had a time where we did not git clone, so that might be the issue here. @tremor021 changed some things around a month or two back
OVERLORD commented 2026-02-05 02:09:35 +03:00
Author
Owner
Copy Link

@samwathegreat commented on GitHub (Oct 8, 2025):

Looks like back in June. Did your change break updatability of existing installs?

@samwathegreat commented on GitHub (Oct 8, 2025): Looks like back in June. Did your change break updatability of existing installs?
OVERLORD commented 2026-02-05 02:09:38 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Oct 8, 2025):

That we need to figure out.

@michelroegl-brunner commented on GitHub (Oct 8, 2025): That we need to figure out.
OVERLORD commented 2026-02-05 02:09:41 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Oct 8, 2025):

@samwathegreat So according to the devs if Wireguard we needed the way we deploy the App so the updates keep working.

Your app was sadly installed with the old method wich dose not use gut pull, we downloaded the release files manually at the time.

So yes, in fact, this is a breaking change.

Best course of action for you is to backup your configs, reinstall in a new LXC, and then restore the configs back in there.

Your current installation can not be saved or updated.

@michelroegl-brunner commented on GitHub (Oct 8, 2025): @samwathegreat So according to the devs if Wireguard we needed the way we deploy the App so the updates keep working. Your app was sadly installed with the old method wich dose not use gut pull, we downloaded the release files manually at the time. So yes, in fact, this is a breaking change. Best course of action for you is to backup your configs, reinstall in a new LXC, and then restore the configs back in there. Your current installation can not be saved or updated.
OVERLORD commented 2026-02-05 02:09:44 +03:00
Author
Owner
Copy Link

@samwathegreat commented on GitHub (Oct 8, 2025):

@michelroegl-brunner @tremor021

I followed your advice to create a new LXC with your script and restore my config.

I found a bug with this script.

When you use the DEFAULT settings, it installs on DEBIAN 13.

I couldn't figure out why my config simply would NOT work after restoring the config. Well...it turns out that there is a change in DEBIAN 13 --

The sysctl.conf file (with the line to enable IP FORWARDING) is no longer located in /etc (which is where the script puts it). It has to be in /etc/sysctl.d/sysctl.conf

So after making a new LXC with your script, IP forwarding is OFF. Because it doesn't read the file from /etc/sysctl.conf!!

The script needs adjusted so that it puts the sysctl.conf in the appropriate directory - otherwise IP forwarding simply does not work and the LXC is useless for wireguard.

That wasn't easy to figure out, but it was so simple!! All I had to do was

mv /etc/sysctl.conf /etc/sysctl.d/sysctl.conf
reboot

And all was working

This is a known issue with DEBIAN 13:

https://www.reddit.com/r/debian/comments/1moideb/ip_forwarding_after_upgrade_to_13_stopped_working/

@samwathegreat commented on GitHub (Oct 8, 2025): @michelroegl-brunner @tremor021 I followed your advice to create a new LXC with your script and restore my config. **I found a bug with this script.** When you use the DEFAULT settings, it installs on DEBIAN 13. I couldn't figure out why my config simply would NOT work after restoring the config. Well...it turns out that there is a change in DEBIAN 13 -- The sysctl.conf file (with the line to enable IP FORWARDING) is no longer located in /etc (which is where the script puts it). It has to be in /etc/sysctl.d/sysctl.conf So after making a new LXC with your script, IP forwarding is OFF. Because it doesn't read the file from /etc/sysctl.conf!! **The script needs adjusted so that it puts the sysctl.conf in the appropriate directory - otherwise IP forwarding simply does not work and the LXC is useless for wireguard.** That wasn't easy to figure out, but it was so simple!! All I had to do was ``` mv /etc/sysctl.conf /etc/sysctl.d/sysctl.conf reboot ``` And all was working This is a known issue with DEBIAN 13: https://www.reddit.com/r/debian/comments/1moideb/ip_forwarding_after_upgrade_to_13_stopped_working/
OVERLORD commented 2026-02-05 02:09:46 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 8, 2025):

@tremor021 could you do this?

@MickLesk commented on GitHub (Oct 8, 2025): @tremor021 could you do this?
OVERLORD commented 2026-02-05 02:09:51 +03:00
Author
Owner
Copy Link

@samwathegreat commented on GitHub (Oct 8, 2025):

I would suggest checking any of the scripts that have a Debian 13 option and need IP forwarding to be on by default.

@samwathegreat commented on GitHub (Oct 8, 2025): I would suggest checking any of the scripts that have a Debian 13 option and need IP forwarding to be on by default.
OVERLORD commented 2026-02-05 02:09:55 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 8, 2025):

The question is which LXC this affects, or whether I should just copy it to the core after creating it.

@MickLesk commented on GitHub (Oct 8, 2025): The question is which LXC this affects, or whether I should just copy it to the core after creating it.
OVERLORD commented 2026-02-05 02:09:59 +03:00
Author
Owner
Copy Link

@TaxiarchAnonymous commented on GitHub (Oct 8, 2025):

One qestion though, when did you install the lxc? we had a time where we did not git clone, so that might be the issue here. @tremor021 changed some things around a month or two back

Came here to see if anyone else made that connection. That was my first thought as well. It caused a slew of issues about that time. I believe it wound up being something not extracting properly. Maybe not extracting with the correct permissions.

@TaxiarchAnonymous commented on GitHub (Oct 8, 2025): > One qestion though, when did you install the lxc? we had a time where we did not git clone, so that might be the issue here. [@tremor021](https://github.com/tremor021) changed some things around a month or two back Came here to see if anyone else made that connection. That was my first thought as well. It caused a slew of issues about that time. I believe it wound up being something not extracting properly. Maybe not extracting with the correct permissions.
OVERLORD commented 2026-02-05 02:10:03 +03:00
Author
Owner
Copy Link

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

@handle-your-set no, their official install script (which also does updates) uses .git directory for version checks and management. If it fails to detect the directory or some variables inside it, it will fail the install. The dev himself instructed us to use git pull if we wanna make it work properly. This is one of the rare scripts we have in our repo that still use git pull as a mean of deploying/updating the app.

Anyway, the fix for Trixie is ready @samwathegreat, just debating with @MickLesk is i should put in a check if user has selected debian version other than 13.

@tremor021 commented on GitHub (Oct 9, 2025): @handle-your-set no, their official install script (which also does updates) uses .git directory for version checks and management. If it fails to detect the directory or some variables inside it, it will fail the install. The dev himself instructed us to use git pull if we wanna make it work properly. This is one of the rare scripts we have in our repo that still use git pull as a mean of deploying/updating the app. Anyway, the fix for Trixie is ready @samwathegreat, just debating with @MickLesk is i should put in a check if user has selected debian version other than 13.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1748
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?