ngoduykhanh / wireguard-ui

Wireguard web interface
MIT License
4.04k stars 502 forks source link

QR Code Regeneration Required for Configuration Updates #619

Open Bojo67 opened 1 month ago

Bojo67 commented 1 month ago

When using WireGuard UI to manage VPN client configurations, any updates to the AllowedIPs field require regenerating a new QR code for clients. This process is cumbersome and can be impractical, especially when dealing with multiple clients or frequent configuration changes.

Issue: The current workflow requires that every time you modify the AllowedIPs for a WireGuard client, a new QR code must be generated and re-scanned by the client device to apply these changes. This approach poses several challenges:

Inconvenience: Manually regenerating and distributing new QR codes each time a configuration change is made can be time-consuming and error-prone.

Scalability: For environments with many clients, this process becomes increasingly complex and difficult to manage effectively.

User Experience: The need to constantly re-scan QR codes affects the user experience, especially for less technical users who may find this process confusing.

Proposed Solution: To enhance usability and streamline configuration management, consider the following improvements:

Support for Dynamic Configuration Updates: Allow clients to dynamically receive and apply configuration changes without the need for a new QR code. This could involve implementing a mechanism to push configuration updates directly to clients.

Enhanced Client Configuration Management: Implement features that enable manual updates to AllowedIPs directly within the client application without requiring QR code regeneration.

Centralized Management: Introduce a centralized management system or API that can handle configuration changes across multiple clients efficiently.

Additional Context: Currently, clients retain the old configuration until a new QR code is scanned, which means changes to AllowedIPs are not reflected in the client’s connection settings. Improving this process would greatly enhance the flexibility and ease of managing WireGuard VPN configurations.

Thank you for considering this issue. Any suggestions or solutions to address this workflow challenge would be greatly appreciated.

Computroniks commented 1 week ago

Just looking at this, this appears out of scope for this project. Configuration of clients is handled by the WireGuard app on the clients device, which is totally separate to this project. To achieve what you are after a custom client application would likely be required. WireGuard UI is simply for managing the configuration on the server, not for updating clients and there is no mechanism for the client application to automatically receive updates.