Previous versions never had this result, they all installed smoothly without any problems.
This time I keep getting the following error when installing Hestia 1.7, please help me.
Note: Each installation was done on a clean Debian 11.1 system with multiple reinstalls of the OS.
Error Alert：
[ * ] Configuring system settings…
sed: can’t read /etc/systemd/timesyncd.conf: No such file or directory
Failed to enable unit: Unit file systemd-timesyncd.service does not exist.
Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service not found.
Sorry, I’m too busy these days to get back to you in time.
I used the nginx -t command, but I don’t understand what the error is.
I just installed it again and still have the same problem.
[ * ] Enable SFTP jail…
[ * ] Create admin account…
[ * ] Configuring NGINX…
Job for nginx.service failed because the control process exited with error code.
See “systemctl status nginx.service” and “journalctl -xe” for details.
Error: nginx start failed
root@debian:~# nginx -t
nginx: [emerg] host not found in set_real_ip_from “<!DOCTYPE” in /etc/nginx/conf.d/cloudflare.inc:4
nginx: configuration file /etc/nginx/nginx.conf test failed
root@debian:~#
My Solution Testing:
After I cleared the contents of cloudflare.inc
root@debian:~# nginx -s reload
nginx: [error] invalid PID number “” in “/run/nginx.pid”
root@debian:~# nginx -c /etc/nginx/nginx.conf
root@debian:~# nginx -s reload
root@debian:~# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
So far, the system started successfully, but I’m not sure if cloudflare.inc will have an impact.
I just tested again, the problem seems to have been solved, it should be Hestia 1.7 system source code problems.
The content within the cloudflare.inc file can be changed to lowercase.
But I checked the installation source code, did not find this error, also went to github to check the content of cloudflare, did not find this error is caused by how.
There was a “bug” / issue with the old method that feches via the website sometimes the “Real user” kicked in this has been replaced via the api and working better…