Blesta not showing directadmin packages

[kikloo]

Hi,

I recently got a new directadmin based server and I configured it in blesta (which is on some other server), when I am trying to add package in blesta, its not populating the directadmin reseller packages I have created in directadmin. What am I doing wrong ?

Please help, thanks in advance.

Thanks.

[Tyson]

There may be an error with the request, or something is not configured correctly.

You should go to add a new package, select Direct Admin, and when no reseller packages show up, take a look a the module logs Logs under Tools > Logs > Module tab. There may be some details/errors in the API requests logged there that could point to the issue.

[MichaelCee]

Hi @kikloo you mention Reseller plans specifically, do your shared plans (if any) import in fine?

• Is the user set in your directadmin module an administrator that can provision reseller services?
• Is there a firewall blocking the two servers from communicating with eachother?
• Have you correctly entered the DirectAdmin server information and password?

[S.H.]

Hello, I have this same problem and I get this error when trying to save packages in Blesta

A DirectAdmin package is required.
An IP address is required.

 

[Tyson]

The DirectAdmin module requires those fields when creating a package. They should appear under the module options section of the package. If you don't see them, check your module and error logs for more information.

[S.H.]

8 hours ago, Tyson said:

The DirectAdmin module requires those fields when creating a package. They should appear under the module options section of the package. If you don't see them, check your module and error logs for more information.

This is what I see:

Direction 	Data 				Date 			Status
Input	myserver.myserver.net|getPackagesUser	2019-Nov-06 9:12:22 PM	 Success
Output	myserver.myserver.net|getPackagesUser	2019-Nov-06 9:12:23 PM	 Error
	a:0:{}	

 

[Paul]

16 hours ago, S.H. said:

This is what I see:

Direction 	Data 				Date 			Status
Input	myserver.myserver.net|getPackagesUser	2019-Nov-06 9:12:22 PM	 Success
Output	myserver.myserver.net|getPackagesUser	2019-Nov-06 9:12:23 PM	 Error
	a:0:{}	

 

Your DA server did not respond. Make sure your firewall on your Blesta and DA server has the DA ports open, they are non-standard so they are closed by default on most firewalls. Make sure your settings are correct. Make sure you have CURL SSL. If all the above is fine, make sure your server can negotiate a high enough TLS protocol that your DA server will accept. See https://docs.blesta.com/pages/viewpage.action?pageId=10551368#Debugging/Tools-CheckPHPCURL,outboundTLSVersion for how to test.

[S.H.]

9 hours ago, Paul said:

Your DA server did not respond. Make sure your firewall on your Blesta and DA server has the DA ports open, they are non-standard so they are closed by default on most firewalls. Make sure your settings are correct. Make sure you have CURL SSL. If all the above is fine, make sure your server can negotiate a high enough TLS protocol that your DA server will accept. See https://docs.blesta.com/pages/viewpage.action?pageId=10551368#Debugging/Tools-CheckPHPCURL,outboundTLSVersion for how to test.

Curl check script reports: TLS version: TLS 1.2.

Would anyone here by willing to try connecting to my DirectAdmin server, I can PM the login details. The server is new and empty, no client accounts have been made as yet so I am willing to do this if someone will help me. At least if it works then it would help me pinpoint which server has the issue, whether its the one with my Blesta installed or the one with DirectAdmin installed.

[brixsat]

Same problem here, reseller packages show, user packages in browser yes, in blesta no

[Jstuts5797]

On 2/9/2020 at 10:34 AM, brixsat said:

Same problem here, reseller packages show, user packages in browser yes, in blesta no

I too am having this issue as the others above. In my log in output I get the error as you all are above plus this line:  hn.hostname.com |getPackagesReseller
a:0:{}

[Shira]

On 11/7/2019 at 6:33 PM, Paul said:

Make sure your firewall on your Blesta and DA server has the DA ports open

which are?

[Shira]

On 3/21/2020 at 9:10 AM, Jstuts5797 said:

I too am having this issue as the others above. In my log in output I get the error as you all are above plus this line:  hn.hostname.com |getPackagesReseller
a:0:{}

Same issue here. Port 2222 is enabled in both TCP IN and OUT, even tried disabling the firewall temporarily.

[qba82]

Perhaps it is related to my bug report: