ACME DNS RFC-2136 Let's Encrypt certs
I've been pushing on certbot to handle CNAME entries when ordering certs, and finally given up. https://github.com/certbot/certbot/issues/6787 https://github.com/certbot/certbot/pull/9970 https://github.com/certbot/certbot/pull/7244 This repo contains scripts that: Create an ACME account with Let's Encrypt use TSIG credentials to talk to bind (RFC-2136) create TXT record in correct zone by following CNAME and SOA entries if present downloads certs installs certs on one or more F5s. The F5 credentials requires Administrator rights as Certificate Manager can't upload files. https://github.com/timriker/certmgr CNAME records are recommended to a zone with minimal or no replication and a low TTL. ie: _acme-challenge.example.com CNAME example.com._tls.example.com _acme-challenge.example.net CNAME example.net._tls.example.com _tls.example.com would have one name server and 30 second TTL or so a TSIG key would be created that only needs update access to _tls.example.com Comments welcome. JRahm I'm looking at you. 😎 More info: https://letsencrypt.org/docs/challenge-types/
Illegal Request in Learning Suggestion for 200 OK response
Dears, I want to know the reason why this suggestion is showing an illegal request status even though response code is 200 OK. Is it because multiple violations triggered? The policy is in transparent mode and I am just verifying the suggestions. Can someone please provide an expert advise?
/mgmt/toc - not possible to launch rest api rest browser
Hi, could you help please on how to kick off the api rest browser? attaching below the internals Thank in advance after providing my admin credentials, the follwoing response is returned { "code": 400, "message": "URI path /mgmt/logmein.html not registered. Please verify URI is supported and wait for /available suffix to be responsive.", "referer": "https://1.2.3.4/mgmt/toc", "restOperationId": 13525870, "kind": ":resterrorresponse" } Platform ID Z101 Platform Name BIG-IP Tenant Software Version BIG-IP v17.1.3 (Build 0.20.11) Bundle, r5600
Extend capacity of the blade on Velos
Hello everyone, for a customer I need to buy another blade for Velos system that permit to extend the capacity of the disk, at the moment i have cofigured a single blade that is it used at 85%, the target is to buy another one, for having a logical drive that is thwe sum of both hard drive. Is it possible to do it ? I have read documentations about it but, i have not found the correct information, in addition you have to say that now, in the first balde there are 9 Tenants who are working in a production environment, so that, the goal is activities, for add the new blade, should not have impacts on the production. Many thanks , in advanced, everyone. Awaiting news,TMOS 21.0.0 compatibility
Hello. The BigIP release matrix and the The F5 hardware/software compatibility matrix documents explicitely declare ix000 hardware serie as not compatible with TMOS 21.0.0. However, IHealth promotes it as an upgrade option for our i5600 hardware, and this uncompatibility doesn't match my own comprehension of "Hardware End of New Software Support (EoNSS)" limit, which is not reached yet for this platform until Jan 01 2026. Does that means TMOS 21.0.0 is supposed to be made available later for this hardware, or just that iHealth has a bug, and that I missed something in the definition of EoNSS ? Regards.How to Use ACME with BIG-IP
We are terminating SSL on BIG-IP and considering using KOJOT-ACME for automatic certificate renewal. Could you explain the steps, configuration, and requirements (such as version or model) for using ACME with BIG-IP? We are struggling because we don’t know exactly what needs to be done on the BIG-IP side.
