Skip to content

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

Open
@iCankat

Description

@iCankat

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions