Tto5MBQGA1UdEQQNMAuCCW1hYy5sb2NhbDAKBggqhkjOPQQDAgNIADBFAiEA4M0kĪYt3GuLjWSccvOkBZTe圆TTbCAzRootmbVRDhxkCIDNUb0N8iWdbFSIutBu1Fl/M WMrBVJDulZUFtgbxS9xOUVohMB8GA1UdIwQYMBaAFBqZ8rK4lWcHiTn2Z4pu2riK P7SWcb0sKtgbqRyzC2mCzVBlKin5Ld9ur5ndhebdo4GIMIGFMA4GA1UdDwEB/wQEĪwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwHQYDVR0OBBYEFBW8 ZTAeFw0yMDA3MDIxNTM1MzZaFw0yMDA3MDMwMzM2MzZaMAAwWTATBgcqhkjOPQIBīggqhkjOPQMBBwNCAATjupQHoH3圎wQC6PXxX1e0C4oYLfIATo5p3z5osc+9oB3d MC8GA1UEAxMoQ2FkZHkgTG9jYWwgQXV0aG9yaXR5IC0gRUNDIEludGVybWVkaWF0
MIIBuzCCAWGgAwIBAgIRAMGDzv0suRkkU3eIWoDbePIwCgYIKoZIzj0EAwIwMzEx Issuer: Caddy Local Authority - ECC Intermediate
#DOCKER FOR MAC INSTALL CERTIFICATE FULL#
Error messages and/or full log output: Chrome’s certificate details:Ĭhrome-cert-details 964×2452 323 KB Chrome’s message:Īttackers might be trying to steal your information from mac.local (for example, passwords, messages or credit cards). Firefox on the same machines works (it also uses the separate cert store and handling). AFAICT the certs are complying with, but they both give the “certificate invalid” message with an additional info “certificate is not standards compliant” (please see below). No matter what I do so far they are giving errors and not connecting. All is working except for Safari and Chrome (both using Keychain) on macOS. Trying to use Caddy 2.1 to serve https on internal domains to (mostly) mac clients. #install to system keychain, set trust (ssl, x.509) Sudo bash -c "echo 127.0.0.1 mac.local > /etc/hosts"ĭocker run -d -p 80:80 -p 443:443 caddy caddy file-server -domain mac.localĭocker exec $(docker ps |grep caddy|awk '') cat /data/caddy/pki/authorities/local/root.crt >./caddy-docker.crt Server: Docker version 19.03.8, build afacb8bĬlients: macOS10.15.5, Safari 13.1.1, Chrome. How I run Caddy:ĭocker run -d -p 80:80 -p 443:443 caddy caddy file-server -domain mac.local a. V2.1.1 h1:X9k1+ehZPYYrSqBvf/ocUgdLSRIuiNiMo7CvyGUQKeA= 2.
0 kommentar(er)
