CSF Stuck on V 13.07
Unsure what is going here, there is 6 updated versions according the CSF changelog from the reported version on my server...
When I am in WHM and click the manual check, it is reporting this:
You are running the latest version of csf (v13.07). An Upgrade button will appear here if a new version becomes available
It does show this...(csget cron check) Failed to retrieve latest version from ConfigServer:
-
In CSF install.txt: Perl Modules ============ While most should be installed on a standard perl installation the following may need to be installed manually: # On rpm based systems: yum install perl-libwww-perl.noarch perl-LWP-Protocol-https.noarch perl-GDGraph0 -
Yeah seems to more be my server is not connecting to the update/downloads server on CSF. Seeing as how ping doesn't report back a success, and trying manually to update with csf -u doesn't work either. Why configserver would ban/block IP is a little strange to me 0 -
I made my own work around I guess. Just manually download from my browser the csf tgz file, uploaded it somewhere else, downloaded and installed v14.00 that way. 0 -
I don't think you get that error if the connection is blocked.
Probably more than one thing going on then, cause I ran those installs and the error didn't even go away, even after a reboot. (ie: yum install perl-libwww-perl.noarch perl-LWP-Protocol-https.noarch perl-GDGraph) When I click manual check it spins forever before I even got the latest version message. It provides a timeout in ssh with csf -u. Either way the manual work around updated the version to v14.00. This is what reports in there now: (csget cron check) Failed to retrieve latest version from ConfigServer:0 -
don't suppose the CSF download server has somehow ended up in your deny table ?? 0 -
don't suppose the CSF download server has somehow ended up in your deny table ??
no, one of the first few things I checked. Including temp disabling the firewall. Sloppy work around worked, but still annoying issue.0 -
You might also want to let them know here: ConfigServer Community Forum - Index page in the event they're unaware there is a potential issue. 0 -
I can mark it as solved, pending you were able to identify a resolution, which it sounds like your workaround achieved. 0
Please sign in to leave a comment.
Comments
10 comments