Curl fix for Lets encrypt

Why is that? Is the timeout of 15 minutes that bad?
Letsencrypt update way before the end of the certificate, so you should not notice anything about the 15 minute delay.
 
Last edited:
Let's encrypt runs in the background (even when you request a 'new' certificate through the user interface), so there really is no need for this. :)
And I think that every serious provider should have IPv6 by now. ;)

Or you should disable IPv6 on your server (also an option of course).
 
On 1 server I have both an ipv6 ip and ipv4 (which is the main ip) and the Letsencrypt is automatically made for the ipv4 so I don't see any issues yet either.
 
Sorry all. I am not saying it s broken. My suggestion is if the Line of code helps anyone. If putting the line of code in means it takes 5 minutes to run shouldn't the main script just be improved?

If it not needed or doesn't help. Can we some how note that.
 
I wonder if changing it is a real improvement. I'm no scripter but I wonder if putting -4 in there by default, would not cause Letsencrypt to not check ipv6 anymore, which would not be a good thing.
But again, I'm no scripter so it's just a thought of me.
 
Richard G said:
I wonder if changing it is a real improvement. I'm no scripter but I wonder if putting -4 in there by default, would not cause Letsencrypt to not check ipv6 anymore, which would not be a good thing.
But again, I'm no scripter so it's just a thought of me.
Click to expand...
Right I don't want to break it. Just wanted them to look at it and see if there was a way to make it better..
 
You must log in or register to reply here.
Back
Top