Configserver down?

During fresh install of cwp the csf firewall errored on install, I have tried everything to get it to install but it may be due to their server being down:

[root@viking src]# sudo wget https://download.configserver.com/csf.tgz
--2025-09-04 03:39:53--  https://download.configserver.com/csf.tgz
Resolving download.configserver.com (download.configserver.com)... 94.130.90.175
Connecting to download.configserver.com (download.configserver.com)|94.130.90.175|:443... failed: Connection refused.

Please see the other threads about CSF going open source (GPLv3). Info about converting to the v15 open source release:
https://starburst.help/security/csf-lfd/csf-firewall-gplv3-release/

CSF is gone for good as of Aug 31st, now what??? Why didn't CWP address this in the fresh installs instead of leaving everyone not working. That is VERY unprofessional!!!

https://configserver.com/announcement/

CSF is gone for good as of Aug 31st, now what??? Why didn't CWP address this in the fresh installs instead of leaving everyone not working. That is VERY unprofessional!!!

https://configserver.com/announcement/
[root@viking ~]# cp -R /etc/csf /etc/csf.backup
cp: cannot stat '/etc/csf': No such file or directory

[root@viking ~]# cp /usr/local/csf/version.txt /usr/local/csf/version-backup.txt
cp: cannot stat '/usr/local/csf/version.txt': No such file or directory

[root@viking csf]# csf -v # Should show v15.00
csf: v15.00 (CentOS Web Panel)
*WARNING* TESTING mode is enabled - do not forget to disable it in the configuration


Got it now

Firewall manager Firewall is Disabled
ConfigServer Security & Firewall (CSF) + Login Failure Daemon (LFD)

Status: csf: v15.00 (CentOS Web Panel)

Enable firewall
[root@server ~]# csf -e
csf and lfd are not disabled!



Firewall manager Firewall is Disabled
ConfigServer Security & Firewall (CSF) + Login Failure Daemon (LFD)

Status: csf: v15.00 (CentOS Web Panel)

Firewall update
[root@server ~]# csf -u;csf -v
Oops: Unable to download: No Host option provided
csf: v15.00 (CentOS Web Panel)

csf -u won't work currently as there is no longer an update server. Starburst is working on setting up a mirror from the Github repository so you can update:
https://starburst.help/control-web-panel-cwp/control-web-panel-cwp-admin-tutorials/csf-firewall-error-oops-unable-to-download-no-host-option-provided/
https://starburst.help/control-web-panel-cwp/control-web-panel-cwp-admin-tutorials/csf-firewall-gplv3-release-tweaked-for-cwp/

As @overser mentioned, since ConfigServer closed there business & went open source, auto updates no longer work.

We setup this on our mirror network so auto updates can work again, please see:
https://starburst.help/control-web-panel-cwp/control-web-panel-cwp-admin-tutorials/csf-firewall-error-oops-unable-to-download-no-host-option-provided/

A list of servers you can use, CSF allows 2, can be found at:
https://starburstservices.com/downloads/mirrors-list/
Under Repository ConfigServer, the Mirror URL is what you would use in the config article above.

This is open to all, including other control panel users, so it will work with cPanel, CyberPanel, stand-alone, etc.

CSF is gone for good as of Aug 31st, now what??? Why didn't CWP address this in the fresh installs instead of leaving everyone not working. That is VERY unprofessional!!!

https://configserver.com/announcement/

This is/was not CWP's fault...

They Do Not control 3rd party companies, ConfigServer shocked everyone when they posted their 30 day notice.

I made a post when that first was posted here.

dl.starburst.help has a mirror of their archive, as well as their new open source.

We also have copies of all their FAQ's in our public knowledge base.

Make sure you have testing mode disabled in csf.conf

Adn then if csf -e still doesn't work for some reason:

Code: [Select]

systemctl enable csf

Code: [Select]

systemctl enable lfd

Code: [Select]

systemctl start csf

Code: [Select]

systemctl start lfd

CSF is gone for good as of Aug 31st, now what??? Why didn't CWP address this in the fresh installs instead of leaving everyone not working. That is VERY unprofessional!!!

https://configserver.com/announcement/

This is/was not CWP's fault...

They Do Not control 3rd party companies, ConfigServer shocked everyone when they posted their 30 day notice.

Of course it's not their fault.  That said, the fact that CWP didn't give a heads up about the fact that their product would stop working is unprofessional.  So, I agree with DragoCon.

Even if they didn't have an immediate solution, they could have added a warning message to the CWP Dashboard about the impending change to CSF.  That would have let people like me (who rarely visit these support forums or follow news about this stuff) the chance to know something might break before it broke.

Trust me, lots of people are grateful that there are people like you who do provide free support.  But that doesn't change the fact that CWP should be more proactive about this stuff.

CSF is gone for good as of Aug 31st, now what??? Why didn't CWP address this in the fresh installs instead of leaving everyone not working. That is VERY unprofessional!!!

https://configserver.com/announcement/

This is/was not CWP's fault...

They Do Not control 3rd party companies, ConfigServer shocked everyone when they posted their 30 day notice.

Of course it's not their fault.  That said, the fact that CWP didn't give a heads up about the fact that their product would stop working is unprofessional.  So, I agree with DragoCon.

Even if they didn't have an immediate solution, they could have added a warning message to the CWP Dashboard about the impending change to CSF.  That would have let people like me (who rarely visit these support forums or follow news about this stuff) the chance to know something might break before it broke.

Trust me, lots of people are grateful that there are people like you who do provide free support.  But that doesn't change the fact that CWP should be more proactive about this stuff.

1. CWP continued to work, so I have no idea what the frak you are talking about with that...

2. The author of CSF didn't put it into the open source arena until 2 days before the end of the month.
Then it took me a few days how to figure out how to re-enable csf -u, so it didn't error.

That just didn't happen to CWP, it also happened to cPanel and Stand-Alone users of CSF.

There is no replacement for CSF, that's the problem.
I saw Imunify 360 try to push ads they that they are a replacement, but they are not. They are just like ClamAV.

Closest replacement would be fail2ban and Nftables, but then still will be missing part of what CSF offers.

Then comes the whole problem that Linux is moving away from IPtables for the for mentioned Nftables in EL10.
But Nftables does have a IPtables compatibility mode.

Which mean some one now has to take the banner and either crate something like CSF from scratch or overhaul CSF completely to work with Nftables in native mode.
CSF was mostly written in Perl, which no one codes in anymore, it's mostly all in PHP now a days.

Thankfully this might happen before the EOL of EL9.

Otherwise, it's just not CWP in trouble, it's also cPanel and others.

Don't get me wrong CWP seems to be dropping the ball lately, I'm not sure what's going on, even from a partner aspect.

@overseer and I try to do the most we can, with @cyberspace helping also.