Repository navigation
Add Sertican / Ücretsiz SSL to integrated projects - #2366
Open
xtrn89bogosse wants to merge 1 commit into
Open
xtrn89bogosse wants to merge 1 commit into
xtrn89bogosse wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Sertican / Ücretsiz SSL to the end of the integrated projects section and updates lastmod.
Project documentation: https://ucretsizssl.tr/acme-entegrasyonu.php
Public server-agent template: https://ucretsizssl.tr/assets/agents/sertican-server.py
The project integrates a PHP ACMEv2 backend with an owner-enrolled command-line agent. Apache/Nginx uses Certbot; IIS and Zimbra use the central HTTP-01 ACMEv2 workflow. This is an integrated project listing, not a standalone Python ACME library or a browser-only certificate form.
Unattended renewal is opt-in after a successful local deployment. Linux checks run twice daily and Windows tasks daily, with independently selected, persistent hours/minutes and randomized seconds on scheduled runs. Existing installations require the documented agent/timer update. Certificate private keys remain on the enrolled server.
Validation covers signed account/order/challenge/finalize/download/revoke flows against a controlled loopback CA, badNonce retry limits, rate-limit handling, scheduler migration, persisted backoff, and server-agent regression checks. We do not claim that every OS/customer setup has been tested against the live Let's Encrypt staging service.
The project uses its own name and does not claim affiliation with or endorsement by Let's Encrypt.