katycomputer

Thanks guys, dashboard now says: Your support and updates are good through Jan 04, 2021.

Hello blestars
My 2 cents on this mater  
We are ditching cPanel for good, mass migrations servers to Virtualmin, the Virtualmin handle 100% cPanel Backups restore witout any issues and so we only need to point the DNS's to the new servers

We only made a few changes on Virtualmin. On Webmin, we add ports 2096/2097 to redirect to Usermin port 2000 and 2086/2087/2082/2083 ports to Virtualmin port 10000

We also pré-installed on the hostname phpMyAdmin and RoundCube with the Mobile Theme (https://github.com/messagerie-melanie2/Roundcube-Plugin-Mobile) to all users have normal acess to a known Webmail and MariaDB Database managment  (Virtualmin alredy bring there own DataBase Managmente and Webmail software). and add a Link on Usermin Painel to open RoundCube Webmail
Finally we add CSF Firewall like so:
cd /usr/src rm -fv csf.tgz wget https://download.configserver.com/csf.tgz tar -xzf csf.tgz cd csf sh install.sh - Install the csf webmin module in:
Webmin > Webmin Configuration > Webmin Modules > From local file > /etc/csf/csfwebmin.tgz > Install Module (sometimes because the webmin cache we have to make this step twice)
After you install the module, you can simply log in to Virtualmin, chick on Webmin (top left) and then: System > ConfigServer Security & Firewall
Also we add PHP verions 5.4, 5.6, 7.2 (now by default virtualmin alredy brings php 5.4 and 7.2) 
#we install remi repository to add more php versions and modules yum install http://rpms.remirepo.net/enterprise/remi-release-7.rpm yum install php56 php56-php-bcmath php56-php-cli php56-php-devel php56-php-fpm php56-php-gd php56-php-mbstring php56-php-mysqlnd php56-php-opcache php56-php-pdo php56-php-pspell php56-php-xmlrpc php56-php-memcached php56-php-iconv php56-php-zlib php56-php-mcrypt php56-php-simplexml #you cann add/remove extensions abose :)  
We also add ioncube like so:
cd /usr/local wget https://downloads.ioncube.com/loader_downloads/ioncube_loaders_lin_x86-64.zip unzip ioncube_loaders_lin_x86-64.zip rm ioncube_loaders_lin_x86-64.zip And add to php.ini on Virtualmin the line for exemple for php7.2
zend_extension = /usr/local/ioncube/ioncube_loader_lin_7.2.so To start migrate you can do it on Virtualmin GUI or on CLI, on CLI (https://www.virtualmin.com/documentation/id%2Cvirtualmin_for_cpanel_users) you can make a batch file with mass import in a very easy way like so:
virtualmin migrate-domain --type cpanel --source /home/cpanel_username_backup_file.tar.gz --user cpanel_username_here --pass 'cpanel_username_password_here' --webmin #for multiple just add a .sh file with a somethin like this: virtualmin migrate-domain --type cpanel --source /home/cpanel_username_backup_file1.tar.gz --user cpanel_username1_here --pass 'cpanel_username_password1_here' --webmin virtualmin migrate-domain --type cpanel --source /home/cpanel_username_backup_file2.tar.gz --user cpanel_username2_here --pass 'cpanel_username_password2_here' --webmin virtualmin migrate-domain --type cpanel --source /home/cpanel_username_backup_file3.tar.gz --user cpanel_username3_here --pass 'cpanel_username_password3_here' --webmin #and so on... Its more easy and less troblen then DirectAdmin, Plesk or even Interworx
Common problems after migration:
#Error 500
.htacess file with the directive "Options +FollowSymlinks" just comment that line
#Rong php version (client can change PHP on Virtualmin painel)
#Some notes for anyonw that never try Virtualmin/Webmin
Virtualmin/Webmin (port 10000) Root = WHM (so many features that in the first time we "lost" inside, but the more time we spent the more you will likeit, its a lot better and more mature then cPanel)
Virtulmin/Webmin User (port 10000) = cPanel (A lot more options than cPanel)
Usermin = Webmail (but with a loit more option like POP/IMAP external emails sincronizing and SPAM filters more advanced than cPanel)
The only thing is that dosent support CloudLinux (its not a downside) and dosent support Softaculous (Virtualmin has is own Software inside that you can add toyr own scripts or buy the Pro License that is 200$ per year with unlimited accounts)
The GPL verion dosent support Reseller accounts, but you can bypass this if you dont want to spend now any money, just creat on Webmin New users with permissions to only acess there clients accounts, is like a Reseller accouny but witout any limit on creating, or do it like us and create for each reseller a VPS or CLOUD server for that reseller maybe is cheper than buy a Virtualmin Pro license, on this critical fase  
Any problems or any douths you can ask me and I will try to fill in  

P.S- We are migrating more than 5k clients from cPanel to Virtualmin and we have tested a lot Virtualmin since last year iin migrations and compability (we have several CLOUD on production with dozens of clients with CentoS 7 + Virtualmin), because of our new CLOUD platform that we have created. 

Periodically, when I login to Blesta, it reports "Your license successfully revalidated. Please log in."
I then have to login again - is this really necessary?  It seems to be a needless aggravation. Additionally, I have a lifetime license, why is Blesta validating my license if it's perpetual?

I found this thread thinking "I am going to remove the branding". I have reconsidered.
We would all be better served by leaving the branding in place. If Blesta is more popular, we'll get more resources devoted to Blesta. A Chevy is less expensive and more reliable than a Cadillac, one of the reason why is because they make more Chevy's. I want more people, many more people to buy Blesta!
I don't see how it hurts my business to promote Blesta within our billing system - my homepage, that's a different story, no web designer gets to put "designed by..." on my homepage.

I found this thread thinking "I am going to remove the branding". I have reconsidered.
We would all be better served by leaving the branding in place. If Blesta is more popular, we'll get more resources devoted to Blesta. A Chevy is less expensive and more reliable than a Cadillac, one of the reason why is because they make more Chevy's. I want more people, many more people to buy Blesta!
I don't see how it hurts my business to promote Blesta within our billing system - my homepage, that's a different story, no web designer gets to put "designed by..." on my homepage.

Provider "B" is alive

Provider "B" is alive

Yep.. just to be extra clear, as an addon to Tyson's post. If we re-encoded the files for v3.6 with the ioncube encoder for PHP 7.0 or higher, it still would not work. It's not a limitation on the software, Blesta 3.6 will not run under PHP 7. We spent a lot of time and effort with Blesta 4.0 to add support for PHP 7, which included a major framework update.
There's no reason anyone should be running EOL software (See https://docs.blesta.com/display/support/End+of+Life+Policy). I highly recommend upgrading to 4.3.2.

Just wanted to chime in here that the Blesta version 3-series (e.g. v3.6.0) will never support php 7+. It simply can not. There are backward incompatible changes introduced in php 7 that prevents Blesta v3.6 from being runnable on that version of php.
In order for Blesta to support php 7+, Blesta must be updated to resolve those backward incompatible php 7 changes, and in so doing has to introduce backward incompatible changes in itself. This means that in order to support php 7, an update to Blesta requires a major software release (i.e. moving from version 3.x to version 4 following semantic versioning standards). This is precisely what we did do by releasing Blesta v4.0, and with that version you can run php 5.4+ or php 7+ using the provided ioncube-encoded files for php 5, php 7, or php7.1+ respectively.
Ioncube itself does not support php 7+ with its php 5 encoded files, so that's why different encoded files must be used for your particular php version.

@bjacksparow I suspect everyone is taking Blesta's side on this one because the fee for support is so reasonable - $39 per year, I too would be grouchy if it was $390  per year, but it's not. Phillips charges a very reasonable fee for an essential tool. We want this software to be successful, it can't survive if its customers look for every conceivable way to avoid supporting the product.
 

It will take more then ion cube encoded files, to get software to run on PHP 7x that was designed to run on PHP 5.6.

cPanel released PHP 7 into cPanel about 1 year after Blesta 3.6.1 (which was released about 2 years ago).
You can not expect support for newer PHP version/s in older software. Sure if Blesta 3.6.1 was the current version, I would expect it to run on PHP 7 but Blesta  3.6.1 is an older version.
You really need to update if you expect it to run on the newer PHP version/s.

So if you upgrade your ram from DDR3 to DDR4 it's the motherboards fault for not taking the ram?  They should make it fit and work?    Because we aren't talking about a minor build update here we are talking about a major version/release change.
If you don't want to pay to upgrade, just run PHP 5.6.  If you want to update your PHP,  you need to update your Blesta as well it's as simple as that.
Get a cheap VPS, put PHP5.6 on it, install blesta, or go to a webhost that provides mulit PHP.  cPanel, Cloudlinux and I'm sure other panel software also provides the user with the choice on PHP version.
 

Please let me know how they made changes that broke it?  The software was released for PHP version 5.6.  It still works on the PHP version it was produced for they didn't break anything.  Your choice of PHP install is what is causing the problem.
FYI: Blesta 3.6.1 was released one month before PHP7 was even released, and a long time before control panel software added support for PHP7.
https://www.blesta.com/tags/3.6.1/
https://en.wikipedia.org/wiki/PHP
Side note but I wish Wingcommander/Privateer still worked on my current PC (without an emulator), wonder if I should message them and tell them to update for me?

Right here, this is the answer....
You do NOT need to update - you do however, need to also NOT update your PHP version.  You can't update one without updating the other.  As I have already said just run PHP5.6 and you will have no problem.
 
I won't be replying to this thread anymore as I feel it will go nowhere everything that can be has been answered already.  Good luck.

Best answer: renew with OpenSRS, then transfer to NameCheap, you don't "lose" the 12 months of domain registration, it gets tacked onto your NameCheap registration.
 

Best answer: renew with OpenSRS, then transfer to NameCheap, you don't "lose" the 12 months of domain registration, it gets tacked onto your NameCheap registration.
 

Why don't you find out what it will take to update to latest & greatest? Blesta pricing is very reasonable.

Hi @bjacksparow,
Why not just run PHP 5.6?  If your host doesn't support it, find one that does.  The better option as @katycomputer has pointed out would be to upgrade your blesta license and install the 'latest & greatest' aka current version.

Thanks Paul - going back to default resolved the issue.

If you're familiar with php you can update /components/reports/aging_invoices/aging_invoices.php to alter the data export for the AR report.

Here' is the default conditional for the auto debit message:
{% if autodebit %}{% if invoice.autodebit_date_formatted %}Auto debit is enabled for your account, so we'll automatically process the card you have on file on {invoice.autodebit_date_formatted} unless payment has been applied sooner.{% else %}If you would like us to automatically charge your card, login to your account at http://{client_url} to set up auto debit.{% endif %}{% else %}If you would like us to automatically charge your card, login to your account at http://{client_url} to set up auto debit.{% endif %} It looks like you just removed the else statement, so it'll either show that message or nothing. I'd suggest putting something in between the autodebit and invoice.autodebit_date_formatted conditionals as a test to see if it is output, which will show whether autodebit is boolean true.
We have a task - https://dev.blesta.com/browse/CORE-2770 which is designed to catch cases where auto-debit is enabled but there is no account set for auto-debit. I don't think this is related to your issue.
The only other thing I would suggest is to try toggling auto-debit off and back on. If the value is not set for some reason, it may appear on anyway. If you toggle off and back on, it will ensure the setting is present.

PayJunction does not allow web hosting providers? I remember when BluePay pulled this nonsense. I complained, dropped them as someone we recommend, and then they were acquired by someone else. They called me, told me that they no longer block hosting providers, and apologized.. but I can't trust them now. They dropped one of our customers for doing web hosting. That's insane. Web hosting does not equal selling crack. Do you have an email contact at PayJunction?

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

Stripe is continuing to support hosting businesses. Just got in contact with them.