Skip to main content

csf v16

Comments

3 comments

  • Hi,

     

    In your current situation, updating cPanel shouldn't apply the CSF updates. The cPanel version upgrade and the CSF migration are separate processes. Since you have AUTO_UPDATES=0 in your csf.conf, cPanel's automatic migration to its maintained CSF fork will not be applied to your server. This is by design — cPanel explicitly skips the migration for servers with AUTO_UPDATES disabled.


    Your CSF v14.24 is from the original ConfigServer (Way to the Web Ltd.), which shut down permanently on August 31, 2025. Their update servers are offline, so your CSF is currently not receiving any security updates from any source.

     

    If you want to ensure your CSF is updated without Auto-updates, we have instructions below under the "Manage Updates Yourself" section:

     

    cPanel will provide its own fork of CSF starting Feb 25th, 2026

    0
  • Scott Galambos

    Right.  But I do not mind setting AUTO_UPDATES=1.  Would an update from v134 to v136 now include csf v16?

    0
  • Hi,

     

    The cPanel update itself shouldn't cause CSF to upgrade to v16. I've tested this on my own VM by enabling Auto updates in CSF and upgrading to cPanel v136, my CSF installation remained on v15.

     

    However, you can run the commands mentioned in the documentation below to process the upgrade to CSF v16.x:

     

    https://docs.cpanel.net/knowledge-base/third-party/how-to-install-csf/#upgrade-to-cpanel-csf

     

    0

Please sign in to leave a comment.