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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
Why do people jump to "my IP is blocked" when they can't get a cert? That's almost never the cause of a problem getting a cert. But it seems to be happening a lot lately that someone can't get a cert, and the first assumption is that Let's Encrypt has blocked their IP.
@nirjhar, you've issued a lot of certs in the past week (see https://crt.sh/?q=lonesock.pro), so much so that I wouldn't be surprised if you'd hit the rate limit for duplicate certs. But the problem right now is that your server is refusing connections on port 80.
Well, first, according to the output you posted, you're trying to get a cert from ZeroSSL, not from Let's Encrypt, so we can't help you with it. Second, the output you posted has nothing to do with bitspath.net. Third, the domain it does have to do with (dhanmondi.lonesock.pro) is refusing connections on port 80, which will prevent cert issuance.