Vendredi soir, vers 23h heure de Paris, Anthropic a reçu un courrier du gouvernement américain. Trois heures plus tard, ses deux modèles d'IA les plus ...

On May 8, 2026, Let's Encrypt temporarily halted all certificate issuance due to a potential incident involving Generation Y root cross-signature issues.

このマニュアルでは、さくらのレンタルサーバで無料SSL（Let’sEncrypt）を導入する手順についてご案内しています。前提条件・設定例前提条件無料SSL機能は米国の非営利団体であるInternetSecurityResearchGroup（ISRG）の運営するLet’sEnc

### Website URL https://ttpl.work.gd & https://tbankindia.work.gd ### Error Message ERR_CONNECTION_TIMED_OUT ### Other Information I recently parked the domains given above to my infinityfree domains “ttpl[dot]rf[dot]gd” and “tbin[dot]rf[dot]gd” respectively and also issued SSL certificates from Let’sEncrypt following the steps given to me for both the [dot]work[dot]gd domains and ttpl[dot]work[dot]gd’s SSL Certificate shows active but i get this timeout message when i try to use https on ttpl[dot]work[dot]gd and about the tbankindia[dot]work[dot]gd domain, its SSL Certificate is not active yet so i am not complaining on it. The domains ending with [dot]work[dot]gd have their dns managed with DNSExit. DISCLAIMER: tbankindia[dot]work[dot]gd is ONLY FOR A SIMPLE BANKING PROJECT, NOT A REAL BANK, the same implies for tbin[dot]rf[dot]gd.

When I've checked my Hostinger account- there is showing my certificate authority is - Let'sEncrypt, that's why I came here

I asked from the Hostinger Team, They said - they do not provide Public key certificate and cabundle to export. And they said- I can get an SSL certificate from Let'sEncrypt, That's why I came here, I urgently need this, can you please help me in this matter

Certificate Authority of my domain is Let'sEncrypt, so could you please help me to get the public key certificate and cabundle

I'll try and describe the setup a bit more... On my router I've got port forwarding set up for 80/443 towards the LAN IP of my HAOS server which is hosting the Nginx Proxy Manager. HAOS web for instance is available via its standard port 8123 locally on LAN. In NPM I defined a proxy host for http://<haos_lan_ip>:8123 and set the SSL setting to generate new cert with Let'sEncrypt and it just worked like that. For Plex the proxy host setup is a little different in that it uses https (without cert) out of the box on its default port 32400, so the host config looks like this: https://<plex_lan_ip>:32400 and I think the cert creation failed on the first attempt, but succeeded on the second try. My dad's ok2pad website was set up to run on port 80, but since I couldn't get the cert created, I tried changing its port to 8080 which didn't help, but that's what it runs on right now and in NPM it is set as http://ok2pad_lan_ip:8080. On Plex and HAOS I have the Force SSL setting enabled.

P.S.: I know of backup CAs in Caddy, but automations may fail for various reasons at some point in time - I experienced a fair share of those. Besides that, the availability of the CA at hand will then be of concern, too. Not with Let'sEncrypt, but I have seen downtimes for ZeroSSL, for example. Those are not a problem for renewals due in 30 days, but certainly for 3 days.

meyergru: > You kind of contradict yourself: You say Let'sEncrypt will not even offer 10 day certificates, yet with the accepted shortening in the next years they must - or use even shorter ones like 6 days. Let's Encrypt offers 90-day certs and shortlived 6+ day certs are pending. That is 6d and some hours something like 6d18h I forget exactly. It does not mean 6 or more days. There is no LE announcement for certs with 10-day lifetimes. meyergru: > As a matter-of-fact, 6 or 10 day certificates will be the only ones viable by 2029 No, 47 day certs will be available in 2029. The progression from the current "longer lived" certs will reduce to that. "shortlived" certs are a different scheme digicert.com ### TLS Certificate Lifetimes Will Officially Reduce to 47 Days The CA/Browser Forum has officially voted to amend the TLS Baseline Requirements to set a schedule for shortening both the lifetime of TLS certificates.

Thank you! I mostly would like to find out whether Let'sEncrypt caches the results and whether the TTL on our records matter. We do wait for propagation to our provider's nameservers. Sharing the account keys is something we'd like to strive for, but this won't always be possible (we build for external users who may or may not have a secret share mechanism available etc).

So, my assumption was that the TXT query results are cached by Let'Encrypt's Unbound recursive resolvers Let'sEncrypt side - from looking at this Caching of DNS-01 for domain and its wildcard · Issue #5820 · letsencrypt/boulder · GitHub I could be wrong

[3/31/2025] [3:11:58 PM] [Nginx ] › ⬤ debug Could not delete file: { "errno": -2, "code": "ENOENT", "syscall": "unlink", "path": "/data/nginx/proxy_host/2.conf.err" } [3/31/2025] [3:11:58 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [3/31/2025] [3:11:58 PM] [Nginx ] › info Reloading Nginx [3/31/2025] [3:11:58 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload [3/31/2025] [3:12:03 PM] [SSL ] › info Requesting Let'sEncrypt certificates for Cert #10: auto.tb.tec.br [3/31/2025] [3:12:03 PM] [SSL ] › info Command: certbot certonly --config '/etc/letsencrypt.ini' --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-10" --agree-tos --authenticator webroot --email 'iatudobelo@gmail.com' --preferred-challenges "dns,http" --domains "auto.tb.tec.br" [3/31/2025] [3:12:03 PM] [Global ] › ⬤ debug CMD: certbot certonly --config '/etc/letsencrypt.ini' --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-10" --agree-tos --authenticator webroot --email 'iatudobelo@gmail.com' --preferred-challenges "dns,http" --domains "auto.tb.tec.br" [3/31/2025] [3:13:36 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/temp/letsencrypt_10.conf [3/31/2025] [3:13:36 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [3/31/2025] [3:13:36 PM] [Nginx ] › info Reloading Nginx [3/31/2025] [3:13:36 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload [3/31/2025] [3:13:36 PM] [ Express ] › warning Saving debug log to /tmp/letsencrypt-log/letsencrypt.log my npm is not issuing a certificate and these are the logs it returns to me, can someone help me? and on the npm panel itself it gives an internal error