• Dr. Wesker@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    5 months ago

    Worth noting, it doesn’t like long .conf filenames. If you get an error that the file can’t be found when importing, try shortening the filename.

      • Dr. Wesker@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        5
        ·
        edit-2
        5 months ago

        I think it expects you to use a standardized device name structure such as wg0 however it doesn’t exactly (or rather clearly) enforce this, and it tries to name the new device whatever the file is named during the import step.

        This problem is somewhat compounded by VPN providers, who often generate some long filename when you export a WG config.