You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying to get docksal to use a nonstandard cert per the doc
I've set URL.crt and URL.key in the /etc/certs/custom/ folder and tagged the cert with a label in my docksal.yml
However, when i run fin restart and load the site it still serves the default *.docksal cert.
When I run docker logs docksal-vhost-proxy i get:
[proxyctl notify]: nginx: [emerg] PEM_read_bio_X509_AUX("/etc/certs/custom/URL.crt") failed (SSL: error:0906D06C:PEM routines:PEM_read_bio:no start line:Expecting: TRUSTED CERTIFICATE)
From this i assumed i needed to trust the CA cert to the box. I trusted the cert locally then realized the cert needed to be trusted in the container after i got the same error.
I haven't made much progress on getting the container to trust a CA cert. Has anyone seen anything like this? I didnt know if there was a known fix or if im trying to do something way off base here.
The text was updated successfully, but these errors were encountered:
I've been trying to get docksal to use a nonstandard cert per the doc
I've set URL.crt and URL.key in the /etc/certs/custom/ folder and tagged the cert with a label in my docksal.yml
However, when i run fin restart and load the site it still serves the default *.docksal cert.
When I run docker logs docksal-vhost-proxy i get:
[proxyctl notify]: nginx: [emerg] PEM_read_bio_X509_AUX("/etc/certs/custom/URL.crt") failed (SSL: error:0906D06C:PEM routines:PEM_read_bio:no start line:Expecting: TRUSTED CERTIFICATE)
From this i assumed i needed to trust the CA cert to the box. I trusted the cert locally then realized the cert needed to be trusted in the container after i got the same error.
I haven't made much progress on getting the container to trust a CA cert. Has anyone seen anything like this? I didnt know if there was a known fix or if im trying to do something way off base here.
The text was updated successfully, but these errors were encountered: