Thank you for the response Timothy, but when I open the private key in a text editor it is the regular header, not the one indicating encryption. However, the folder containing the database files *is *encrypted. When I ran the routine to create the private and public keys and the CSR, I saved those files to a different folder. I'm wondering if that is causing the issue. Maybe they should have been saved into the folder where the database files reside (i.e., the encrypted folder).
Rebecca On Thu, Jan 9, 2020 at 7:05 PM Timothy Penner <tpen...@4d.com> wrote: > If I had to guess, its that the private key is encrypted and requires a > password. If that’s true you will need to remove the password first. > > Here is a reference for this, from digicert nonetheless: > https://knowledge.digicert.com/solution/SO5292.html > > -Tim > > > Timothy Penner > Senior Technical Services Engineer > > 4D Inc > 95 S. Market Street, Suite #240 > CA 95113 San Jose > United States > > Téléphone : +1-408-557-4600 > Standard : +1-408-557-4600 > Fax : +1-408-271-5080 > Email : tpen...@4d.com > Web : www.4d.com > > > > > > > -- Rebecca Bryant Williams becca...@gmail.com ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
