Thanks John. The permissions are the same except the old files have an
additional group, "Authenticated users", that was not listed for the new
files. We added that group for the new files but they are still not
working. Maybe we should try removing all groups except "Authenticated
users"... The old files are from Go Daddy and the new files are from
DigiCert but I'm told that should not make a difference. Plus we have at
least two other sites running fine with DigiCert certificates.

Thanks again for the reply.
-- 
Rebecca Bryant Williams
becca...@gmail.com

>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 9 Jan 2020 09:14:10 -0500
> From: Rebecca Bryant <becca...@gmail.com>
> To: 4d_tech@lists.4d.com
> Subject: problems with SSL cert
> Message-ID:
>         <CAO6o6=Xfo1G6g=
> fvvs3degbckja06imy++knwmabga8-qge...@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> I am having a problem getting a new SSL certificate to work. This web app
> has been running successfully with SSL for several years. The current cert
> expires in a few days so I used GENERATE ENCRYPTION KEYPAIR and GENERATE
> CERTIFICATE REQUEST to generate a private key, public key, and certificate
> request. The request was submitted to DigiCert (by a tech support
> co-worker). The resulting file was renamed 'cert.pem' and the private key
> was renamed 'key.pem' and placed in the folder with the structure. When I
> try to start the app I get an error on the first line of the startup
> routine; it lists the 'key.pem' file with the error 'Access denied'. I have
> done all of this successfully before so I am stumped as to what is causing
> the failure this time. The app works fine if I replace the new cert.pem and
> key.pem files with the old ones (from Go Daddy). The app is running via 4D
> Server 16R5 on Windows Server 2016. Normally it runs as a service via
> FireDaemon. I have several other apps running with the same configuration
> and with SSL certs that were generated the same way.
>
> Any ideas what the problem might be? Any help would be greatly appreciated.
>
> Thank you and Happy New Year to all,
> Rebecca Bryant Williams
> becca...@gmail.com
>
>
> ------------------------------
> Message: 3
> Date: Thu, 9 Jan 2020 08:46:53 -0600
> From: John DeSoi <de...@pgedit.com>
> To: 4D iNug Technical <4d_tech@lists.4d.com>
> Subject: Re: problems with SSL cert
> Message-ID: <2f4f5618-6c73-4455-9222-ff8c2ced3...@pgedit.com>
> Content-Type: text/plain;       charset=us-ascii
>
>
> > On Jan 9, 2020, at 8:14 AM, Rebecca Bryant via 4D_Tech <
> 4d_tech@lists.4d.com> wrote:
> >
> > When I
> > try to start the app I get an error on the first line of the startup
> > routine; it lists the 'key.pem' file with the error 'Access denied'.
>
> Compare the file permissions on the old key to the new key and make sure
> they are the same. Not sure about Windows, but with Linux things sometimes
> fail if file access is too permissive. Keys should generally be user only
> access but maybe that is not the case here to run as a service.
>
> John DeSoi, Ph.D.
>
**********************************************************************
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
**********************************************************************

Reply via email to