The CSF project is abandoned, and newly installed CWP Pro already has several issues during installation.
Here is the topic: https://www.jaspreet.net/2025/09/06/3180/how-to-fix-csf-firewall-error-oops-unable-to-download-no-host-option-provided/

@Sandeep B. Do you have any idea how to replace CSF in CWP Pro servers?

🔍 Issue Summary (CSF v15.00):

• csf and lfd are both properly installed and running:

  • systemctl status csf → active (exited)

  • systemctl status lfd → active (running)

  • Manual commands such as csf -e, csf -r work as expected

  • lfd.log confirms proper startup, log watching, and IP tracking

However, the CSF firewall still shows as "Disabled" on the CWP Admin interface.

---

✅ What Works Correctly (on another server):

• On a similar environment (CWP Pro + AlmaLinux 9.x), the CSF firewall is correctly shown as active in the CWP interface when using csf v14.24 (CentOS Web Panel)

• All functionality and UI detection works fine with that version

Check out: https://starburst.help/control-web-panel-cwp/control-web-panel-cwp-admin-tutorials/csf-firewall-error-oops-unable-to-download-no-host-option-provided/

CSF replacement tested in old Centos 7, AlmaLinux 8.10 and AlmaLinux 9.6

The CSF project is continuing as Open Source project, the website is here: https://docs.configserver.dev/

Github: https://github.com/Aetherinox/csf-firewall

And as it was suggested in article https://www.jaspreet.net/2025/09/06/3180/how-to-fix-csf-firewall-error-oops-unable-to-download-no-host-option-provided/ you have to update the content of
/etc/csf/downloadserver

Comment out (or delete) the old content of the file and set the new line of download server: download.configserver.dev

Restart CSF and from the GUI of CWP update Firewall.
The result will be appear in the screen, and the CFS/LFD will update to the current version: Status: csf: v15.01 (CentOS Web Panel)

Or, you can use the solution suggested by @Starburst above.

Just as a note that is for the Forked version by Aetherinox who registered the .dev domain name.

Which is fine if you want to stick wit them going forward.

Just an FYI

Applied this fix.

Went from 14.26 to 15.0 without any hiccups using starburt's supplied config. Then I looked at the issue further and found that Aetherinox / csf-firewall was prbably going to be most supported and having a help community if needs be.

So I cahttr -i the conf files, edited them, then I chattr +i them again and did an update via CWP and not the command line.using Aetherinox / csf-firewall brought the version upto date at V 15.07

Not sure what made me look but I was doing some admin and looked at Way to the Web Ltd in a csf file and looked up and Configserver.com to find out that it has closed down permanently.

Note: I was thinking at first the CWP would update the package sourses in cwp script/s update. I went ahead without nowing if they had or had not.

@TheHolbi @Starburst

@Sandeep B. Is CWP going to update CWP with a new cfs repository / source? Will it hoop our fire walls if we took matters into our own hands by using the examples above? Is CWP going to pull from the Aetherinox / csf-firewall frok?