Can't update CSF - Protocol scheme 'http' is not supported

nutN2Lewz

Verified User
Joined
Feb 26, 2013
Messages
20
I posted this in the CSF Forum but never got a response ...

New CSF install on Centos6/DirectAdmin. Perl module HTTP::Request is installed.

When the cronjob attempts to update CSF I receive an email with "Oops: Unable to download: Protocol scheme 'http' is not supported". The CSF UI in DirectAdmin always states "Unable to connect to http://www.configserver.com, retry in xxx seconds. An Upgrade button will appear here if new version is detected"

Can anyone help me solve this error?

Thanks, Barry
 
Have you manually created a cron job for this, or is the cron job created by CSF itself? I ask because of restrictions in DirectAdmin you must login to the root shell to upgrade csf, for example you can't upgrade CSF in the GUI. I manually do this as root:

Code:
csf -u
 
I did not manually create a cron job, just what was automatically created by CSF. I guess it is time to do a "csf -u" and forget about it until the next csf update.

Thanks, Barry
 
Just tried a root csf -u and I get the same error message ...

Oops: Unable to download: Protocol scheme 'http' is not supported

I am running perl v5.10.1. LWP::UserAgent is installed. Maybe I need to update perl?

Barry
 
You replied a month later you're wrong, he did gave the correct answer. :)

The error notice was not about not being able to connect but the scheme was not supported.
There are 2 ways to connect, either HTTP::Tiny or LWP::UserAgent.
Installing either one of them would fix them, or like CSF says itself:
Code:
yum install perl-libwww-perl.noarch perl-LWP-Protocol-https.noarch
or via apt-get or cpan.
 
You replied a month later you're wrong, he did gave the correct answer. :)

The error notice was not about not being able to connect but the scheme was not supported.
There are 2 ways to connect, either HTTP::Tiny or LWP::UserAgent.
Installing either one of them would fix them, or like CSF says itself:
Code:
yum install perl-libwww-perl.noarch perl-LWP-Protocol-https.noarch
or via apt-get or cpan.

perl-LWP-Protocol-https is not available on centos 6.7 w/o adding other repos.
also not in the epel repo now for some reason. server is fresh (2 days) install with only epel added to default repo.

I had same error, when looking after I ran cron to generate msg got scheme issue also.
added ip to whitelist in csf and it works, not sure if there was a fallback that worked once ip was whitelisted or not but I didn't have to mess with other repo or compile on my own.
 
perl-LWP-Protocol-https is not available on centos 6.7 w/o adding other repos.
As I said, you can install this via Cpan.

Normally CSF will fall back to http::Tiny by default. This can be changed to be http:Tiny by default in csf.conf.
I never ever had to add CSF's ip to the whitelist of the firewall (which is csf itself), so in that case CSF will block it's own ip? I wonder why or how.

Anyway, in that case both solutions are correct.
 
You replied a month later you're wrong, he did gave the correct answer. :)

The error notice was not about not being able to connect but the scheme was not supported.
There are 2 ways to connect, either HTTP::Tiny or LWP::UserAgent.
Installing either one of them would fix them, or like CSF says itself:
Code:
yum install perl-libwww-perl.noarch perl-LWP-Protocol-https.noarch
or via apt-get or cpan.

i've changed URLGET to Tiny in Firewall Configuration and after that i was able to run 'csf -u' without any inconvenience :cool:
 
Old post.
CSF also updated their online install.txt file long time ago:

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-GDGraph

# On APT based systems:
apt-get install libwww-perl liblwp-protocol-https-perl libgd-graph-perl

# Via cpan:
perl -MCPAN -eshell
cpan> install LWP LWP::Protocol::https GD::Graph
 
Sorry if I offended you
I'm not offended but since this is logic info, we normally don't up that ancient posts for it. If nobody asks in 6 years (and even 10 years after that link), then most likely in all this time nobody runs into that ip issue anymore or knows where the look.
Still odd indeed that they did not update that blog link, they probably forgot about it.
However it's good you want to help, for sure appreciate that. ;)
 
Back
Top