Same issue An error occured during request "GET https://acme-v02.api.letsencrypt.org/directory"
@arvydasHostinger I moved your post into its own thread. We will need more info from you to be able to help.
You posted in a thread about a communications timeout problem. There are a wide variety of causes of that kind of problem. And, by your description you are having a different problem than they were.
Had you started your own thread you would have been shown the below form. Please answer as much as you can
=============================
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.
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
5 Likes
It seems there was a temporary issue with issuing SSL.
Now everything is back to normal.
We are using the PHP ACME library and we received errors like these for multiple domains:
- An error occured during request "HEAD https://acme-v02.api.letsencrypt.org/acme/new-nonce"
- An error occured during request "GET https://acme-v02.api.letsencrypt.org/directory"
I did not see any message on the status page so I checked forums.
It was between 8:00 am - 3:00 pm on UTC timezone.
Not sure if you have noticed some issues at that time?
I have not heard anything different than what you see.
By my clock it is only 14:29:00 UTC so not quite 3:00pm yet 
There were a couple other reports from Singapore with same temporary problem. These can happen. Were your failed requests all at a particular time? Like always at the zero minute of each hour or similar? Because those are especially busy times and more likely to get fail message.
In the past a wide outage results in far more reports here than we saw.
3 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.