Hi @Raphael, already checked those threads, only one guy having a similiar issue than me:
Thing is, i’m not using Cloudflare for my server domain, as i understood, error 400 is due to bad dns configuration, when i installed the HestiaCp, the panel didn’t added the DNS rules automatically like Vestacp, dns and mail are empty, should id add the rules manually for the domain and then try to SSL?
Depends how you built up your dns. The only thing I can say is that let’s encrypt works properly and the LE 400 leads to an connection issue - as written in the other posts. Also be sure you’ve removed all ipv6 records, otherwise the validation will also fail.
I know the platform work, just don’t get it, why dns lookup is showing on any sites but hestia don’t recognize it, this is my dns settings, see something strange in it?
Also did “ping” to all the records and all respond to the server ip…
I didn’t set any ipv6 records.
Found a solution! By default Vestacp used to assign my main ip to domains automatically when added to the panel, in this case Hestiacp applied the my local ip provided by te server vendor wich is pretty similar to my main ip, just figured it out watching close in the panel.