Jump to content

cluster

Members
  • Posts

    37
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by cluster

  1. Debian 11
    PHP 7.4
    Blesta 5.70
    ISPConfig 3.2.10p1


    1. On package activation - > Error message: web_php_options_notempty<br /> ssh_chroot_notempty<br />
    I have no idea why this error occurs, selected in package a template (package) of the ISPConfig server which was shown in Blesta package setup

    2. I have allowed to use a domain name as username in ISPConfig, but this is blocked (regex check) in Blesta (domain.tld) contains a dot.
    Can this problem be solved by a extended regex?

    need some help to solve these problems

  2. is it possible to add an extra email template to modules in order to send it manually from the admin area?

    f.ex.
    a special abuse message in a hosting module or a final notice in the domain module that the domain name is about to expire today.
    These messages should then be displayed in the admin area under the respective service - domain names or hostings etc.

  3. I would like to place a product in the shopping cart via a direct link and from there an option for registering or transferring a domain name or using an existing domain name.
    Can I create my own additional order template for this and does that work w/ Blesta?

    add product > my order form > add domain name option (register new, transfer, use existig) > checkout

  4. 13 hours ago, Paul said:

    This error seems to indicate that MySQL crashed, are you still getting this error? If so, see that you meet the "Recommended Requirements" and options for MySQL/MariaDB https://docs.blesta.com/display/user/Requirements

    If you get past that error and still have trouble and want to get us a copy of the database securely so we can run a test import and debug in a local environment we will be able to resolve any issues and get an updated importer to you (and delete all copies of the data).

     

    Thanks that helped, the timeouts were too low ...
    I have adjusted:
    wait_timeout = 3600
    connect_timeout = 1200
    interactive_timeout = 1200


    I don't know why but the whmcs date format for all affiliate tables is different from the whmcs date format - so the affiliate page in blesta now shows an error message about wrong date format ...
    whmcs date format is set to d/m/Y but the affiliate tables use e.g. 2015-11-12

    Is there any sql query which can convert the date format in the affliate tables from Y-m-d to d/m/Y?

  5. I searched all the whmcs tables and emptied the following which did not have a valid userid
    tbloauthserver_access_tokens
    tbloauthserver_clients
    the same error message is still displayed, only customers and invoices are imported.

    I am a little disappointed that there is no feedback here ...
    I was able to import everything from whmcs in a wisecp installation (except for cancellations & domains price list).
    When will these problems be fixed in the blesta import script?

  6. Debian Buster / PHP 7.4 (fpm) / MariaDB 10.3

    WHMCS 7.10.3

    Blesta 5.2.1

     

    I have tested an import from whmcs with a few errors ...

    not imported:
    Packages, Services, Affiliates, SupportTickets, Servers, Domain price list

    Cients are imported but many inactive are shown as activ, only clients from whmcs with status closed are set to inactive, but both (closed & inactive) needs to be set as inactive in Blesta.

    The import completed but the following errors ocurred:

    importTransactions: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away on line 196

    importPackages: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196

    importPackageOptions: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196

    importServices: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196

    importSupportDepartments: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196

    importSupportTickets: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196

    importAffiliates: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196

    importMisc: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196

     

    another try w/ debug mode enabled:

    importCurrencies took: 0.0036 seconds
    -----------------
    
    importInvoices
    -----------------
    importInvoices took: 185.6431 seconds
    -----------------
    
    importTransactions
    -----------------
    importPackages
    -----------------
    importPackageOptions
    -----------------
    importServices
    -----------------
    importSupportDepartments
    -----------------
    importSupportTickets
    -----------------
    importAffiliates
    -----------------
    importMisc
    -----------------
    decrypted 0 values using WHMCS' custom algorithm
    decrypt took: 0 seconds
    total time took: 1026.206 seconds
    Array
    (
        [error] => Array
            (
                [0] => The import completed but the following errors ocurred:
                [1] => importTransactions: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away on line 196
                [2] => importPackages: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196
                [3] => importPackageOptions: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196
                [4] => importServices: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196
                [5] => importSupportDepartments: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196
                [6] => importSupportTickets: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196
                [7] => importAffiliates: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196
                [8] => importMisc: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196

     

  7. Blesta 5.2.0
    PHP(fpm) 7.4
    Debian 10

    This is a dev installation where I have activated debugging

    System > Automation
    /admin/settings/system/automation/

    shows:

    file_exists(): open_basedir restriction in effect. File(/usr/sbin/php) is not within the allowed path(s): (/var/www/my.mydomain.tld/:/usr/share/php/).
    file_exists(): open_basedir restriction in effect. File(/usr/sbin/php) is not within the allowed path(s): (/var/www/my.mydomain.tld/:/usr/share/php/) on line 110 in /var/www/my.mydomain.tld/htdocs/app/controllers/admin_system_automation.php
    UnknownException::setErrorHandler
    Line 232
    /var/www/my.mydomain.tld/htdocs/vendors/monolog/monolog/src/Monolog/ErrorHandler.php
    
    Monolog\ErrorHandler->handleError
    Line file_exists(): open_basedir restriction in effect. File(/usr/sbin/php) is not within the allowed path(s): (/var/www/my.mydomain.tld/:/usr/share/php/) on line 110 in /var/www/my.mydomain.tld/htdocs/app/controllers/admin_system_automation.php
    Printing Stack Trace:
    #0 /var/www/my.mydomain.tld/htdocs/vendors/monolog/monolog/src/Monolog/ErrorHandler.php(232): UnknownException::setErrorHandler()
    #1 [internal function]: Monolog\ErrorHandler->handleError()
    #2 /var/www/my.mydomain.tld/htdocs/app/controllers/admin_system_automation.php(110): file_exists()
    #3 /var/www/my.mydomain.tld/htdocs/app/controllers/admin_system_automation.php(143): AdminSystemAutomation->getPathToPhp()
    #4 /var/www/my.mydomain.tld/htdocs/app/controllers/admin_system_automation.php(96): AdminSystemAutomation->createCronCommand()
    #5 /var/www/my.mydomain.tld/htdocs/vendors/minphp/bridge/src/Lib/Dispatcher.php(142): AdminSystemAutomation->index()
    #6 /var/www/my.mydomain.tld/htdocs/index.php(21): Dispatcher::dispatch()
    #7 {main}

     

  8. I would like to use guzzlehttp with a panel module, but it's not installed ... how can this be solved?

    require section of my composer.json module file:

        "require": {
            "blesta/composer-installer": "~1.0",
            "phillipsdata/priority-schedule":"^1.0",
            "guzzlehttp/guzzle": "^7.0"
        }

     

  9. are my Blesta declarations correct in this part?

                'reseller_name' => $params['user_name'] = $this->user_name,
                'reseller_pass' => $params['password'] = $this->password,
                'action'        => 'create',
                'domain'        => $params['domain'],
                'hp_name'       => $params['package_name'],
                'admin_name'    => $params['username'],
                'admin_pass'    => $params['password'],
                'fname'         => $params['client']->first_name,
                'lname'         => $params['client']->last_name,
                'firm'          => $params['client']->company,
                'zip'           => $params['client']->zip,
                'city'          => $params['client']->city,
                'state'         => $params['client']->state,
                'country'       => $params['client']->country,
                'email'         => $params['client']->email,
                'phone'         => $params['client']->telephone,
                'street1'       => $params['client']->address1

     

  10. can someone help to make these whmcs declarations compatible with blesta?
    I've already adapted the first two for reseller_name & reseller_pass ...

            return apiRequest($params, [
                'reseller_name' => $params['user'] = $this->user_name,
                'reseller_pass' => $params['password'] = $this->password,
                'domain'        => $params['domain'],
                'hp_name'       => $params['configoption1'],
                'admin_name'    => $params['username'],
                'admin_pass'    => $params['password'],
                'fname'         => $params['customer']['firstname'],
                'lname'         => $params['customer']['lastname'],
                'firm'          => $params['customer']['companyname'],
                'zip'           => $params['customer']['postcode'],
                'city'          => $params['customer']['city'],
                'state'         => $params['customer']['state'],
                'country'       => $params['customer']['countryname'],
                'email'         => $params['customer']['email'],
                'phone'         => $params['customer']['phonenumber'],
                'street1'       => $params['customer']['address1'],
                'street2'       => $params['customer']['address2']
            ]);

     

  11. ### edit ###

    solved - allow_url_fopen=1

    so I guess re-captcha needs allow_url_fopen enabled

    #########

    Blesta: 5.2.0

    PHP: 7.4

    I have activated Recaptcha (v2) but  something doesn't seem to work, the Google Keys are correct even when entering the Captcha it is marked as correct ...
    so I can no longer log into the admin area because an incorrect captcha error is always shown again and again

     

  12. I have now set the date format as follows, so it's displayed exactly the same result as in the whmcs.
    blesta:
    d/m/Y > 02/10/2021
    d/m/Y H:m > 02/10/2021 10:10

    whmcs shows a different parameter (DD/MM/YY) maybe whmcs internal but results are now identical
    DD/MM/YY >  02/10/2021 10:10


    I think the date format should match before start a migration - right?

  13. It will take me a few months to finish some special modules, therefore I can wait for the official Blesta 5.1 release ...
    So I'm thinking about starting w/ 5.1 beta to set up and prepare everything.
    Is it possible to upgrade from a beta version to an official release afterwards?

    Thank you for the great work!

  14. I think I will choose Blesta and migrate from whmcs soon ?

    one more question about the invoice emails ...
    the shared invoices function what does it mean exactly?
    Is this function safe (using an one-time individual string link) ... with "safe" I mean if someone pays via the link is then the payer automatically logged into the customer account after the payment and has access? Would a css attack be possible via GET variables to access the client area from a payment link?
    I would like to use the payment link function for invoice emails if it's safe and the customer accounts cannot be compromised via payment links.

  15. is the following possible with Blesta (e.g. hooks, plugins etc.)

    1.  captcha integration into login froms

    2. Login notification for customers via email (notification for a successful login via email to the customer, incl. date, time IP address

    3. max login attempts - blocking after x fail logins

    4. blesta installation in subfolder /clients without blesta rewrite to a second /clients Folder - for now it shows /clients/clients/... when blesta was not installed into webroot

    thank you guys!

     
     
×
×
  • Create New...