HostingforPixels

I've been doing some more testing tonight to understand which versions of Blesta work and when the issue starts manifesting itself. 1. Blesta 4.1.1 - No Issues. Works repeatedly with 15 Plesk Service Plans. 2. Blesta 4.3.0 - No Issues. Works repeatedly with 15 Plesk Service Plans. 3. Blesta 4.3.1 - Fails to populate Service Plan drop-down when Plesk Server has more than 4 Custom Service Plans. 4. Blesta 4.3.2 - Fails to populate Service Plan drop-down when Plesk Server has more than 4 Custom Service Plans.

Just some quick observations; 1. All of my Plesk Servers, with 15 Service Plans, have been working in a Production environment with Blesta 4.1.1. All 15 Plans + the default 'Admin simple' are displayed in drop-down. 2. I tried copying version 2.4.0 of the Plesk Module in to Blesta 4.3.2, and it experienced the same problem. So problem maybe not with the module itself!

Yes. I can confirm that. Five Customised Plans added on the Plesk Server kills the drop-down, four works. I tried the Plesk example API PHP code a couple of nights back and that worked from the Blesta Server. I copied the two PHP files in to the Blesta Directory and ran it from the command line and from the browser and it worked. That was a server with 15 plans. So maybe this is something on the Blesta side! We need someone with more knowledge to investigate this ...

Sorry. Just saw your response after I sent my reply. Yes. I think you've discovered the cause of the issue. But now we need to work out how to solve this!!

Hi Ashevillewebhosting, I have 15 customised Service Plans on all of my Plesk Servers! I think you just stumbled on something interesting but I'm not sure where this leaves us! I just switched my settings in the Plesk Module to a server that was ready to go, but not urgent, with the 15 Service Plans set-up. I tried adding a package in Blesta and it failed. I then deleted all 15 Service Plans form the Plesk Server and tried adding a package, and it worked. The Service Plan drop-down listed the 'Admin Simple' default plan! I then added a new service plan on the Plesk Server and that is now in the drop-down!

So Blesta/Plesk are communicating fine via API... any ideas? ......... Ashevillewebhosting, I see the same thing. Although I don't have any packages, if I go into the Plesk Module settings and enter an incorrect password for the Plesk Server and try to add a package. The Module Log shows the output error from the server indicating that the password is wrong, see snippet pasted below. If I correct it, it goes away. <?xml version="1.0"?> <packet version="1.6.9.1"> <system> <status>error</status> <errcode>1001</errcode> <errtext>You have entered incorrect username or password.</errtext> </system> </packet>

Thanks Nelsa and ashevillewebhosting for your replies. I tried looking at the network tab in dev tools tonight and everything looked fine. All green, no broken connections. This was really frustrating because it was something I hadn't thought about and I got my hopes up that it would be the issue. One of the things that I find strange is that I can reinstall my server with Ubuntu and Blesta 4.1.1, select the Plesk module, and try adding a package and the select plan drop-down will populate immediately - everything works! I can then do another reinstall with Blesta 4.3.2, select the Plesk module, try adding a package and never see the drop-down populated. I can repeat it, again and again, and the same thing happens. Something very odd is happening, and I can't figure it out - I think I will have to go back to just using 4.1.1 and forget about ever upgrading! Like you ashevillewebhosting this is now stopping me from moving forward with new releases.

Hi everyone, First, I wanted to highlight that I have seen this issue mentioned recently in another post, but the problem didn't occur on a second server, so it was viewed as a server issue! The problem I'm seeing is repeatable across installs, and across different servers. A bit of background - I've been running a modified 4.1.1 Blesta install for months now which has been working flawlessly with three Plesk Onyx Servers. I didn't update because of the modifications made. I decided following the updates to 4.3.2 that I wanted to be able to update my installs so I created some scripts to automate some mods, and phased out some other mods allowing me to upgrade following the normal process with no worries. I decided to test 4.3.2 on a test server dedicated to Blesta, which is 'connected' to another test server running Plesk Onyx. The test set-up had also been running 4.1.1 without problem. Both servers run Ubuntu 16.04 configured to use PHP 7.0 and do not have issues with NAT IP's, etc. NOTE: From this point forward I am discussing the test servers and the installs of both 4.1.1 and 4.3.2 are 'Vanilla' installs with no modifications. As such the Plesk Modules are versions 2.4.0 and 2.5.0. The installs were performed on the same Blesta server and were fresh installs of Ubuntu and Blesta. The installs were performed by a script that has been carefully tuned over a few weeks of use to install Blesta. The only step remaining after the install is to enter the license and staff details in the browser. This script was used to install both versions of Blesta. The only modification to the script is a variable to tell it which Blesta version to pull in for the install. This means that the steps are performed in the same order and PHP modules, etc meet the requirements for Blesta. The Blesta folder included the PHP 7.0 HOT FIX update. 1. The Problem I installed 4.3.2 as explained above. No problems were observed during the install. I logged into the dashboard, checked that all widgets were loaded, that cron was working and completed a basic set-up e.g company name. Next I installed the 'Plesk Module', set-up a Server Group called 'Plesk Servers' and added my Plesk Test Server - Label, IP address, username, password. No problems were encounter so far. Next I went into 'Packages' > 'Browse Packages' and selected 'Module' - Plesk, 'Server Group' - Plesk Servers, and 'Standard' account type. Finally, I expected the 'Plesk Service Plan' to be populated but it never was. It just showed '-- please select --'. This was never updated at all following repeated reloads, etc. The Plesk Module Logs showed; 45.xx.xx.xxx|service-plan:get a:1:{s:6:"filter";a:0:{}}. (Input, Success). No Output was observed, but this has always been the same on the 4.1.1 production servers. If I altered the 'Plesk Server' password to be wrong I observed the following output in the log indicating that successful communication with the Plesk Server API was occurring. 45.xx.xx.xxx <?xml version="1.0"?> <packet version="1.6.9.1"> <system> <status>error</status> <errcode>1001</errcode> <errtext>You have entered incorrect username or password.</errtext> </system> </packet> 2. What was Checked Obviously, I assumed that the install was to blame. So I checked; 1. The logs for any errors. None observed. 2. The PHP Extensions were all checked. 3. Checked the CURL SSL CA-Certificate and SSL operation - fine. 4. Checked OpenSSL CA-Certificate settings in php.ini - fine. 5. Checked phpinfo output - PHP 7.0 installed, all extensions ok, IOCube installed. 6. Blesta Logs checked - no errors. 7. Copied Plesk API PHP example code into Blesta directory and ran on the CLI and in browser. Result was correct interaction with Plesk and a list of api versions outputted. 3. Repeated 1. with Blesta 4.1.1 Point one was repeated step-by-step with a Blesta 4.1.1 zip including PHP 7.0 Hot Fix. It was installed on the same server, installed with the same script, and set-up in the same sequence. The 'Plesk Service Plan' drop-down was instantly populated - no errors observed. Add Packages was fully configured and saved. This process was repeated with several alternating installs of 4.1.1 and 4.3.2. The results were always the same. 4.1.1 worked every time. 4.3.2 never updated the service plan drop-down. 4. Tested on a New Server The above was repeated on another server with exactly the same results. The server was with another supplier but still running Ubuntu 16.04 with PHP 7.0. The same install process was used and the same results observed. Any one have any ideas of where I'm going wrong with 4.3.2? I haven't seen any mention of changes to the set-up process. Thanks for your help. Gary

Hi everyone, I'm currently going through and trying to ensure that my VAT settings are working correctly. I think I understand how everything works in Blesta! Being based in the UK I have to play with the wonderful EU VAT regulations and the differences between individuals, businesses, with a TAX ID, or with no TAX ID! My problem is that I can't determine from the many forum posts exactly what the current EU VAT capabilities are within Blesta! Are they complete? Are there holes still? I saw one forum post from 2015 where Paul appeared to confirm that they were going to sort the problems. Did this happen? If not, how do you guy's in the EU handle VAT in Blesta? Thanks for your help. Gary

Hi, thanks for the response. Yes. I think you're right about the Plesk Module not supporting configurable options. That is why I wanted to use add-ons instead. I can configure the add-on group and link it to a hosting package. But the add-on needs to be a separate service plan in Plesk. This means that if the main hosting package is selected at checkout, with no add-on, I want service plan A to be created by the Plesk Module. BUT, if the add-on is checked I want the Plesk Module to create service plan B, but not A.

Morning everyone, I have a working hosting platform with Blesta using the Plesk Module to create subscriptions in Plesk Onyx. I have a query about add-ons. I understand how to create them now, but I'm not exactly sure how they work in reality. I could experiment but thought it might be quicker to ask a question here. As an example, if I have a package in Blesta called 'Standard Hosting' which sets up a subscription in Plesk of the same name everything is fine. I want to include an add-on which adds additional software in Plesk. This means that I need Blesta to trigger a Plesk Service Plan if the option is selected? But I'm not sure how add-ons work. If at checkout it says product + option what will Blesta attempt to set-up in Plesk. The main product and the add-on, or the add-on? What I'm after is if main product is selected only then 'main product' service is setup in Plesk. But if add-on is selected 'add-on service' is selected. But not both! Hope this makes sense? Thanks. Gary

Hi Michael, I sent my hostnames via a support ticket and Paul sorted the license problem immediately. Thanks. Gary

Hi, I have purchased a multi-company add-on and have successfully set-up multi-company through the admin panel. The drop-down in the top-right hand corner lists both companies and selecting a company displays the correct admin panel, etc. I have set-up the DNS settings so that myaccount.company.com works for both. The problem is that I keep getting an invalid license message. If I enter the license it then fails for the other company. Am I right in assuming that the main license for the first company in my account is updated for both? or should I be using a different license code for each company? If the second is the case then I'm can't see where it is listed. Any help with this would be great. I am sure it is just me missing something! Thanks. Gary

Hi Michael, sorry for the delay replying. The last couple of weeks have been a bit crazy! I rebuilt my Blesta server using a standard LAMP installation and everything now works as intended. I had used EasyEngine to create the basic server set-up, which is python based tool intended for creating WordPress installs, which can also be used to create a basic server using NGINX. Obviously, something in the set-up wasn't right, so I went back to good old Apache!

Hi Michael, sorry I meant to mention in my post that I had reverted back to the Bootstrap theme and exactly the same issue occurs! I'm on Site today so can't try anything until later. To be honest I think it's a server issue. I used an Easyengine plain site install to get the server up and running and I'm considering going for a straight LAMP setup - this is just a development server! just wanted to highlight it to save time, if anyone else had seen it. Thanks for the comment though. Gary