It seems like on new installations on Debian 12 bookworm and version 1.8.3 that nginx gets installed but when trying to start it fails to start with an emergency error that the cloudflare inc doesnt seem to exist. See screen shot.
How can onego about fixing this does one need to redeploy the machine and start a new installation? Can the installation process be resumed?
Trying to understand this a bit further. I can confirm the file indeed does not exist as per the screenshot
is this a file that maybe I can pull from the git repository and upload in the location mentioned in my previous screenshot?
Hello @jaquilina,
cloudflare.inc file is created during install fetching the ips from IP Ranges so something went wrong during your install. Maybe you should fill an issue on github because if there is a problem getting the ips during install, the include to cloudflare.inc in nginx.conf should not be created.
Anyways, here is the content of /etc/nginx/conf.d/cloudflare.inc file:
# Cloudflare IP Ranges
# IPv4
set_real_ip_from 103.21.244.0/22;
set_real_ip_from 103.22.200.0/22;
set_real_ip_from 103.31.4.0/22;
set_real_ip_from 104.16.0.0/13;
set_real_ip_from 104.24.0.0/14;
set_real_ip_from 108.162.192.0/18;
set_real_ip_from 131.0.72.0/22;
set_real_ip_from 141.101.64.0/18;
set_real_ip_from 162.158.0.0/15;
set_real_ip_from 172.64.0.0/13;
set_real_ip_from 173.245.48.0/20;
set_real_ip_from 188.114.96.0/20;
set_real_ip_from 190.93.240.0/20;
set_real_ip_from 197.234.240.0/22;
set_real_ip_from 198.41.128.0/17;
# IPv6
set_real_ip_from 2400:cb00::/32;
set_real_ip_from 2405:8100::/32;
set_real_ip_from 2405:b500::/32;
set_real_ip_from 2606:4700::/32;
set_real_ip_from 2803:f800::/32;
set_real_ip_from 2a06:98c0::/29;
set_real_ip_from 2c0f:f248::/32;
real_ip_header CF-Connecting-IP;
These are the perms for the file:
$ ls -l /etc/nginx/conf.d/cloudflare.inc
-rw-r--r-- 1 root root 805 Jul 24 20:42 /etc/nginx/conf.d/cloudflare.inc
Cheers,
sahsanu
Thanks for this.
If i manually create this file, how can i restart the hestia installation process?
I thought that the installation completed successfully and now the problem was that nginx didn’t start. I’ve been using hestiacp for 5 days so don’t know whether hestiacp supports restart a failed installation so I would wait till someone confirms it but if I were you, I would start again from scratch.
The problem is this start seems to be during the installation step, I think this is an incomplete install but I am not sure as the script doesnt show any progress as what has been installed and what is still pending
Just to give everyone an update this issue has been resolved as a fix has been pushed to the git repository.
Yes. Patched it yesterday evening we will release a new update on Monday / Tuesday…
if i pull the bash script with wget does it have the fix in it since it pulls it from github, or do i need to wait until you do another release?
You can pull:
And follow the steps explained here:
Will doing this
wget https://raw.githubusercontent.com/hestiacp/hestiacp/release/install/hst-install.sh
not pull the latest version of the script with the deployed fix?
Will not work
You need to clone the repo and follow the steps here:
# Replace with https://github.com/username/hestiacp.git if you want to test a branch that you created yourself
git clone https://github.com/hestiacp/hestiacp.git
cd ./hestiacp/
# Replace main with the branch you want to test
git checkout servicing
# Install Dependencies
npm install
# Build
npm run build
cd ./src/
# Compile packages
./hst_autocompile.sh --all --noinstall --keepbuild '~localsrc'
cd ../install
bash hst-install-{os}.sh --with-debs /tmp/hestiacp-src/deb/