• Dr. Wesker@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    30 days 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
        30 days 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.

  • bloodfart@lemmy.ml
    link
    fedilink
    arrow-up
    5
    ·
    30 days ago

    The reason wg-quick wants ten character filenames in the conf file is that it (the conf file name) is gonna be the virtual adapter name and the limit on those is ten characters.

    Some vpns are annoying and give you confs that will totally work except that they’re a whole goddamn sentence. One of those vpns is air.

    • joojmachine@lemmy.mlOP
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      29 days ago

      yeah, proton vpn is the same, this guide is what made it finally work for me personally