OpenSSL - something more useful than 256 error

[jinnicky (Bob Ewart)]

I do wish that OpenSSL would come up with something more useful than 256 error.

I had 2 net-to-net virtual nets running, but had to rebuild my firewall. Due to a change in DDNS servers, I had to re-do the certificates.

My first try after reinstalling IPfire and a backup was to remove the x509 which seemed to remove the connections. It complained about using a duplicate port of one of the old connections.

I then reinstalled the backup and deleted the two connections, reboot.

The first one set up with out problems. It’s pretty much default everything on port 1195 with OpenVPN subnet of 10.10.9.0/255.255.255.0

The second one on port 1196 with OpenVPN subnet of 10.9.9.0/255.255.255.0, copied from what was working before, gives an OpenSSL 256 error.

The names are different, I even tried changing the local VPN hostname. I tried variations in the certificate fields

[tphz (iptom)]

Have you read this thread?

OpenSSL Error 256 when add a new N2N

Hi, below you have a link that may help: edit Also look in the index.txt file. The path to the above files in IPFire: /var/ipfire/ovpn/certs/ edit2 Below are the contents of the files in the new system [obraz] Below are the contents of the files after generating root/host certificates. [obraz] Below are the contents of the files after adding the N2N test connection. [obraz] edit3 Completion of information about index.txt file [obraz] The index.txt file is an ascii file cons…

BR

[ummeegge (Erik Kapfer)]

Hi all,
@jinnicky did you checked ‘/var/log/httpd/error_log’ ? May there are more detailed information what causes the 256 error ? Such error may can be intercepted by a plausibility check in ovpnmain.cgi ?

Best,

Erik

[jinnicky (Bob Ewart)]

Yes I did, thank you.

It turns out that the fields in the second certificate matched the first one too closely. Once I changed that, it was accepted.