[enom module problems]

2 hours ago, inspirenethost said:

Hi, Hope someone can assist me.

I have added the domains but it won't allow me to activate the following 

DNS Management ?	Email Forwarding ?	ID Protection ?	EPP Code

But as you can see from the image the module has been set to eNom

 But 

Any help regarding this please?

The Enom module does not yet support DNS Management, Email Forwarding, or ID Protection yet. This is a new feature, which has yet to be updated for all registrar modules who's APIs support the actions. See https://docs.blesta.com/display/user/Enom

[Cron job problem with Direct Admin]

30 minutes ago, sunrisepro said:

That exact cron job has been there since my last comment so it's been active for 6 days and cron still needs to be run manually. I'm looking into SSH access to my VPS.

I'm also using Blesta 5.02 - does that affect anything?

5.4.1 is the latest. It's possible that 5.0.2 does not have full compatibility with PHP 7.4, but I'm doubtful that is the issue here. If you can get SSH access and run that command via SSH it will tell us quite a bit.

[Cron job problem with Direct Admin]

On 6/7/2022 at 8:25 AM, sunrisepro said:

I'm stil stuck on this and have been running cron manually once a day. This is the path Blesta is showing in the Automation screen:

/usr/local/bin/php -q /home/username/domains/domain.com/public_html/subdomain/index.php cron > /dev/null 2>&1

This is what my host recommended using, including the correct path to php 7.4 (which I confirmed is the version in use):

/usr/local/php74/bin/php /home/username/domains/domain.com/public_html/subdomain/index.php

My host also noted that the '-q' flag is outdated and should not be used.

I'm also trying these cronjobs:

/usr/local/php74/bin/php /home/username/domains/domain.com/public_html/subdomain/index.php cron > /dev/null 2>&1
/usr/local/php74/bin/php /home/username/domains/domain.com/public_html/subdomain/index.php

All are set for 5 minutes, none are working. I'm happy to pay someone to resolve this for me as I'm lost on what could be wrong.

Based on this information, you should use:

/usr/local/php74/bin/php /home/username/domains/domain.com/public_html/subdomain/index.php cron > /dev/null 2>&1

If this doesn't work and you have SSH access you should try running it manually like this and see if it works:

/usr/local/php74/bin/php /home/username/domains/domain.com/public_html/subdomain/index.php cron

This last command should output to your shell any output from the cron. Take note of what is output.

If it works, run the following command to check what your cron job actually is:

crontab -l

 

 

 

[DirectAdmin Minimum Password Length]

On 6/3/2022 at 10:21 PM, Kal said:

@Paul, I've done some more tests and worked out that the problem is with the `DirectAdmin.password_length` setting. Regardless of what I set this to, the error appears if I enter a password of less than 12 characters. The `DirectAdmin.password_requirements` setting works as expected.

For example:

Configure::set('DirectAdmin.password_requirements', [
    ["A-Z"],
    ["a-z"]
]);
Configure::set('DirectAdmin.password_length', 9);

With these settings, a password of 'Abcdefghijkl' (12 characters) passes, but a password of 'Abcdefghijk' (11 characters) fails.

Is this a bug, or have I missed something?

That is unusual. I was able to reproduce this and have created the following task:

https://dev.blesta.com/browse/CORE-4667

[DirectAdmin Minimum Password Length]

19 hours ago, Kal said:

Something just occurred to me… I have two-factor authentication turned on in DA (as every security-minded admin should). Is this incompatible with the module?

I'm not familiar with DA's 2FA and nobody else has mentioned it, but if you are forcing 2FA then that may be the problem. I would suggest temporarily disabling it to check if it works.

Edit: Obviously if API commands require 2FA they ill never be able to be automated.

[Translation - strings are translated but do not show..]

7 minutes ago, Alexvw said:

Websites prove their identity through certificates that are valid for a certain period of time. The certificate for translate.blesta.com expired on 6/1/2022.

Thanks, I knew I had to have missed 1 or 2 when I updated a bunch of servers this week. FIxed.  

[Offering Additional Services By ResellurClub]

On 5/28/2022 at 11:34 AM, Franz said:

Unfortunately, they will not they got out of the module making business some time ago (Official ResellerClub WHMCS Module) to focus on their API. I was looking at using the universal module for this but I have no idea how to...but I think it's possible. 

Often times companies hire a dev firm to build the integration for them. They might have someone like that maintaining that integration from 10 years ago.

You can use the universal module and manually activate anything that you sell. See https://docs.blesta.com/display/user/Universal+Module#UniversalModule-ServiceOptions I linked directly to the service options section, because that and notifications is going to be the most important part of creating a Universal Module product. Any fields you want to request from the customer can be added here as service fields if they do not add to the cost. Any fields that would add to the package cost can be added as configurable options under Packages > Configurable Options, and assigned to an option group, that is then assigned to your package.

[DirectAdmin Minimum Password Length]

On 6/1/2022 at 4:13 AM, Kal said:

I have edited this file as described, removing unwanted requirements and reducing the minimum password length to 9, but as soon as I try to add a service I still get the same message:

Help!

(BTW, for anyone who still believes that character-composition requirements are a good idea, you might want to read the advice of security experts like Troy Hunt, NIST and Microsoft who all advise against this practice. See: Passwords Evolved: Authentication Guidance for the Modern Era. A poor decision for Blesta to turn this on by default IMO.)

When Blesta is not the authority on the password requirement, we go with the strictest possible requirement defined by the control panel. If the panel has a setting to force passwords of 12 characters, upper-case, lower-case, and a special character, then we require that so that there is not a failure to deploy a new account or update a password within the panel.

We are actually against such requirements that make it difficult for the user to remember the password while making it easy for a computer to guess. This sums up our thoughts on passwords: https://xkcd.com/936/

Regarding the issue, are you certain that you have modified the correct file? You don't have another copy of Blesta in another directory? You are using the DirectAdmin module and not another? The password you provided meets the password requirements for your DA server? The text of the error message will not change based on you changing the requirements, so if the password doesn't meet the requirements you set, you'll get the same error unless you modify that in:

/components/modules/direct_admin/language/en_us/direct_admin.php:$lang['DirectAdmin.!error.direct_admin_password.format']

 

 

[Translation - strings are translated but do not show..]

If the plugin was already installed then its name and description, including what is shown under Settings > Company > Automation will use the language at the time it was installed. You could uninstall and re-install the plugin, or more preferably (To not lose data by uninstalling the plugin), update the language in the cron_tasks table and plugins table

cron_tasks.name, cron_tasks.description
plugins.name

These are one of the few remaining things that do not pull the language dynamically.

[Force Namecheap Module to IPV4 only]

On 5/28/2022 at 12:53 AM, MDHMatt said:

As per their documentation found here

https://www.namecheap.com/support/api/global-parameters/

and described here

https://www.namecheap.com/support/api/intro/

they use whitelisted ipv4 address to control access to the api which you enter into your account page. Should you enter a non whitelisted ip it gives an error.

this could also be useful for people with multiple IP address who maybe want to limit what ip to use for api calls

Ok, this is unusual because an IP restriction on the API would normally mean that the API would restrict the IP for the source of the request. If you can specify any IP and it uses that, it could be spoofed to bypass the check. It doesn't make sense. I think the 1st comment in that documentation you linked sums it up well:

Quote

Can anybody explain my WHY ClientIp must be included in request? NameCheap API server already knows which IP calls it from, right? It is not only data redundancy, it's error-prone misconception. Client should authenticate itself (username+token), API server should check if remote IP is on the whitelist, configured on NameCheap's side.

It seems to me that this is something Namecheap should fix. Adding a field to specify the IP is a pretty hacky-fix.

The example in this thread of using an IP address of 127.0.0.1 for ClientIP, does this work universally? If so, the simpler solution may be to just specify 127.0.0.1 for ClientIP in all requests like the example code, rather than requesting it. OR, if the IP address = IPv6, then instead of using that address, send 127.0.0.1. Thoughts?

[Docker test deployment: Trial has already been issued for this domain]

4 hours ago, marcusdewald said:

Hello everyone,

I am currently evaluating several solutions, also Blesta.

I deployed a test instance via docker on my localhost but the trial license isn't available.

Error: 

Sorry, a trial has already been issued for this domain and is no longer valid. To obtain a new trial key, please contact sales@blesta.com. If you'd like to purchase a license, please visit www.blesta.com.

Someone here who could help me out or am I missing something important?

Best regards

If you are loading Blesta through your browser using the hostname "localhost", then it won't work due to abuse. Use a different hostname, even if its one you make up and add to your hosts file. Also make sure your docker container's IP doesn't change or the license will stop working.

[Force Namecheap Module to IPV4 only]

6 hours ago, MDHMatt said:

@Paul can we have a way to enter an ip in the module settings that lets us set the ClientIP? this could be auto populated using the existing code but having an option to adjust it would be great as namecheap get you to whitelist ip address to use the api with and only ipv4

What is the purpose of the ClientIP? Is this the IP address that API calls should originate from , or is it simply passed as a parameter in the API call? I have not looked into this myself. If $_SERVER['REMOTE_ADDR'] is returning an IPv6 address for your server, I can understand the fix posted above to force another IP. However, what are the implications if you enter an invalid IPv4 address, or one that does not resolve to this server? If the IP is just passed along to the API as a parameter, then I suppose it wouldn't cause any communication issues if the IP that made the request were different.

[Cron job problem with Direct Admin]

46 minutes ago, sunrisepro said:

The url is the correct path to Blesta's index.php - that's what should be accessed for the cron job?

This is not an issue, it was working fine for well over a year before I deleted the cron job by mistake last week.

The example Blesta shows under Settings > System > Automation is usually correct. Sometimes your path to PHP will be different, but it usually does a good job of detecting it.

If you deleted your cron job and don't remember what command you were using, probably you were calling a different version of PHP and that version met the system requirements while the new version does not.

[Which registrar modules implement DNS management, email forwarding, etc?]

On 5/14/2022 at 6:35 AM, planfourscott said:

I'm sandboxed with NameSilo and only EPP Code appears to work. Would love to have full functionality for this module.

What other modules have actually implemented DNS management, email forwarding and ID protection? I can't find anything in the specific module docs.

The Namesilo module does support DNS management, email forwarding, and ID protection. Are you running the latest version of Blesta? You must set pricing for these options, if they are enabled under Packages > Domains. Packages > Domains > Configuration: Configurable Options tab, click edit next to each option. Set pricing for each term/currency you offer.

[Client Cancellation]

On 5/15/2022 at 5:14 AM, LittleCreek said:

How can a client cancel a service? I thought it could be done by clicking Order History and cancelling from there but that does not seem to do anything. It doesn't actually cancel the service.

A client can click Manage next to their service in the client area, and there will be a cancel option.. assuming that you have enabled their ability to cancel under Settings > Company > Billing/Payment, by checking the option "Allow Clients to Cancel Services". If your client group settings are defined for the client, you may need to enabled it within their client group also, as these override the default company settings.

[Not selling domains]

18 hours ago, drz2 said:

I want to get out of the domain selling business. How do I set up the packages so that they will use only customer-provided domains? Thanks.

Your order form should use the "General" order form type instead of "Domains and Other". Modules determine what fields are required from the customer, so if you are selling shared hosting through a module like cPanel, Plesk, Directadmin, etc then the module will request a domain from the customer during checkout.

 

[Cron job problem with Direct Admin]

1 hour ago, sunrisepro said:

I managed to delete my cronjob by mistake, now I'm having trouble setting up a cron job that works.

I know the url to php, after asking my host. My command looks like this:
 

I set it to go off every minute, I check /admin/settings/system/automation/ after 1 minute, and it still shows that cron last ran 2 days ago when I ran it manually. I'm not sure what's wrong.

The cron should only run every 5 minutes, if it runs every minute it will be ignored. I realize you were probably just testing to see if it was working. Blesta does a generally pretty good idea of determining the command which you can see under Settings > System > Automation. Sometimes the path to PHP is wrong.

If your path to PHP is right, as well as the path to your cron, then your CLI PHP may be missing system requirements. You can check your logs under ../logs_blesta/ for any errors (Path defined under Settings > System > General) and you can, if you have SSH access, try running the cron command manually without sending the output to dev null. To run it via SSH, the command would look something like this based on what you provided:

/usr/local/php74/bin/php /home/username/domains/my_domain/public_html/subdomain/index.php

The most common problem is that the CLI version is missing ioncube or some other dependency.

[Invoice and Payment not showing]

Have you configured a payment gateway with a currency, and enabled both the currency and the gateway on the order form? Packages > Order Forms: Edit

[PHP 8 Support]

On 9/3/2021 at 4:12 AM, MDHMatt said:

Hey any news on PHP 8 support? Im aware its probably dependant on ionCube updating the code to support php 8.

As of Blesta 5.4, PHP 8 is supported through the hotfix-php8 SourceGuardian patch included in the release. As of now, ionCube has yet to release support for PHP 8, so we have implemented this alternative.  

[Migration Issue]

On 5/11/2022 at 6:18 AM, Himax said:

  

Hi Paul, I'll try to reply, in hope of an anwer.

All invoices seem to have been imported, including their detail lines.

I traced the mysql statements issued by the migration tool. It tries to insert twice the same row in the "invoices_recur_created" table (here is invoice id 521 while in the previous example it was 519).

637226 Query    INSERT INTO `invoices_recur_created` (`invoice_recur_id`, `invoice_id`) VALUES ('1', '521')
637226 Query    INSERT INTO `invoices_recur_created` (`invoice_recur_id`, `invoice_id`) VALUES ('1', '521')

Here the invoices_recurcreated table has an unique primary index over "invoice_recur_id+invoice_id".

Investigating further, it looks like the issue happens on a customer with "billable items" that were invoiced on multiple invoices, please see the attached image That is, WHMCS allows you to create a generic billable item and to specify that it has to be billed multiple times. So WHMCS will bill the item on multiple invoices at the predefined schedule. Then you can see on which invoices it was billed. So you have a back-reference or link from the invoices to the billable item. My guess is that the import module is trying to create this recurring billable item multiple times.

Perhaps it's enough to "ignore" the error or to check if the recurring item is already present and act accordingly.

Let me know, as this is blocking for me. I'd like to proceed with a paid license.

Thanks.

Thanks for the update. Tagging @Jono so he can take a look.

If you are willing to provide basic steps on how to create a billable item to generate multiple invoices in WHMCS as you indicated, we can try to reproduce for a test import.

[Can a customer order multiple add-ons?]

On 5/6/2022 at 12:30 PM, drz2 said:

Right now the add-ons feature on the order form is a radio button that allows only one choice. How can I set it up so that a customer can order multiple add-ons?

You can assign multiple addon package groups to a package group, in which case the client will be able to select 1 addon from each group.

[enom module problems]

1 hour ago, drz2 said:

OK, I got to trhe hidden packages by filtering "package groups". Then, I edited the .com and selected the enom module. Now, all seems okay. Thank you for your help!

Ok, very good, glad that worked!  

[enom module problems]

16 minutes ago, drz2 said:

No new error messages in blesta logs, after a re-try to set .com with the enom module--same result as before. No hidden packages under any module.

There are no hidden packages under Packages when you filter using "Show hidden Packages"? All domain TLDs should have a hidden package.

[[HELP] Paypal Checkout Standard]

On 5/3/2022 at 9:54 AM, PressWizards said:

Please add this to the Blesta documentation here:

https://docs.blesta.com/display/user/PayPal+Payments+Standard

The PayPal API Username, API Password, and API Secret can be found in PayPal, go to Account Settings > API Access > VP/SOAP API integration (Classic).

The direct URL is here:

https://www.paypal.com/businessprofile/mytools/apiaccess/firstparty/signature

Hope this helps others trying to find it as I was, since there are a ton of API options in PayPal now.

I realize it's optional but very helpful when trying to manage PayPal payments and want tighter integration so that it handles refunds as needed, without a lot of manual work. 

Thanks, we added a help box just below the table that lists the fields with this information. Much appreciated!  

[enom module problems]

5 hours ago, drz2 said:

I have the latest Blesta version (5.3.2) downloaded from Blesta. I set it up fresh and did not migrate TLD's. There is this domain-related entry in the logs_blesta folder:

[2022-05-04T00:14:34.356201+00:00] general.WARNING: E_WARNING: call_user_func_array() expects parameter 1 to be a valid callback, class 'None' does not have a method 'getTlds' {"code":2,"message":"call_user_func_array() expects parameter 1 to be a valid callback, class 'None' does not have a method 'getTlds'","file":"/var/www/vhosts/myclinicalsite.com/httpdocs/clients/app/models/module_manager.php","line":837} 

Looking forward to a fix. Thank you. 

Ok, that sounds like it's trying to use the "None" module, which is not a registrar module.

Try this.. under Packages, click the Filter icon and check the box "Show Hidden Packages" to filter by hidden packages, which are domain packages. Note the "Module" listed for all, in each status "Active", and sometimes "Inactive" will have some. Are any using "None" for the module? If so, backup your database as a precaution, and then try to delete the hidden domain package using "None" for the module.