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

    OpenVPN keys and certs in one file

    Scheduled Pinned Locked Moved OpenVPN
    3 Posts 2 Posters 1.6k 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.
    • S
      spm002
      last edited by

      Hi there, is there a way to enable the ability to have the certificates all nested in one .ovpn file instead of having it in seperate files.
      I know with the Normal OpenVPN with EasyRSA, there would consist a .ovpn, CA file, a certificate and a key, which to merge it in the .ovpn config file would look something like:

      –---BEGIN OpenVPN Static key V1-----
      f745... rest of tls key
      -----END OpenVPN Static key V1-----

      <ca>-----BEGIN CERTIFICATE-----
      CA Cert here
      -----END CERTIFICATE-----</ca>

      <cert>-----BEGIN CERTIFICATE-----
      Certificate Here
      -----END CERTIFICATE-----</cert>

      <key>-----BEGIN PRIVATE KEY-----
      Key Here
      -----END PRIVATE KEY-----</key>

      But im not too sure how to do it with the pfsense openvpn config files, as when I export the client config, I get a .p12 file which cannot be put into the .ovpn file.

      Is there anyway I could go about putting all the extra keys from the pfsense openvpn config into one .ovpn file?

      Thanks.

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Try exporting to Viscosity inline and see if that doesn't get you closer to what you are looking for.

        The exports are exported in a way that the target systems need for import.

        ETA: You probably want Inline > Others

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • S
          spm002
          last edited by

          Didnt realize it was that simple haha.
          Thanks a lot!

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.