Fehlermeldung ist, dass es sich um keine sichere Verbindung handelt.
Habe ein Zertifikat von #letsencrypt mit #certbot erstellt.

Lösche ich alle Browserdaten und rufe meine URL auf, komme ich aus dem WLAN auf meine FritzBox raus.
Per LTE komme ich direkt zum Server auf die installierte Nextcloud

@izaya not shure if #1blu does support #certbot or #LetsEncrypt tho...

Maybe @fuchsiii knows more...

Otherwise #Contabo and #Hetzner offer #Web and #eMail hosting...

Nachgang zu #DomainFactory:Mittlerweile hat deren Support meine #Kündigung händisch bearbeitet, die letzte Domain ist umgezogen, der Vertrag gekündigt.

Nun bin ich bei #AllInkl. (Viele schwören auch auf #Manitu als Ersatz.) Der #Umzug kostet mich viel Zeit, auch durchaus etwas Geld. Aber dafür gibt's #LetsEncrypt #Zertifikate nun gratis, allein das spart ein dreistelliges Sümmchen pro Jahr ein. Außerdem zwei Inklusiv-Domains mehr und mehr Space.

It would be so cool if an organization popped up that somehow provided free merchant credit card services, like #letsencrypt did for SSL certificates. But I guess they'd have to bypass Visa/Mastercard fees somehow, while still accepting them for payment. Impossible?

https://www.wsj.com/finance/visa-mastercard-prepare-to-raise-credit-card-fees-ed779be1 #visa #mastercard #creditcard #fees

@fedibikes

Warum kein #LetsEncrypt mit #Cerbot und/oder #Dehydrated und Eintrag in die #Crontab ?

@SgtBloody @koyu

True.
Maybe try it I suppose.

Just make sure that the costs dont add up too much

And if you want SSL, make sure it has #LetsEncrypt Support, if you want to go that route
(Ooor pay extra to get it another way I guess)

My first #NextCloud instance is running in my local network 🥳
Unfortunately, #iOS needs a valid certificate for access...
I would like to use a wildcard certificate from #LetsEncrypt for all severs on my local network (I use a own public domain internally).. Any hints how to realize that and how to distribute this wildcard certificate to all the local servers?
My domain hoster have a #acme compatible API
Any tutorials are welcome 🤘
#linux #server

Let’s Encrypt Zertifikat zu FRITZ!Box Importer:
https://github.com/jzdm/le-certificate2fritzbox
Skript zum automatisierbaren Zertifikatsimport auf die #Fritzbox.
#Letsencrypt #certificate #import #Zertifikat

Apart, bijna een kwartier zitten wachten tot de DNS mijn _acme-challenge goed doorgaf, de na certificaatuitgifte ingevulde dummywaarde was binnen vijf minuten weer zichtbaar. #Letsencrypt

Bon, au cas où ça arrive à quelqu'un, mon wildcard certificate (*.m0le.net) n'était plus valide suite à son expiration et j'avais l'erreur:

Failed to renew certificate domain.net with error: Unable to determine zone identifier for domain.net using zone names: ['domain.net', 'net']

Quand je faisais un certbot renew.

J'ai du recréer un token OVH API et c'est reparti.... aucune idée de ce qu'il s'est p… http://shaarli.m0le.net/?MPEq2A Note: letsencrypt OVH dns #certbot #letsencrypt #ovh

#HAProxy seems to have gotten a better way to handle #LetsEncrypt #TLS certificates with #acme.sh. I missed this post during summer: https://www.haproxy.com/blog/haproxy-and-let-s-encrypt. Going to try this in my home lab one of the upcoming evenings.

It ought to be easy-peasy to provision an #AWS #EC2 instance, point a domain name at it, and start serving a website. But friends, it is not. For who knows what reason, #AmazonLinux2023 makes it nearly impossible to use #LetsEncrypt, and AWS's alternative solution (#NitroEnclaves and such) is beyond overkill.

Scaling an instance up or down fails as often as it succeeds for me. The new policy of charging for #IPv4 addresses basically doubles the price for a small website. ☹️

(3/8) 🧵

It ought to be easy-peasy to provision an #AWS #EC2 instance, point a domain name at it, and start serving a website. But friends, it is not. For who knows what reason, #AmazonLinux2023 makes it nearly impossible to use #LetsEncrypt, and AWS's alternative solution (#NitroEnclaves and such) is beyond overkill.

Scaling an instance up or down is fragile. It fails as often as it succeeds. The new policy of charging for #IPv4 addresses basically doubles the price to run a small website. ☹️

(3/8) 🧵

Thank you #letsencrypt for at least 6 years #certificates for my webspace @team

🙌🍾

10 Jahre Let's Encrypt: 78 Prozent des Webverkehrs sind verschlüsselt | heise online
https://www.heise.de/hintergrund/10-Jahre-Let-s-Encrypt-78-Prozent-des-Webverkehrs-sind-verschluesselt-9235610.html

Today's edition of "Monday Morning unexpected UI changes which will make you wake up" is bought to you from #Azure which has removed the Browse Button from the #LetsEncrypt GUI. Fortunately the GUI is still available at
https://[your-webapp].scm.azurewebsites.net/letsencrypt.

10 Jahre #LetsEncrypt - zum Jubiläum könnte man ja S/MIME-Zertifikate einführen, oooooder? ;)

Celebrating Ten Years of Encrypting the Web with Let’s Encrypt - @eff
#letsencrypt #encryption #privacy

https://www.eff.org/deeplinks/2023/08/celebrating-ten-years-encrypting-web-lets-encrypt

Nice little #nix & #nixos tip when serving websites with #acme and #letsencrypt which isn't mentioned anywhere I've seen yet:

You can specify an acme cert using `security.acme.certs.<name>.{...}` and then in your nginx vhost use `useACMEHost` **instead of `enableACME`** which lets you do things like having the "bare" domain setup with a proper redirect to `www.` without duplicating the cert.

สงสัยบางอย่าง
ถ้าตั้ง DNS ชี้ไปยังที่อยู่ IP แบบ Dynamic วันดีคืนดี IP เปลี่ยนแล้วไม่ได้ update จะมีบอตมาหลอกออกใบรับรอง "Let's encrypt" ผ่าน http รึเปล่า? เพราะเคยตั้ง DNS ทิ้งไว้แล้ว IP เปลี่ยนลองเข้าเล่น ๆ ออกเว็บใครก็ไม่รู้ :fox_nervous:
#letsencrypt

With the proper documents, any may pass and be trusted. #TLS #LetsEncrypt #Linux #OpenSource https://cromwell-intl.com/open-source/letsencrypt-tls-cert-godaddy.html?s=mc