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 11 Packages Projects Releases 10 Wiki Activity

Regarding WireGuard LXC #46

New Issue
Closed
opened 2026-02-04 16:22:03 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-04 16:22:03 +03:00
Owner
Copy Link

Originally created by @donaldzou on GitHub (Nov 14, 2024).

Originally assigned to: @MickLesk on GitHub.

Please verify that you have read and understood the guidelines.

Yes

A clear and concise description of the issue.

Hi @MickLesk,

My name is Donald Zou, and I'm the creator of WGDashboard.

Recently, it came to our attention that our project is being used in wireguard-install.sh, and we're happy that it has been chosen and adopted by the ProxmoxVE community!

We were wondering if it would be possible to add more guidance on https://community-scripts.github.io/ProxmoxVE/scripts?id=wireguard, as some users are mixing up WGDashboard and WireGuard and mistakenly thinking they’re the same. Additionally, it might be helpful to include a WireGuard configuration template within the guide or the installation script to simplify things for users.

Looking forward to hearing back from you.

Best,
Donald

What settings are you currently utilizing?

Default Settings

Which Linux distribution are you employing?

Ubuntu 24.04

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

No response

Originally created by @donaldzou on GitHub (Nov 14, 2024). Originally assigned to: @MickLesk on GitHub. ### Please verify that you have read and understood the guidelines. Yes ### A clear and concise description of the issue. Hi @MickLesk, My name is Donald Zou, and I'm the creator of [WGDashboard](https://github.com/donaldzou/WGDashboard). Recently, it came to our attention that our project is being used in `wireguard-install.sh`, and we're happy that it has been chosen and adopted by the ProxmoxVE community! We were wondering if it would be possible to add more guidance on https://community-scripts.github.io/ProxmoxVE/scripts?id=wireguard, as some users are mixing up WGDashboard and WireGuard and mistakenly thinking they’re the same. Additionally, it might be helpful to include a WireGuard configuration template within the guide or the installation script to simplify things for users. Looking forward to hearing back from you. Best, Donald ### What settings are you currently utilizing? Default Settings ### Which Linux distribution are you employing? Ubuntu 24.04 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. _No response_
OVERLORD added the maintenance label 2026-02-04 16:22:03 +03:00
OVERLORD commented 2026-02-04 16:22:07 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 14, 2024):

Hi Donald,

I understand what you mean, but I'm not sure what else to add to the website?
A note that WGDashboard is a management interface for existing configurations?

Feel free to give us suggestions. We can also open a “Discussion”, “Announcement” at any time by defining further steps.

Example:
https://github.com/community-scripts/ProxmoxVE/discussions/193
or
https://github.com/community-scripts/ProxmoxVE/discussions/192

later there will probably be real wiki entries, but unfortunately we are not yet ready at the current stage of the project, which is why we note all this in Discussions.

@MickLesk commented on GitHub (Nov 14, 2024): Hi Donald, I understand what you mean, but I'm not sure what else to add to the website? A note that WGDashboard is a management interface for existing configurations? Feel free to give us suggestions. We can also open a “Discussion”, “Announcement” at any time by defining further steps. Example: https://github.com/community-scripts/ProxmoxVE/discussions/193 or https://github.com/community-scripts/ProxmoxVE/discussions/192 later there will probably be real wiki entries, but unfortunately we are not yet ready at the current stage of the project, which is why we note all this in Discussions.
OVERLORD commented 2026-02-04 16:22:10 +03:00
Author
Owner
Copy Link

@donaldzou commented on GitHub (Nov 14, 2024):

Hi @MickLesk,

Thanks for the quick response.

Yes, maybe a note to tell users that WGDashboard and WireGuard is not the same, and if they encountered issues with WireGuard, they should reach out to them not us, which happened before.

We also noticed that some users who used the WireGuard LXC script don't know how to create configuration, so maybe we can propose an addition to the existing wireguard-install.sh:

...

default_config_name="wg0"
default_config="/etc/wireguard/${default_config_name}.conf"
if [ ! -f $default_config ]; then
    sudo touch default_config
    private_key=$(wg genkey)
    { 
        printf "[Interface]\n";
        printf "PrivateKey = ${private_key}\n";
        printf "Address = 10.0.0.1/24\n";
        printf "SaveConfig = true\n";
        printf "PostUp = iptables -A FORWARD -i ${default_config_name} -j ACCEPT; iptables -A FORWARD -o ${default_config_name} -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE;\n"
        printf "PostDown = iptables -D FORWARD -i ${default_config_name} -j ACCEPT; iptables -D FORWARD -o ${default_config_name} -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE;\n"
        printf "ListenPort = 51820 \n\n"
    } >> $default_config
fi

...

So when user access WGDashboard the very first time, they will see this configuration ready for them.

Let me know what you think 😄

@donaldzou commented on GitHub (Nov 14, 2024): Hi @MickLesk, Thanks for the quick response. Yes, maybe a note to tell users that WGDashboard and WireGuard is not the same, and if they encountered issues with WireGuard, they should reach out to them not us, which happened before. We also noticed that some users who used the WireGuard LXC script don't know how to create configuration, so maybe we can propose an addition to the existing `wireguard-install.sh`: ```bash ... default_config_name="wg0" default_config="/etc/wireguard/${default_config_name}.conf" if [ ! -f $default_config ]; then sudo touch default_config private_key=$(wg genkey) { printf "[Interface]\n"; printf "PrivateKey = ${private_key}\n"; printf "Address = 10.0.0.1/24\n"; printf "SaveConfig = true\n"; printf "PostUp = iptables -A FORWARD -i ${default_config_name} -j ACCEPT; iptables -A FORWARD -o ${default_config_name} -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE;\n" printf "PostDown = iptables -D FORWARD -i ${default_config_name} -j ACCEPT; iptables -D FORWARD -o ${default_config_name} -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE;\n" printf "ListenPort = 51820 \n\n" } >> $default_config fi ... ``` So when user access WGDashboard the very first time, they will see this configuration ready for them. Let me know what you think 😄
OVERLORD commented 2026-02-04 16:22:13 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 16, 2024):

@donaldzou

If you like, feel free to link our project as well. :-) This way, Proxmox users can see it too.

@MickLesk commented on GitHub (Nov 16, 2024): @donaldzou If you like, feel free to link our project as well. :-) This way, Proxmox users can see it too.
OVERLORD commented 2026-02-04 16:22:19 +03:00
Author
Owner
Copy Link

@donaldzou commented on GitHub (Nov 24, 2024):

@donaldzou

If you like, feel free to link our project as well. :-) This way, Proxmox users can see it too.

@MickLesk

Hi yes! The doc just updated with linking to community-script!

🛠 Install
📝 Requirements

@donaldzou commented on GitHub (Nov 24, 2024): > @donaldzou > > If you like, feel free to link our project as well. :-) This way, Proxmox users can see it too. @MickLesk Hi yes! The doc just updated with linking to community-script! [🛠 Install](https://donaldzou.github.io/WGDashboard-Documentation/install.html#for-proxmox-virtual-environment) [📝 Requirements](https://donaldzou.github.io/WGDashboard-Documentation/requirements.html)
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 maintenance
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#46
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?