as @fullyint suggested, but after provisioning and deploying the red chain in google Chrome appeared, with a “Your connection is not private” warning.
I decided to create a new provision on a new server on a fresh new trellis installation. After completing provision and deploying the site’s certificates still seems not to be working correctly.
When clicking on Certificate’s detail issuer is Fake LE Intermediate X1.
I can get site to work on https. Any ideas of what could be happening?
It may not be a solution but i think let’s encrypt requires the domain to point to the server ip so i’d check the dns propagation. As i said it may be something to check but may not be a solution.
Thanks everyone for the answers. I reinstalled Trellis and found there was a var defined as letsencrypt_ca: “https://acme-staging.api.letsencrypt.org” in our group_vars/all/main.yml, which should have been at the staging group
I tried reprovisioning the server without success, so we move to a fresh new droplet and we now have our brand new ssl on the domain.