Conversation
| curl -X GET "https://api.cloudflare.com/client/v4/zones" -H "Authorization: Bearer <API_KEY>" -H "Content-Type: application/json" | jq . | ||
| ``` | ||
|
|
||
| Open your `certbot.toml`, and update these fields: |
There was a problem hiding this comment.
The certbot is now a built-in feature in tproxy. It can be configured in tproxy.toml
There was a problem hiding this comment.
Is the standalone Certbot still available? Is the initialization and renewal process fully automatic?
There was a problem hiding this comment.
Is the standalone Certbot still available?
Yes.
Is the initialization and renewal process fully automatic?
When using the tporxy built-in certbot, it will exit after the cert is renewed. We can combine with external auto-restart, such as docker's restart=always to make it fully automatic.
The standalone certbot wont notify the tproxy when cert get renewed.
There was a problem hiding this comment.
it will exit after the cert is renewed
And it will cause existing TCP connections to drop?
There was a problem hiding this comment.
And it will cause existing TCP connections to drop?
Yes, approximately once per quarter.
There was a problem hiding this comment.
As I checked, the certbot became a built-in feature after this PR: #107. Since it's a big change, the documentation needs to be completely rewritten.
I think this is too much for this PR and it should be a separate task. This PR is proposed as a quick fix for the missing part of the doc, based on the tested behavior.
docs: add tproxy setup guide & faq
2 participants
No description provided.