SSL issues (one resolved, one not)

So one of the best solutions I found (and probably there is) would be to generate your own Certificate Authority (CA) and a signed certificate for your .local domain than authorize it in your chrome.

NOTE: BE SURE TO REPLACE yourdomain.local WITH YOUR ACTUAL DOMAIN

Steps:

  1. Backup Existing Certificates:
  • Execute: cp -r ~/DevKinsta/ssl ~/DevKinsta/ssl_backup
  1. Generate CA Key and Certificate:
  • Navigate to SSL directory: cd ~/DevKinsta/ssl
  • Generate CA key: openssl genrsa -out myCA.key 2048
  • Create CA certificate: openssl req -x509 -new -nodes -key myCA.key -sha256 -days 1825 -out myCA.pem
  1. Generate Domain Key and CSR:
  • Generate domain key: openssl genrsa -out yourdomain.local.key 2048
  • Create CSR: openssl req -new -key yourdomain.local.key -out yourdomain.local.csr
  1. Sign CSR with Your CA:
  • Sign CSR: openssl x509 -req -in yourdomain.local.csr -CA myCA.pem -CAkey myCA.key -CAcreateserial -out yourdomain.local.crt -days 825 -sha256
  1. Import CA to Chrome:
  • Open Chrome and go to chrome://settings/certificates
  • Navigate to Authorities, click Import, and select myCA.pem
  • Follow prompts to trust the CA for identifying websites.
  1. Restart DevKinsta Docker:
  • Restart Chrome DevKinsta and Docker container to apply the new certificate.

Hope that’s useful