Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration(peer) is disabled after restart #481

Open
alirezaalavi87 opened this issue Nov 12, 2024 · 3 comments
Open

Configuration(peer) is disabled after restart #481

alirezaalavi87 opened this issue Nov 12, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@alirezaalavi87
Copy link

Describe The Problem
After each reboot of system, all configurations are disabled. This is an issue because if my server get restarted when I'm offsite, I can't connect to the VPN anymore and overall, I should start my wanted peers everytime.

Expected behavior
Remember which peers are enabled and which are disabled and start the enabled ones every time automatically.

OS Information:

  • OS: debian bookworm
  • WGDashboard: v4.1.0
@alirezaalavi87 alirezaalavi87 added the bug Something isn't working label Nov 12, 2024
@donaldzou
Copy link
Owner

Hi, you can do that by going to "Settings" > "WireGuard Configuration Settings" > "Toggle When Start Up", and check whichever you want turn on when WGDashboard run :)

@alirezaalavi87
Copy link
Author

alirezaalavi87 commented Nov 12, 2024

Thank you. I didn't realize the setting page had different tabs.

But this can be better: it always starts them. If it could remember their state and restore it would be much better.

if I'm not wrong the current behavior is equal to sudo systemctl enable wg-quick@wg0

@donaldzou
Copy link
Owner

Thank you. I didn't realize the setting page had different tabs.

But this can be better: it always starts them. If it could remember their state and restore it would be much better.

if I'm not wrong the current behavior is equal to sudo systemctl enable wg-quick@wg0

No problem!

Kind of.. as WGDashboard not replying on system service. What it does is it store a list of configuration name in wg-dashboard.ini, and everytime it startup, it will check for that list and see which is not tuned on and turn it on with wg-quick up wg0, wg-quick up wg1... and so on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants