[Solved] EasyRSA 3 build-ca error

xlepws

Hello, I'm trying to create a VPN server on a Win10 machine..I can successfully enter the EasyRSA 3 Shell, do the init-pki, then I get an error during the build-ca phase:

EasyRSA Shell
# ./easyrsa init-pki

Note: using Easy-RSA configuration from: ./vars

init-pki complete; you may now create a CA or requests.
Your newly created PKI dir is: c:/Program Files/OpenVPN/EasyRSA-3.0.1/pki


EasyRSA Shell
# ./easyrsa build-ca

Note: using Easy-RSA configuration from: ./vars
./easyrsa[1215]: mktemp: not found
./easyrsa[1215]: mktemp: not found
Loading 'screen' into random state - done
Generating a 2048 bit RSA private key
..................+++
..................................................+++
writing new private key to ''
Invalid argument
3868:error:02001000:system library:fopen:system library:bss_file.c:398:fopen('','wb')
3868:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:400:

Easy-RSA error:

Failed to build the CA

What can that be? I have absolutely no clue on how to proceed :?

Thank you!

Traffic

xlepws wroteYour newly created PKI dir is: c:/Program Files/OpenVPN/EasyRSA-3.0.1/pki

Are you sure you have write access to this directory ?

xlepws

Hi, I suppose "I" have write access to the folder. I mean, I launched

c:\Program Files\OpenVPN\EasyRSA-3.0.1>bin\sh.exe bin\easyrsa-shell-init.sh

through an Admin Command Prompt, and it (the easyrsa shell) was able to create the "pki" folder..why shouldn't it be able to write in it?

I also tried disabling inheritance to EasyRSA-3.0.1 folder and giving every user the "full-control" permissions and pushing them down to subfolders..but nothing changes, the error is still the same :cry:

Any suggestion?

Traffic

Looks like you have encountered this bug:
https://github.com/OpenVPN/easy-rsa/issues/84

I recommend you download v3.0.0-rc2
https://github.com/OpenVPN/easy-rsa/releases/tag/v3.0.0-rc2

Also:
https://forums.openvpn.net/topic19629.html

xlepws

bang on 😉

What I had done was to copy the "missing" \bin files from 3.0.0-rc2 to 3.0.1, then proceed. But somehow 8-) this wasn't the way to go.
Just using the full 3.0.0-rc2 folder did the trick!

Thank you!

Traffic

Thanks for letting us know the solution 8-)