Problem generating SSL; Need to restart NGINX everytime

Community Support
1

Hello,

I have a weird issue with one of my Hestia setups and I can’t figure out what is wrong. I compared all the config files with another Hestia install that it working fine and I can’t identify the issue. (Maybe I missed a config that I am not aware of?)

What happens is; When editing any SSL setting (like creating a new certificate or enabling automatic HTTPS redirection), basically any setting that is editing the nginx config, it seems like the reloading of NGINX doesn’t occur.

For example:
I create a new website, I check the “enable SSL”, I then get a 404 error because it says it cannot find the directory /well-kown/ to complete the challenge. I then do a full restart of NGINX and it then works.

I then need to do another NGINX reboot once that completes, otherwise it seems to keep the non-https config. If I try to install something with softaculous right away wirhout rebooting it a 2nd time, it will install it on http instead of https.

After that if I enable automatic HTTPS redirection, I also need to do another reboot for my changes to be saved.

I tried to reboot the server of course.

In the past we had custom nginx errors configured, but we removed that, and then there was an Hestia update. The issue started to happen after that update. We removed the custom errors at the same time as the update…

I’m using nginx as proxy and apache as web server.

At this point I am consireding a full reinstall of Hestia as I can’t figure out what’s going on.

I’d be grateful for your ideas and suggestions.

Thanks

2

first thing i would call is open files, have a look at the search function for “open files” and increase the limits.

2 Likes
4

sorry, that’s bullshit… No reinstall is needed, probaly the main issue is a limit in max open files as written above. Increase open max files limits and check again, it will probaly give the solution.

1 Like
5

Hello,

Thank you for your answer, it seems like this was indeed the issue.

We increased the max files and the certificate generated without any error on the first try.

I guess we reached too many sites now on our server that it started hitting that limit when running reloads on NGINX, makes sense.

Thanks again for the help! :slight_smile:

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.