# Problem connecting to server (get for https://acme-v02.api.letsencrypt.org/directory; curl returned with 60
**URL:** https://community.letsencrypt.org/t/problem-connecting-to-server-get-for-https-acme-v02-api-letsencrypt-org-directory-curl-returned-with-60/164465
**Category:** Help
**Created:** [November 1, 2021, 8:33am UTC](https://community.letsencrypt.org/t/problem-connecting-to-server-get-for-https-acme-v02-api-letsencrypt-org-directory-curl-returned-with-60/164465 "2021-11-01T08:33:56Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Rups](https://community.letsencrypt.org/u/Rups)
#### Post date: [November 1, 2021, 8:33am UTC](https://community.letsencrypt.org/t/problem-connecting-to-server-get-for-https-acme-v02-api-letsencrypt-org-directory-curl-returned-with-60/164465/1 "2021-11-01T08:33:56Z")
Hi,
I have lots of sites encrypted on my Ubuntu Machine with LetsEncrypt (via [Forge](http://forge.laravel.com)). This always worked like a charm, but few months ago that changed.
When I want to create or update a certificate, I get this error:
```nohighlight
2021-11-01 09:28:49 URL:https://forge-certificates.laravel.com/le/1234442/781378/rsa?env=production [4644] -> "letsencrypt_script1635755329" [1]
Cloning into 'letsencrypt1635755329'...
Note: checking out '91cccc0c234e4decf0a19595fa19a6f306788032'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at 91cccc0... ensure newline before new section in openssl.cnf
ERROR: Problem connecting to server (get for https://acme-v02.api.letsencrypt.org/directory; curl returned with 60)
EXPECTED value GOT EOF
ERROR: Problem connecting to server (get for https://acme-v02.api.letsencrypt.org/directory; curl returned with 60)
EXPECTED value GOT EOF
```
It look likes an old issue if I search the forum, but it does still occur..
I searched on this forum and found a solution that worked for someone; to set the MTU to 1400. I tried this, but that is not working for me. The other topics don't have a clear solution posted for as far I could find.
Is there maybe someone that has **the** solution?
---
### Author:  [@\_az](https://community.letsencrypt.org/u/_az)
#### Post date: [November 1, 2021, 9:34am UTC](https://community.letsencrypt.org/t/problem-connecting-to-server-get-for-https-acme-v02-api-letsencrypt-org-directory-curl-returned-with-60/164465/2 "2021-11-01T09:34:35Z")
Error code 60 indicates an error with SSL certificate verification, which would suggest that something is outdated or wrong with the trust store on this server.
What is the output of:
```
dpkg-query -l ca-certificates
curl -V
```
---
### Author:  [@rg305](https://community.letsencrypt.org/u/rg305)
#### Post date: [November 1, 2021, 3:17pm UTC](https://community.letsencrypt.org/t/problem-connecting-to-server-get-for-https-acme-v02-api-letsencrypt-org-directory-curl-returned-with-60/164465/3 "2021-11-01T15:17:07Z")
> [@Rups](#):
>
> `ERROR: Problem connecting to server (get for https://acme-v02.api.letsencrypt.org/directory; curl returned with 60)`
Here is the longhand English for that error:
```nohighlight
60 Peer certificate cannot be authenticated with known CA certificates.
```
---
### Author:  [@system](https://community.letsencrypt.org/u/system)
#### Post date: [December 1, 2021, 3:17pm UTC](https://community.letsencrypt.org/t/problem-connecting-to-server-get-for-https-acme-v02-api-letsencrypt-org-directory-curl-returned-with-60/164465/4 "2021-12-01T15:17:36Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.