Jump to content

Nelsa

Members
  • Posts

    408
  • Joined

  • Last visited

  • Days Won

    12

Posts posted by Nelsa

  1. On 9/18/2018 at 10:46 PM, ashevillewebhosting said:

    Hello - did you ever manage to come up with a solution for this? I'm dealing with the same issue and it's keeping me from being able to roll out Blesta into production.

    Hello, sorry for the late response....I did make some changes to blesta original module but after migrating to new dedicated servers I start to use an original module since there is no NAT any more....this customized module had different fields for server IP address and hosting account IP since Plesk API package has IP in Hosting section and in gen_setup section and those two are completely different parameters......can be the same but in most cases will not be. If you look in tools->logs->plesk (input for webspace:add)  after you add plesk hosting in blesta ....you will see the content of Plesk API XML package  and you will see "IP_ADDRESS" and "IPv4" with the same value..... but these values can be obtained from different fields in settings.

  2. This syntax has to.be set;

    |/usr/local/bin/php -q /home/USERNAME/domains/SOMEDOMAIN.COM/public_html.......

    So for blesta it would be something like

     "|/usr/local/bin/php -q /home/USERNAME/domains/SOMEDOMAIN.COM/public_html/blesta_directory/plugins/support_manager/pipe.php".

  3. Thing is,email address has to be hosted.on same server ...and it has to be authorative for MX record...so if your domain is not hosted on same server or it is but you use external mail server than it will not work...

    Procedure is:

    First create email address you want to pipe....than you can make  forwarders

  4. That is used when custom theme is set to load correct css...it is link generated by PHP, .when you use default theme then theme.css or theme.css?dir= will not cause any difference but if you switch to the custom theme than without dir= it will load default theme ...

    You can find it in structure.pdt

            // Theme CSS
            if (isset($theme_css)) {
            ?>
            <link href="<?php $this->Html->_($theme_css);?>" rel="stylesheet" type="text/css" media="screen" />
         

     

  5. You should have three  directories to upload languages, components, and plugins...upload all 3 to blesta root directory..than go to settings__>internationalization and you'll see additional language  and will be INSTALL...click to install and than if you want to use that language as default go to settings-->localization and change default language...your clients will have the option to select language by themselves even if you leave English as default

  6. 1 hour ago, HostKoala said:

    Hi this seems slightly misleading

     

    But from what I understand I need a $10/year subscription to use it

    @Blesta Addons

    It was free before they changed the business model..some plugins made by najhost/blesta addons were free when released and after the business model was changed some end up in paid subscription...that is why you will find that line of text in first post...

  7. You don't have to upgrade your OS or kernel for this(even it is suggested) except if you are using centos 5.x.x and even if you upgrade OS if it isn't enabled it will still be non supported ...,you need to enable  tls 1.2 and you can still support 1.1 and older ...in worst case you will have to upgrade Open SSl even you probably have one that support tls 1.2 just isn't enabled

    When it comes to hardcoding which version to use you don't do that on your server..even you can set support for only one..it is better to set widely support backward than client when connecting can hardcore which tls to use if they want..You are in the situation that many clients are connecting and some of them may use older TLS...and chippers and you don't want to reject connection..also this will not only impact payment gateways ...instead it will impact all traffic and many browsers still use older TLS

     

     

    For upgrade on centos

    SSH as root or SUDO

    yum update openssl libcurl

    Enable TLS 1, 1.1 ,and 1.2

    SSLProtocol -all +TLSv1 +TLSv1.1 +TLSv1.2

    Want remove some...just delete from command which you want

     

    You can test your SSL connection and SSL and TLS versions supported at https://www.ssllabs.com/ssltest/index.html 

  8. There are lot of payment processors that don't support hosting,seo, domains,SSL and similar services....it is unbealivable..even we have better records than most business in other niche....for example we had 3 Paypal open cases from 2014 and 2 chargebacks from users paid by credit cards many of them simple tag these categories as risky   @Paul, I suggest check this before start working on gateway...I mean why would you or any company waste your resources for a payment processor that doesn't support niche where 99% of your customers are working in

  9. 8 minutes ago, swanseahost said:

    Hi there,

    Please could someone assist me with an order form ?  I don't want or need all the details on the signup form as I am offering VPS for secure VPN traffic.  So as little details as needed would be good.

    Is there a way to just have the signup ask for a username and password ?

    Thanks

    You can use blesta universal module for this,add two fields for username and password + set it as required and users will have to set username and password on order form.These two fields will not be related to sign up form...user will still sign up for blesta account first but they will have to set username and password in service/package order form.At this way your users will have blesta account username/password different from service username/password..I mean you should have blesta user registration data to be separeted from service/package  data..

  10. 6 hours ago, EMar said:

    I don't know where exclude rules files are.

    You said you have centos panel..if you look in admin interface..under security--->mod security you will find options to enable/disable mod security..and also there will be conf files locations...if nothing is changed it should be ....

    Main Configuration --> /usr/local/apache/conf.d/mod_security.conf
    Rules Configuration --> /usr/local/apache/modsecurity-cwaf/cwaf.conf
    Disabled Rules --> /usr/local/apache/modsecurity-cwaf/custom_user.conf

     

    To edit file use command  vi /usr/local/apache/modsecurity-cwaf/custom_user.conf (to edit other file just change file location after vi) ,after that ...when file is opened click on i (short for insert) and than you can edit content,when you are done first click on ESC ..than press left shift + q ....than enter wq and hit enter .If you are not good with ssh just install WINSCP and than you can download file..edit it and upload again in one minute using GUI

     

  11. 4 hours ago, EMar said:

    Thanks but I know the main php ini is at /etc/php.ini

    As far as i know I need the paths to 

    /etc/php/7.0/cli/php.ini
    and
    /etc/php/7.0/fpm/php.ini

    Which don't exist at these locations.

    Maybe they're not installed fully or they exist at a different location.

     
     

    Change path to ini file in your command from /etc/php/7.0/cli/php.ini  to /etc/php/7.1/cli/php.ini if you have installed  mailparse for php 7.1 , the same thing should be done when you install mailparse for php 7.1 and any other php...liike 5.0 ,5.5 ,5.6 etc with difference that lower PHP version will require lower mailparse version due min. requirements every mailparse version require

  12. To be completely clear,if you have two zip files after download than lufti-blesta.zip contains blesta template and it should be uploaded to blesta templates directory..if I remember correctly it is app/view/client ,than go to settings and activate this template and you will have it on your blesta installation..including portal.

    Second zip file lufti-html.zip is simple html website , it should serve as front-end and it is not required...it is optional if you want to have website same as your blesta installation,and you handle these files as you would any html website..I don't know what is included in this lufti-html.zip but I suppose there is few html.files few directories with images,CSS,js etc..

  13. 8 hours ago, techTD said:

    Hi BlestaStore

    I used blesta portal plugin to put index.html code from Futfi theme, however I got double header, double menu and the result is not full width page.

    I guess I have to remove header part from index.html or edit some file to remove header. any pointer please?

    Please see the attached file.

    Regards

    TD

     

    Lutfi_Home.JPG

    I don't recommend you to swap index.html by simple inserting code in portal box...if you have blesta in domain root directory than just disable portal and upload html files to root directory and in same time activate this template.Reason why you have two headers are because header is already included once in template structure.pdt ,index.html and other html files are not part of blesta template at all...it is front-end html website theme included as all-in-one integration.So html files should be uploaded in your website root directory and if you have blesta in root directory than disable portal and it should work....

  14. 10 hours ago, MineHarvest66 said:

    Hold that thought... Even Cpanel provisioning doesn't have 100% support. The only module that I know that does is Vituralizor and I believe that they made and maintain the module.  

    So in regards in automating Shared hosting and such you will get be able to do so but with limitations. 

    I don't understand how cPanel and Plesk shared hosting module doesn't  support automation??From ordering to account creation there is no need for manual handling,...client order package and after client pay invoice..account is auto-provisioned, activation email is sent and that is it....there is no need for any manual handling ...

  15. I had also issues with upgrades few times on php 7, then I started to follow one simple procedure ... 1.overwrite files with new one  2. switch back to php5.6   3. start upgrade process CLI or WEB(doesn't matter)   4. apply hotfix php7 and switch to php7 . 

    With this approach, I never had problems(today upgraded from 4.1.0 to 4.2 ) while uploading hotfix php 7 after overwriting and then starting upgrade throw up an error (...files encoded with 5.6...etc).Now I didn't go deeper into this issue since this approach works fine for me.

×
×
  • Create New...