Community Forums
Connect with us on LinkedIn
+ Reply to Thread
Results 1 to 6 of 6
  1. #1
    Member
    Join Date
    Dec 2008
    Posts
    21

    Default Error: (Curl Error) Received problem 3 in the chunky parser - code: 56

    Hello,

    I'm using the WHMCS, the api work fine for lasted version 11.24, but actually I have another server with 11.25, and I have the report of a new account created with the next error "Error: (Curl Error) Received problem 3 in the chunky parser - code: 56"...

    Someone know how to fix it????

    Thanks a lot, and sorry for my bad english...

    Jonathan J.
    Last edited by Jonjimar; 02-12-2010 at 04:14 PM.

  2. #2
    Member
    Join Date
    Feb 2003
    Location
    Texas
    Posts
    73

    Default

    I too would like to hear from WHMCS and Cpanel on this subject as it has got on too longer with a fix by one of them


    Quote Originally Posted by Jonjimar View Post
    Hello,

    I'm using the WHMCS, the api work fine for lastet version 11.24, but actually I have another server with 11.25, and I have the report of a new account created with the next error "Error: (Curl Error) Received problem 3 in the chunky parser - code: 56"...

    Someone know how to fix it????

    Thanks a lot, and sorry for my bad english...

    Jonathan J.

  3. #3
    Member
    Join Date
    Feb 2003
    Location
    Texas
    Posts
    73

    Default Error: (Curl Error) Received problem 2 in the chunky parser - code: 56

    Any response to this cpanel?? Dave someone ??

  4. #4
    cPanel Staff cPanelDavidL's Avatar
    Join Date
    Nov 2007
    Posts
    17

    Default

    We are looking to recreate this issue presently. Would someone be able to walk us through recreation of this error?

  5. #5
    cPanel Staff cPanelMatt's Avatar
    Join Date
    Apr 2005
    Location
    Houston, TX
    Posts
    409

    Default

    If you are encountering this issue, please open up a ticket with us at https://tickets.cpanel.net/submit

    With this ticket please include credentials to access both the WHMCS installation and the cPanel server in question. I have had this issue reported to me about a week ago and have been unable to reproduce the problem (thus why I need access to an affected WHMCS installation).
    Matt Dees
    Integration Developer
    cPanel, Inc.
    cPanel Integration Blog

  6. #6
    Registered User
    Join Date
    Apr 2010
    Posts
    1

    Default

    Just got a reply back from my hosting support. They have been speaking to WHMCS and cPanel and got this reply:

    "It appears that there are some issues with the way that cPanel handles STDERR output over non-SSL connections. It would seem that it's writing them to socket rather than the error_log."

    There is a couple of things they recommend:

    If you have access to WHM, go to Tweak Settings and untick 'Display Errors in cPanel instead of logging them to /usr/local/cpanel/logs/error_log'
    (apparently cPanel is removing that option in cPanel v11.25.1)

    Also if you enable SSL access in WHMCS (Under Setup -> Servers -> Edit Server at the bottom) It should stop the error from occurring.

Similar Threads & Tags
Similar threads

  1. Error log: PHP curl error
    By cyberchimps in forum cPanel and WHM Discussions
    Replies: 3
    Last Post: 05-12-2011, 02:45 PM
  2. Replies: 3
    Last Post: 03-09-2011, 11:28 PM
  3. ERROR: Curl Error libcurl was built with SSL disabled, https: not supported!
    By ramystyle in forum cPanel and WHM Discussions
    Replies: 2
    Last Post: 08-21-2007, 04:52 PM
  4. Received Error 500 for New Account
    By hbuckland in forum cPanel and WHM Discussions
    Replies: 4
    Last Post: 06-04-2007, 05:36 PM
  5. Horde forwarding error sendmail returned error code 255
    By Snowman30 in forum cPanel and WHM Discussions
    Replies: 2
    Last Post: 03-04-2004, 10:46 AM
Linkedin       Facebook       Twitter       RSS       Flickr       YouTube