Results 1 to 13 of 13

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

  1. #1
    Join Date
    Feb 2013
    Posts
    25

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

    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

  2. #2
    Join Date
    Apr 2009
    Posts
    2,186
    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

  3. #3
    Join Date
    Feb 2013
    Posts
    25
    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

  4. #4
    Join Date
    Feb 2013
    Posts
    25
    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

  5. #5
    Join Date
    Jul 2008
    Location
    Maastricht
    Posts
    3,548
    I would certainly update first and see if that resolves your problem.
    Greetings, Richard.

  6. #6
    Join Date
    Aug 2008
    Posts
    194
    yum install perl-LWP-Protocol-https
    Manage And Secure Your Servers
    PM ME

  7. #7
    Join Date
    Jun 2012
    Posts
    626
    Quote Originally Posted by arazit View Post
    yum install perl-LWP-Protocol-https

    you replied to a 2.5 yr old post and didn't give what fixes it
    http://blog.configserver.com/?p=2308
    need to allow the ip there through firewall, instantly fixes issue.

  8. #8
    Join Date
    Jul 2008
    Location
    Maastricht
    Posts
    3,548
    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.
    Greetings, Richard.

  9. #9
    Join Date
    Jun 2012
    Posts
    626
    Quote Originally Posted by Richard G View Post
    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.

  10. #10
    Join Date
    Jul 2008
    Location
    Maastricht
    Posts
    3,548
    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.
    Greetings, Richard.

  11. #11
    Join Date
    Apr 2018
    Posts
    3
    Quote Originally Posted by Richard G View Post
    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

  12. #12
    Join Date
    May 2008
    Location
    The Netherlands
    Posts
    1,183
    Quote Originally Posted by arazit View Post
    yum install perl-LWP-Protocol-https
    Just wanted to add that this is still a good solution, just used this on CL 7.
    ~ Arieh

  13. #13
    Join Date
    Dec 2018
    Posts
    1

    thanks !

    Quote Originally Posted by arazit View Post
    yum install perl-LWP-Protocol-https
    solved also my problem

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •