Plesk 17.8.11 Help

ashevillewebhosting · August 23, 2018

Hi,

I just installed Blesta 4.3.1 on my Plesk web server to give a try. I used the following guide to install the module and add new packages: https://docs.blesta.com/display/user/Plesk

However, when I go to add a new package, the 'Plesk Service Plan' dropdown never seems to populate? Anyone out there familiar with this or how to fix it?

Thanks!
Justin

Paul · August 23, 2018

The most common reason for this is that your Plesk server is not able to be reached. Please check that the credentials are correct, that CURL SSL is in your PHP, and that the required ports are open at your firewall egress TCP. You can also check the module log under Tools > Logs > Module, and the system file logs (usually ../logs_blesta/) which is defined under Settings > System > General.

ashevillewebhosting · August 23, 2018

Thanks for writing back!

The credentials are good, and the module logs just say 'success'. I did have an open_basedir error in blesta general-warning-2018-08-23.log, so I set it to none. I'm seeing this in the general-notice-2018-08-23.log: [2018-08-23 20:56:12] general.NOTICE: E_NOTICE: Trying to get property of non-object {"code":8,"message":"Trying to get property of non-object","file":"/var/www/vhosts/ashevillewebhosting.net/httpdocs/blesta/components/modules/plesk/plesk.php","line":2261}

Are they're any unique firewall ports to be opened? This instance is running on the same server I'm trying to set up in blesta if that helps.

Tyson · August 23, 2018

1 hour ago, ashevillewebhosting said:

I'm seeing this in the general-notice-2018-08-23.log: [2018-08-23 20:56:12] general.NOTICE: E_NOTICE: Trying to get property of non-object {"code":8,"message":"Trying to get property of non-object","file":"/var/www/vhosts/ashevillewebhosting.net/httpdocs/blesta/components/modules/plesk/plesk.php","line":2261}

This would be the problem. It looks like Plesk is not responding with a valid result, or it's timing out, etc., and then that error is encountered because that "response" is unexpected.

When looking at the logs under Tools > Logs > Module, click the table row to expand that particular request to show all Input/Output. It would be useful to know if any of the Output records have an error status, and what the response is in that case.

ashevillewebhosting · August 24, 2018

Thanks Tyson,

The Tools > Logs > Modules doesn't seem to be much help, I just have the same entry repeated (attached). Not sure where to look next.

Tyson · August 24, 2018

Looks like the response from Plesk wasn't logged, perhaps due to another error.

Unfortunately, some debugging is necessary to see what's going on. Let's begin by trying to determine what Plesk is responding with.

Could you update the file /components/modules/plesk/plesk.php?
Toward the bottom of that file you should be able to find the following:

private function parseResponse(PleskResponse $response, $module_row = null, $ignore_error = false)
    {
        Loader::loadHelpers($this, ['Html']);

        // Set the module row
        if (!$module_row) {
            $module_row = $this->getModuleRow();
        }

        $success = false;

Update that by adding a new line to log the raw response from Plesk:

private function parseResponse(PleskResponse $response, $module_row = null, $ignore_error = false)
    {
        Loader::loadHelpers($this, ['Html']);

        // Set the module row
        if (!$module_row) {
            $module_row = $this->getModuleRow();
        }

        $this->log($module_row->meta->ip_address, $response->raw(), 'output', false);

        $success = false;

Save that and make sure it's uploaded to the server, then try to access the plans again. Afterward, look at the module log and see if there is a second entry for the "Output" direction. Is there any data?

ashevillewebhosting · August 24, 2018

I updated the file as described, but the modules log looks the same to me?

Blesta Addons · August 24, 2018

in line 2260 add the fallowing line, what is the result

			print_r($service_plans->get($data));die();

ashevillewebhosting · August 25, 2018

With that at 2260, or above the private function line, I just get a blank screen when trying to access the modules or packages page.

Blesta Addons · August 25, 2018

3 hours ago, ashevillewebhosting said:

With that at 2260, or above the private function line, I just get a blank screen when trying to access the modules or packages page.

it should normally before the line

// Response is only an array if there is more than 1 result returned

and you should check the developer tools to see the output with F12 .

ashevillewebhosting · September 10, 2018

Hi all,

I was able to revisit this yesterday using a fresh install, this time adding both by Plesk servers in the module. I was able to add packages and provision accounts without issue when selecting the server that Blest ISN'T running on; however when selecting the same server as previously mentioned, which Blest IS running on, I ran into the same issue (no output in the logs).

These servers are identically configured, so I'm assuming it has to do with the location of the install... any ideas?

Thanks,
Justin

ashevillewebhosting · September 10, 2018

I went back and added the lines mentioned above... when adding the line below, server 1 (blesta locally installed) still doesn't work, and doesn't output error, server 2 works fine.

        $this->log($module_row->meta->ip_address, $response->raw(), 'output', false);

When adding the below to 2260, same for server 1, server 2 no longer works.

// Response is only an array if there is more than 1 result returned

Dev tools output for server 1:

1. module_email_tags:"{module.ip_address} {module.port} {package.type} {package.plan} {package.reseller_plan} {service.plesk_domain} {service.plesk_username} {service.plesk_password} {service.plesk_webspace_id}"
2. module_options:"↵<div class="title_row"><h3>Module Options</h3></div>↵<div class="pad">↵ ↵ <ul>↵ <li>↵ <label for="module_group">Server Group</label>↵<select name="module_group" id="module_group">↵<option value="select">-- Please Select --</option>↵<option value="" selected="selected">Any</option>↵</select>↵ </li>↵↵ <li class="module_row_field">↵ <label for="module_row">Server</label>↵<select name="module_row" id="module_row">↵<option value="1" selected="selected">VPS1</option>↵<option value="2">VPS2</option>↵</select>↵ </li>↵ <li>↵ <label for="plesk_type">Account Type</label>↵<input type="radio" name="meta[type]" value="standard" id="plesk_type_standard" checked="checked" />↵<label for="plesk_type_standard" class="inline">Standard</label>↵<input type="radio" name="meta[type]" value="reseller" id="plesk_type_reseller" />↵<label for="plesk_type_reseller" class="inline">Reseller</label>↵ </li>↵ <li>↵ <label for="plesk_plan">Plesk Service Plan</label>↵<select name="meta[plan]" id="plesk_plan">↵<option value="" selected="selected">-- Please Select --</option>↵</select>↵ </li>↵ </ul>↵↵ <script type="text/javascript">↵ $(document).ready(function() {↵↵ // Bind tooltips for this content↵ $('#module_group').closest('ul').blestaBindToolTips();↵↵ // If no group selected hide row listing↵ ↵ // If group changes, determine if row listing should be shown↵ $('#module_group').change(function() {↵ if ($('#module_group').val() != "")↵ $('li.module_row_field').hide();↵ else↵ $('li.module_row_field').show();↵ })↵ });↵ </script>↵ ↵ <script type="text/javascript">↵ $(document).ready(function() {↵ $('input[name="meta[type]"]').change(function() {↵ fetchModuleOptions();↵ });↵ });↵ </script>↵ </div>↵"

Name

Dev tools output server 2: PleskResponse Object ( [xml:PleskResponse:private] => SimpleXMLElement Object ( [@attributes] => Array ( [version] => 1.6.9.1 ) [system] => SimpleXMLElement Object ( [status] => error [errcode] => 1014 [errtext] => Parser error: Request is invalid. Error in line 2: Element 'get': This element is not expected. Expected is one of ( owner-id, owner-login, owner-all ). ) ) [xml_container_path:PleskResponse:private] => /packet/service-plan/get [raw:PleskResponse:private] => error 1014 Parser error: Request is invalid. Error in line 2: Element 'get': This element is not expected. Expected is one of ( owner-id, owner-login, owner-all ). )

WebhostingNZ.com · September 10, 2018

@ashevillewebhosting have you tried totally disabling your firewall for a minute and seeing if Blesta will then work with the server Blesta is installed on? Just to rule out any issue with the firewall that is. Don't forget to re-enable your firewall straight after.

ashevillewebhosting · September 11, 2018

4 hours ago, WebhostingNZ.com said:

@ashevillewebhosting have you tried totally disabling your firewall for a minute and seeing if Blesta will then work with the server Blesta is installed on? Just to rule out any issue with the firewall that is. Don't forget to re-enable your firewall straight after.

I tried this as well; stop using (systemctl stop firewalld) but same with the same result it seems.

ashevillewebhosting · September 11, 2018

Thanks all for your help on this. I'm really hoping to switch to Blesta if I can figure it out!

So I spun up another Centos/Plesk VM, installed Blesta, and connected it via Plesk Module to the the two previous servers, as well as itself. This time I had no issues with packages on the same server, but continued to get no response from the initial problem server. Looking like it's less of a Blesta/Plesk thing, and more of an issue with that particular server just not outputting a response?

Anyone know where I should be looking now? Any Plesk experts out there? These all have the same configurations essentially; same version OS, same version Plesk, same updates, etc.

Paul · September 12, 2018

If the issue has to do with Blesta running on the same server it's provisioning on, I wonder if it's related to this.. see https://docs.blesta.com/display/user/Plesk#Plesk-CommonIssues

Essentially you need to enable graceful restart of Apache. What happens is the account is created, but then Plesk restarts Apache and drops the connection over the API to Blesta.

ashevillewebhosting · September 12, 2018

44 minutes ago, Paul said:

If the issue has to do with Blesta running on the same server it's provisioning on, I wonder if it's related to this.. see https://docs.blesta.com/display/user/Plesk#Plesk-CommonIssues

Essentially you need to enable graceful restart of Apache. What happens is the account is created, but then Plesk restarts Apache and drops the connection over the API to Blesta.

Thanks Paul,

That's what I was thinking, but I created another Plesk vm and installed a Blesta trial on it as well, and it worked fine when querying itself. Well, it pulled the packages from it; but I then saw the issues you mention above when provisioning a new account. I'm at a loss as to why that initial server won't output a response when querying packages, no matter whether Blesta is local or not. It's the only one out of 5 Plesk VMs that isn't working.

Paul · September 12, 2018

1 hour ago, ashevillewebhosting said:

Thanks Paul,

That's what I was thinking, but I created another Plesk vm and installed a Blesta trial on it as well, and it worked fine when querying itself. Well, it pulled the packages from it; but I then saw the issues you mention above when provisioning a new account. I'm at a loss as to why that initial server won't output a response when querying packages, no matter whether Blesta is local or not. It's the only one out of 5 Plesk VMs that isn't working.

Sounds like the issue is unique to that one Plesk server. Have you reached out to Plesk support?

dyna56 · October 30, 2019

Hello!
Sorry for my English, I speak Spanish!
I have the same problem, is there a solution?

Paul · October 30, 2019

1 hour ago, dyna56 said:

Hello!
Sorry for my English, I speak Spanish!
I have the same problem, is there a solution?

Your Plesk server is not responding. Check your firewall, make sure the required ports are open on both ends.

dyna56 · October 30, 2019

What would be the required ports?

17 minutes ago, Paul said:

Su servidor Plesk no responde. Verifique su firewall, asegúrese de que los puertos requeridos estén abiertos en ambos extremos.

What would be the required ports?

Paul · October 30, 2019

2 minutes ago, dyna56 said:

What would be the required ports?

What would be the required ports?

It's defined in your module configuration, typically 8443 see https://docs.blesta.com/display/user/Plesk?preview=/2621908/6225988/plesk-server.png

See also https://support.plesk.com/hc/en-us/articles/213932745-What-ports-need-to-be-opened-for-all-Plesk-Services-to-work-with-a-firewall for a full list of Plesk ports, 8443 is plesk-https, 8880 is plesk-http. Your server should be able to make egress connections on these ports. These are non-standard ports and would not be open by default on most firewalls.

dyna56 · October 30, 2019

29 minutes ago, Paul said:

Está definido en la configuración de su módulo, normalmente 8443, consulte https://docs.blesta.com/display/user/Plesk?preview=/2621908/6225988/plesk-server.png

Consulte también https://support.plesk.com/hc/en-us/articles/213932745-What-ports-need-to-be-opened-for-all-Plesk-Services-to-work-with-a- firewall para una lista completa de puertos Plesk, 8443 es plesk-https, 8880 es plesk-http. Su servidor debería poder realizar conexiones de salida en estos puertos. Estos son puertos no estándar y no estarán abiertos de manera predeterminada en la mayoría de los firewalls.

Make the changes and it didn't work.
Disable the firewall and it didn't work either
Any other suggestions?

Paul · October 31, 2019

16 hours ago, dyna56 said:

Make the changes and it didn't work.
Disable the firewall and it didn't work either
Any other suggestions?

It can't connect. If it's not the firewall, you could check CURL SSL, check your settings make sure the port is correct. Make sure there is a path to Plesk from the server you have Blesta on. (Can you ping it?) Does your CURL support modern TLS? If Plesk is only listening on TLS 1.2 and your server can't negotiate 1.2 then it won't be able to connect.

There's an example script you can use to test what version of TLS you support, and confirm that CURL SSL is working. See https://docs.blesta.com/pages/viewpage.action?pageId=10551368#Debugging/Tools-CheckPHPCURL,outboundTLSVersion

Sign In

Plesk 17.8.11 Help

Question

ashevillewebhosting

23 answers to this question

Recommended Posts

Paul

ashevillewebhosting

Tyson

ashevillewebhosting

Tyson

ashevillewebhosting

Blesta Addons

ashevillewebhosting

Blesta Addons

ashevillewebhosting

ashevillewebhosting

WebhostingNZ.com

ashevillewebhosting

ashevillewebhosting

Paul

ashevillewebhosting

Paul

dyna56

Paul

dyna56

Paul

dyna56

Paul

Join the conversation

Browse

Activity