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

"etc/wireguard/wg0.conf" file gets corrupted after reboot #10

Open
iCankat opened this issue Jan 22, 2021 · 0 comments · May be fixed by #11
Open

"etc/wireguard/wg0.conf" file gets corrupted after reboot #10

iCankat opened this issue Jan 22, 2021 · 0 comments · May be fixed by #11

Comments

@iCankat
Copy link

iCankat commented Jan 22, 2021

The QR code given in the first installation works just fine. But, let's use (create or remove) functions as get after making the necessary config settings. When we reboot after use, none of them work anymore. Because after reboot "/etc/wireguard/wg0.conf" file gets corrupted. More precisely, it gets corrupted after create and remove, but is noticed after reboot. "/wg-api/scripts/data/wg.def" does not get the necessary information from here and update itself, PublicKey and AllowedIPs remain empty. In addition, when we use the remove process, the user can still continue to use it even though they delete it from the profiles folder. "wg set $interface peer $key remove" instantly destroys this command when we run it manually in the terminal. When we use a command with "wg.sh" it breaks. It also crashes after reboot when we do create and remove with GET or use "wg.sh -a xxxx & wg.sh -d xxxx" directly. Corrupts the "wg.conf" file. Can you tell me where exactly is the problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant