Posts by kess

  • i-MSCP WHMCS Module error

    Sorry Nuxwin, but at present I've canceled everything pending.

    I had to generate the order and accept it without the automatic provision. I've than created the new domain manually using the i-MSCP interface.

  • i-MSCP WHMCS Module error

    Hi Nuxwin

    thx for your reply.


    The domain name is a required field during registration, but the domain registration (real domain registration on a registrar) is not mandatory.

    A customer could have an existing domain name, and he only needs the Hosting Plan.


    Here's the order form, as you can see the domain name is present, but unfortunately the error is still there.


    What kind of further information do you need in order to investigate ?

    Thx a lot,

    bye Kess.

    Files

  • i-MSCP WHMCS Module error

    Hello guys,

    I'm facing a strange error upon a new customer creation using the WHMCS module.


    I can't find no log in WHMCS or on i-MSCP Server. The only thing I have is the response in the WHMCS Module Queue:

    Code
    1. i-MSCP (WHMCS): SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '-1' at line 1

    i-MSCP Server:

    Debian 9 Stretch with default php 7.0 (with FPM) and MariaDB 10.1 using i-MSCP 1.5.3 (2018120800)

    Additional Plugins: ClamAV, LetsEncrypt, Mailgraph, Monitorix, OpenDKIM, PhpSwitcher, Postscreen, RoundcubePlugins, ServerDefaultPage, SpamAssassin, WHMCS


    WHMCS Server:

    Debian 9 Stretch with php 7.1 (with FPM) and MariaDB 10.1

    WHMCS 7.7.1 General Release


    i-MSCP Server has been recently upgraded from Jessie and php 5.6, to the specs written above.


    Please could someone give me some hint on how I can debug the problem ?

    There's no WHMCS log (I can see all the Others Plugin logs, but not for WHMCS).


    I Can see the request incoming in i-MSCP when looking at /var/log/nginx/access.log

    Code
    1. XXX.YYY.ZZZ.AAA - - [22/May/2019:16:46:08 +0200] "POST /whmcs HTTP/1.1" 200 200 "-" "i-MSCP (WHMCS)" "-"

    But unfortunately no further informations.

    Any help is appreciated.


    Thank you very much,

    Bye Kess.

  • An exception has been thrown after system upgrade

    Just for your information,

    I modified line 1599 in /var/www/imscp/gui/library/Functions/Shared.php

    from

    Code
    1. $possibleHostSources = ['HTTP_X_FORWARDED_HOST', 'HTTP_HOST', 'SERVER_NAME', 'SERVER_ADDR'];

    to

    Code
    1. $possibleHostSources = ['HTTP_X_FORWARDED_HOST', 'SERVER_NAME', 'HTTP_HOST', 'SERVER_ADDR'];


    It seems that $_SERVER['HTTP_HOST'] returns w00.mydomain.com4443 and this is not the result we expect. I don't know why the result is not w00.mydomain.com:4443

    So I choosed SERVER_NAME as preference...


    Now the panel is working again as expected.

  • An exception has been thrown after system upgrade

    Hello guys,

    I have the following problem after login to the panel.

    The server has been upgraded today from Jessie to Stretch and from i-MSCP 1.5.3 to i-MSCP 1.5.3-2018120800

    Everything went well, but unfortunately after the login form I can not do anything else.


    With Debug Mode enabled, I can see:

    Code
    1. An unexpected error occurred
    3. An exception has been thrown in file /var/www/imscp/gui/library/Functions/Shared.php at line 1634:
    5. Invalid Host "w00.mydomain.com4443"


    Unfortunately the logs are not telling big things… in effect the error is reported nowhere…

    This is the only thing I have.


    The list of the installed Plugins is: ServerDefaultPage, Postscreen, ClamAV, SpamAssassin, Monitorix, RoundcubePlugins, PhpSwitcher, OpenDKIM, Mailgraph, LetsEncrypt, WHMCS


    Please tell me where I can watch in order to find the cause.

    Thx for help,

    bye Kess.

  • PhpSwitcher and PHP 7.2

    Basically you should resolve it with:

    Code
    1. apt-get install libgd-dev libgd2-xpm-dev

    But the you should ensure that you don't have any broken packages or pending packages before proceeding...