Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

preferred_chains not consistent after auto renew #4383

Closed
JaosnHsieh opened this issue Oct 15, 2021 · 1 comment
Closed

preferred_chains not consistent after auto renew #4383

JaosnHsieh opened this issue Oct 15, 2021 · 1 comment
Labels
invalid ❓ This doesn't seem right

Comments

@JaosnHsieh
Copy link

Since the issue on electron.
Remove the current certificate by $ rm -rf /var/lib/caddy/.local/share/
And add ISRG Root X1 as preferred_chains value and issued ISRG Root X1 certificate successfully.

But after around 2 weeks, Caddy automatically renew the certificate, and seems like it's not use ISRG Root X1 as preferred_chains.

Is there a way to check what's the preferred_chains value in existing files in /var/lib/caddy/.local/share/ or how to make it consistent after renewing?

OS Ubuntu 18.04
Caddy version 2.4.5

/etc/caddyCaddyfile

api.example.com:80 {
        reverse_proxy localhost:3333
        tls {
        issuer acme {
            preferred_chains {
                root_common_name "ISRG Root X1"
            }
        }
    }
}

api.example.com:443 {
        reverse_proxy localhost:3333
        tls {
        issuer acme {
            preferred_chains {
                root_common_name "ISRG Root X1"
            }
        }
    }
}
@JaosnHsieh
Copy link
Author

After checked issue history from https://crt.sh/.
It seems not related to renew issue on Caddy.
closed because the issue should on electron side.

@francislavoie francislavoie added the invalid ❓ This doesn't seem right label Oct 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid ❓ This doesn't seem right
Projects
None yet
Development

No branches or pull requests

2 participants