Nelsa

Well Error: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away is common issue with many shared hosting providers,mostly problem is low limits for one or more variables in mysql configuration file my.cnf , in most cases if you incrase wait_timeout and/or max_allowed_packet it will resolve issue and in case when problem is timeout even incresing php settings can solve issue but again only if it is timeout issue but it is very rare..since you can't really get much with php tweaking...ask provider to incrase these values if server is not under your control

First step Install Plesk module (settings-->module-->available-->install plesk module Step two,add your VPS as Plesk server (set admin as username or root and admin/root password as password,in IP field set public IP you set as shared IP in plesk) Step 3,add package..there you have to set name and description of your package,in module option select plesk....in server group field check any ...than service plan field will be available...select one you want to sell.Than set pricing,in field term you need to set 1,2 or any number you want to be....than select period month or year...etc....than set currency and price,setup fee...After you set first billing period ...for example 1 month price 2.00$ setup fee 0.00 Cancellation Fee 0.00 ,you can add additional price..for 3 months ...6 months..1 year..etc. Next thing would be welcome email template(when account created your client will get it)..this is something you can find here at forum and edit to fit your needs or write yourself.Than you need to assign package to at least one group(can be assigned to more than one),if there is no groups available create new group...just select option create group and name it..like Plesk hosting...Web hosting...Linux hosting or what ever you want..After that click on create package and you have package....But now you need order form...To create order form navigate to packages--->order form and at right side clcik add option.... There you need to set few things...name and label(used also as url string)are first two...name will be also title ..you can set for example name Plesk start ..label plesk hosting...or what ever you want...Next two fields are visibility and type,these fields are by default set to public and general and this is what you want to set if you want this package to be only for hosting plan only(or any other service/product only)...if you want first domain search and order form to be shown than hosting plan you need to set domain and other as order form type.Also there is client registration type..as name suggest,no order form..just registration form.Next is order form template or widget,you can select any of available.....Than you need to set default client group,by default set to users and than there are few checkbox fields and one tex box..there you can select will you force https on order form,will orders wait for manual review ,allow cupons..and url of terms of service(required only if you check " Require Agreement to Terms of Service ) ... Last thing is package group....here you will see group you created when hosting package is created but groups also can be created if you navigate to packages--->package groups.After this click create order form and that is it...you can now also,on same page "order form" navigate to settings and select default order form and few more options...After this your first package will be available at this order form..when you want more packages to be at same order form/page,create more packages and at last step,before click create packages,don't create new package group...instead add package to same group. To be more clear here is logic behind....you have package groups....to these groups you will assign packages(for example plesk hosting group will have few plesk packages...cpanel hosting groups few cpanel packages..etc)and than you assign one or more group/s to order form..for example you add two groups..Plesk hosting and cpanel group...than you add 3 plesk packages to plesk hosting group, and 3 cpanel packages to cpanel group....now you add new order form named web hosting and assign plesk hosting and cpanel hosting groups to this order form...when you visit this order form url you will have 6 hosting packages offered...if you want instead to have two order forms,one for plesk and one for cpanel plans than you will add two order forms and assign one group to each order form.

What do you mean by six different reseller accounts??If question is related to 6 different web hosting or domain reseller accounts than you can have as many as you wish/need...One blesta license covers one company but this is related to your company/brand,when it comes to service/products that is something handled by modules and you can add 10 different web hosting reseller accounts as 10 different servers...or you can also use 5 different domain reseller accounts to provission domains.So there is no restrictions on how many cPanel/plesk/direct admin..etc servers you can add(and you can add any server with root or reseller ceredentials).So,as I said,service/products are handled by modules..cpanel module,eNom module..etc but under every module you can add multiple accounts/servers(depending what is handled).

When you run cron manually not all tasks will be executed,there are many tasks sheduled to run at certain time or time period,in your case 2 of 3 tasks run once per day...

If there is no paypal as payment options go to order form settings and allow payments from paypal,also in paypal gateway settings make sure corect currency is enabled. After order is made,in checkout process ...first.... payment methods will be listed.....than on next page paypal buttons(if paypal is selected).In case you can't see paypal listed as payment methods than you will have to edit order form and and set paypal as one of the payment methods...

Two buttons should be presented at checkout/confirm payment page ,one button will be labeled as checkout and second subscribe...

You have to change php version or apply hotfix...change to php 5.6 or find hotfix for 7.0 and upload files(and replace existing).You can find hotfix in any blesta installation zip file,you can't miss since directiries are named hotfix-php7 but just in case here is hotfix attached to this post, upload it to blesta installation and extract with the option "replace existing"checked. app.zip

We had new domain manager scheduled for 4.0..than re-scheduled to 4.1....what happens after that I don't know

Oh, ...it is not that what you think...server is already port forwarded problem is because before creating webspace/hosting account there is validation process to check is IP address of future hosting account existing on the server and because public IP fetched from module settings is checked and compared with server IP which is private IP...there is mismatch and as result only client is added to Plesk without hosting account. When it comes to questioning why someone want NATed server... ....providers use different cloud or virtualization environments and software and most of these are designed to provision NATed servers....it is not like you have the option..even you can search for provider that offer for example VPS without NAT but NAT has own advantages and some users want it for many different reasons...this is simple problem with Plesk module. @theone85ca Google cloud is worst option for servers you intend to use for selling hosting,I must say they have most idiotic practice on the planet..they provision servers with not only blocked outgoing port 25(which should be only port blocked when want to disable users to send from SMTP servers)but they also block 587 and 465 ports which disable relaying..and worst thing..in next paragraph they recommend SendGrid, Mailgun, and Mailjet but any of these to be used you have to relay for which you need port 465 and 587...I have really said opinion about their staff who do this and write https://cloud.google.com/compute/docs/tutorials/sending-mail/ Edit..they seems they corrected this thing with ports 465 and 587..I have server there and remember they had blocked ports for relaying while suggesting to use it When it comes to plesk server behind NAT and blesta...you have two options...implement this tweak suggested at previous page and after that, it will work on auto pilot or you can add private IP as second IP in Plesk(put private IP in first field while leaving a second field reserved for mapping IP empty) and in this case blesta will create account but you will have to go to plesk and switch to first IP manually every time new account is created since domains will be linked to wrong IP and when you visit any domain it will just show default plesk page every time instead files from hosting account.

I know...but that was not case I was talked about...this case is when you have one/same server with 5 IP address for example and you want set one IP for first package....than different IP for second.... Also this issue with NATed server is only related to Plesk module....Also I never looked how WHMCS handle this and as I remeber there we didn't had issues with NATed servers while we used WHMCS....I just can't remember does plesk module in WHMCS has field list of IPs like it has in cPanel module and did I have to set private IP in this field. It was long time ago,I moved to Blesta in 2014 while WHMCS 5 was latest version..but I know I didn't have to edit module in WHMCS for NATed servers.

Yes,that is how most people do...you can also add same server twice with different ip and than when create package just select that server for that package...But there is space for improvements ...for example module can be adopted so user can specify list of IP and than when creating new package, in service options select IP from that list for that package....But for us was important to have module that can auto provision new accounts without intervention on servers behind NAT.....amd that was not possible. Without this customization only way to make module to work was to add private IP manualy in Plesk as second IP ...only reason this IP has to exist is because plesk will not create webspace if IP is not on the list of IP....and for some reason it doesn't reckognize public IP as one of server IPs....in fact I know reason....it is because when comparing this ipv4 with server IPs....private IP is fetched for comparation.... This was very ugly solution.... problem was everytime new account is created you had to go and manualy change IP from that private IP to right one...Because of this I started to look for better solution...

Plesk API xml request package for add:webspace has two fields for IP address...one is server ip and second is hosting account IP...this is logic because you may want to have different IP for hosting accounts...doesn't have to be related to NAT...if you look other billing scripts for this niche they have separate fields for IP list and server IP/hostname used for requests and internal script usage...So Plesk API xml include ip_address and ipv4 but there is big difference how these two are build in module....while ip_address value is taken from module meta row which itself is value you put in module settings ip field.....second parameter ipv4 is simple ipv4=ip_address ....and those two are in completly different section of XML request....ip_address is part of general/gen_setup section where general information about webspace is provided like user name,phone,login ..etc...second section hosting is where specific hosting features are specified and one of fields is ipv4....So generally this ipv4 can be set also to be populated at same way like ip_address but you have to first add new field to module settings template and than set ipv4 to be taken from there....so when it comes to your question "what happens if you change order"...it will happen that your request will fail if you put private IP in ip_address since it is used as target for post request....if you set different public IP it will work if it resolve to right server...If you want to have second ip optiona than it can be implemented in module with one simple IF statemen before existing code for ipv4 and than new code put in IF and existing code leave after IF as it is...otherwise you will have to put same IP in both fields if server is not behind NAT. But again this has usecase also when server is not behind NAT but you have more IPs... Anyway this was my adhoc implementation which doesn't require big changes to module...and it worked for us few years...I did say I will publish this plugin but since changes are so small I didn't see.any logic to publish this as new plugin...or even as hack.

As I see you already saw old threads ...there was few reasons this happened to me...and you can use Mozila or Chrome developer tools ...in mozila go to inspector than switch to network tab and find POST request for module/service/options(or something like that...will se it broken..completed request will be green)and check response...on servers I had this issue...in most case it was error "oh no mysql has gone...." And this was resolved with increased mysql_wait_timeout and/or mysql_allowed_package

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.

You have to add TLDs by yourself..if I remeber correctly there are only 3 tlds by default ..there is file universal_domains.php in components/modules/universal_domains/config/ and there you can add TLDs you want to sell in array and than it will be visible on order form.

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".

Give me few minutes ,I have direct admin demo somewhere...I will check and give you instructions...

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

You can set pipe from domain also, create e-mail first than set forwarder

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" />

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

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...

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

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

Did you change php version?Check version,maybe host owner is changed php version(if you don't own server)