You don’t know me too well, yet. Had already done that, hence “Installed now.”
Might be an idea to modify the original post with ‘rename’ as a pre-requisite.
Interestingly, I had to manually add port 8083 to CSF.
Pro tip:
If you are accessing your CSF protected server from a client with a dynamic IP, then signup for a dynamic DNS service, such as no-ip.org
In CSF configure DYNDNS to check every 10 minutes and ignore the resolved IP from blocking. Add your hostname eg. me.no-ip.org to /etc/csf/csf.dyndns
This way you won’t block yourself from the server - at least in terms of the firewall.
Of course, if you have a static IP then get yourself a DNS entry and add that.
Yes that could be the issue as there is no valid certificate any more to work with it.
Try to ping a external server. If it is not working most likely cause could be that there is a wrong ip blocked. Had it last time (+/- 2 weeks ago) and after disabling the firewall it worked fine.
@AlwaysSkint - Thanks, updated prerequisites with rename. Adding port 8083 is not interesting, all ports are disabled by default. Hestia is not officially supported. This is kind of hack which is actually working only with Hestia CP v1.0. Starting from Hestia CP v1.1.0 you also need to make manual changes. This will be maybe changed in the near future as @eris pointed out - there is an idea of changing the system, so that such changes in templates are preserved.
We switched over from the old php array system to Gettext. To make sure we can match. To make the strings working we use _() now. Following the official gettext function.
Thank you for this tutorial. What I would really like is for CSF to support Hestia. I added my request to the CSF Suggestions forum as in the link above. But for CSF to support Hestia, I am hoping more on this forum will register with the CSF forum and add your vote. CSF got 44 votes on the Hestia forum. I am hoping for 44 suggestions to support Hestia on the CSF forum!
