• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

WireGuard Package install error (2.5.2 RC)

Scheduled Pinned Locked Moved WireGuard
8 Posts 3 Posters 1.4k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R
    Risfold
    last edited by Jul 6, 2021, 11:41 PM

    I was attempting to install the package using the GUI on the 2.5.2 RC and ran into the below error. I am running this install virtually as a test environment. I was unable to find additional info or reports of this error on the forum or github. Has anyone else seen this as well? Is there any recommendation for a fix?

    I am running 2.5.2.r.20210629.1350, attempting to install 0.1.3_1, however, I have seen this also on earlier versions of the RC and package as well.

    d28fcb17-e45b-410c-a2b5-0c72c8afd117-image.png

    Error received:

    Installing pfSense-pkg-WireGuard... 
    Updating pfSense-core repository catalogue...
    pfSense-core repository is up to date.
    Updating pfSense repository catalogue...
    pfSense repository is up to date.
    All repositories are up to date.
    Checking integrity... done (0 conflicting)
    The following 1 package(s) will be affected (of 0 checked):
    
    New packages to be INSTALLED:
    	pfSense-pkg-WireGuard: 0.1.3_1 [pfSense]
    
    Number of packages to be installed: 1
    [1/1] Installing pfSense-pkg-WireGuard-0.1.3_1...
    [1/1] Extracting pfSense-pkg-WireGuard-0.1.3_1: ....
    pkg-static: Fail to create /usr/local/www/wg/js:Not a directory
    [1/1] Extracting pfSense-pkg-WireGuard-0.1.3_1... done
    Failed
    

    cd728b15-4823-4908-9c47-13141ea4acc6-image.png

    1 Reply Last reply Reply Quote 0
    • K
      kalledk
      last edited by Jul 7, 2021, 10:04 AM

      My guess is that mkdir is not called with -p and therefore fails if the wg folders doesn't exists.

      Possible patch that broke it

      Either add

      ${MKDIR} ${STAGEDIR}${PREFIX}/www/wg
      

      or change it

      ${MKDIR} -p ${STAGEDIR}${PREFIX}/www/wg/js
      

      But that is just my guess

      R 1 Reply Last reply Jul 7, 2021, 10:54 PM Reply Quote 0
      • R
        Risfold @kalledk
        last edited by Jul 7, 2021, 10:54 PM

        @kalledk Thanks for finding that! 1.1.1 was the earlier version I had issues with as well.

        I found this code in the package developer's repository as well. I will submit a an issue there.

        ...Though... I just saw that 2.5.2 final was released today. I will upgrade that first and test.

        R 1 Reply Last reply Jul 7, 2021, 11:12 PM Reply Quote 0
        • R
          Risfold @Risfold
          last edited by Jul 7, 2021, 11:12 PM

          @risfold said in WireGuard Package install error (2.5.2 RC):

          I just saw that 2.5.2 final was released today. I will upgrade that first and test.

          Confirmed the issues is still present for me on 2.5.2 RELEASE.

          Issue posted to Github here: https://github.com/theonemcdonald/pfSense-pkg-WireGuard/issues/139

          C 1 Reply Last reply Jul 8, 2021, 1:29 AM Reply Quote 0
          • C
            cmcdonald Netgate Developer @Risfold
            last edited by Jul 8, 2021, 1:29 AM

            @risfold looks like a newline issue. {MKDIR} macro is equivalent to mkdir -p already, so that isn't the issue. Will get it fixed in a snap

            Need help fast? https://www.netgate.com/support

            R 2 Replies Last reply Jul 8, 2021, 1:34 AM Reply Quote 1
            • R
              Risfold @cmcdonald
              last edited by Jul 8, 2021, 1:34 AM

              @theonemcdonald said in WireGuard Package install error (2.5.2 RC):

              {MKDIR} macro is equivalent to mkdir -p already, so that isn't the issue.

              Interesting, thank you for looking into this.

              Will get it fixed in a snap

              I'm sure that you will! Thanks for all your work on the project!

              1 Reply Last reply Reply Quote 0
              • R
                Risfold @cmcdonald
                last edited by Jul 9, 2021, 5:01 PM

                @theonemcdonald I haven't see reports of others having this issue, especially now that the package is available in the RELEASE channel. Any idea why I would have this issue?

                I haven't been able to troubleshoot much, luckily it seems like I have some sort of edge case.

                1 Reply Last reply Reply Quote 0
                • R
                  Risfold
                  last edited by Jul 12, 2021, 1:35 AM

                  Thanks to Tigger2014 on github, I dicovered some how a directory for the package was a file on my system. After renaming the file, I was able to successfully install the package. Issue resolve on my end. Thank you!

                  1 Reply Last reply Reply Quote 0
                  8 out of 8
                  • First post
                    8/8
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                    This community forum collects and processes your personal information.
                    consent.not_received