The SSL take time (10m) to activate the domain

[job_noam (Noam)]

This is our caddyfile (version: 0.10.9):

*.example.me:443 {
    tls /etc/ssl_custom/exampleme.pem /etc/ssl_custom/exampleme.key
    proxy / http://example.elasticbeanstalk.com {
        transparent
        header_downstream server "Example"
    }
}
:443 {
    tls {
        max_certs 500000
    }
    tls noam@example.com
    proxy / http://example.elasticbeanstalk.com {
        transparent
        header_downstream server "Example"
    }
}

After 10m the domain is working with SSL and everything. But until then the brwoser wrote there is a problem with the SSL.

Any idea way?

Thanks

[Whitestrake (Matthew Fay)]

@job_noam

After 10m the domain is working with SSL and everything.

Is this a *.example.me domain or a :443 domain you’re having trouble with?

Are you able to share Caddy logs during the attempt to connect to your sites when your browser gives you an error? (Run Caddy with the -log option).

[job_noam (Noam)]

@Whitestrake

:443

It’s give me the error on that: :443
And sorry I can’t share the logs because it’s production and I don’t have logs there. sorry

[Whitestrake (Matthew Fay)]

No logging on production, that’s unfortunate. There’s a large number of possible problems going on here, and the best way (that won’t involve hours and hours of trial and error) is to simply check what Caddy is telling you, via process, access, and error logs.

Unless you can do that, your best chance might be to hope that someone else on the forums here has experienced the same symptoms and pinned down the cause on their own systems.

[job_noam (Noam)]

I also agree with you but when we tried to add the logs last time our “caddy service” go down. So we disable it.
I know it’s the best way but we wanted the working way