Lets Encrypt SSL Error (Error: Let's Encrypt validation status 400 (domain.com). Details: 403:"MY-IP: Invalid response

21

I managed to get a certificate for the primary domain. An error occurs when trying to generate a certificate for www-alias:

image
image536×626 26.4 KB

image
image1302×91 18.7 KB

If you delete www-alice:
image
image804×297 51.1 KB

22

What happens if you delete the redirect and keep the www alias?

23

Does not work:

image

image
image1312×76 13.4 KB

24

I wonder why http://www.derxxxxv.com returns a 400 error and not Hestia 404 error or the success page.

25

Maybe Hestia should send a request to htppS://www.alias-domain

26

Let’s encrypt does it…

27

Hi, there i have purchased the domain from cloudflare and proxy is on, im getting the same ssl error on create, what should i do,

28

like everyone from time to time i face this error also
i found that if i do nginx restart it fixes it for some time

29

check max open files, probaly limit needs to be adjusted.

30

can you please clarify how that can be done?

31

have a look at the search function: Search results for 'max open files' - Hestia Control Panel - Discourse

33

I was able to fix it like here:

comment:

systemctl reload-or-restart "$service" >> $log 2>&1
else

in
/usr/local/hestia/bin/v-restart-service

P.S.
Still not fixed in
Hestia Control Panel v1.9.3

34

as you can follow in the thread, its still a max open files issue

35

Try from this logic: Openbase_dir error / proxy_fcgi:error - #22 by sahsanu

36

I would like to understand better, is it just a matter of commenting on this section or does anything else need to be done?

systemctl reload-or-restart “$service” >> $log 2>&1

I’m new to using Hestia CP and I’m having the same problem regarding Lets Encrypt SSL status 400.

37

Please attach your error log or screenshots!

38

i guess you forgot so commet
else

39

When commenting in the v-restart-service file, as below:

reload-or-restart

I get the following error now:

editar-dominio
editar-dominio618×107 5.91 KB

I even checked the status of bind9. The command return screen is as follows:

bind1
bind1717×148 4.99 KB

bind9
bind9609×160 4.63 KB

As I said earlier, I’m new to using Hestia CP. In fact, my websites were working normally. Now, I am unable to generate SSL on any domain be it an old or new website.

The error remains below the browser:

erro-navegador

Any suggestions on what I can still do?

Thanks!

40

It seems your server is having trouble connecting to IPv6 networks. You should check and resolve that issue first.

41

Huym… got it. I’m going to “research” this issue today.

Thank you very much for the tip!

1 Like