Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
That error means that the Let's Encrypt main server successfully reached kozmetiktoptancisi.com to get an authentication file, but some Let's Encrypt secondary servers could not reach kozmetiktoptancisi.com. Please try again to see if the problem persists.
There is a timeout checking EDNS. And your zone definitions are inconsistent.
Fatal: Inconsistency between delegation and zone. The set of NS records served by the
authoritative name servers must match those proposed for the delegation in the
parent zone.: ns1.kozmetiktoptancisi.com (188.132.179.100): Delegation:
ns13.fiberserver.com, ns14.fiberserver.com, Zone: ns1.kozmetiktoptancisi.com,
ns2.kozmetiktoptancisi.com. Name Servers defined in Delegation, missing in Zone:
ns13.fiberserver.com, ns14.fiberserver.com.Name Servers defined in Zone,
missing in Delegation: ns1.kozmetiktoptancisi.com, ns2.kozmetiktoptancisi.com.
Effektive only one ip address works. May be fix your delegation and remove the not working ns14 server.
May be there are some random timeouts, so the first DNS check works, one of the secondary not.
One could argue that the IPs are the same (included in the root reply).
But that is inconsequential.
The names are NOT the same and this creates a DNS problem.