Paul

I would recommend putting Blesta on a different server than WordPress. WordPress often has vulnerabilities, which could let an attacker into all your customer data in Blesta. For integration, you can hire a company like Zomex to integrate the WordPress theme you buy with Blesta to make it look the same and match. This is what most people do.

Thanks. I see no reason why you should be logged out unless the hostname in your browser changed, or your IP changed, or the server path to your installed changed. Tyson is looking into this in more detail to see if it may be a bug.

SELECT * FROM `log_cron` WHERE `output` LIKE '%validate%'; Can you run this query on your database? Any results? If yes, interested in the start and end dates. This is the cron log that contains license validations, which should occur automatically as part of your normal cron run.

Please open a ticket with us so we can confirm the license is eligible for transfer. https://docs.blesta.com/display/support/License+Transfers

Settings > System > Automation. When is the date/time for the last cron run? What version of Blesta are you running? Do you have a cron job set up to run the command shown on that page every 5 minutes?

What module are you using? We have a task for cPanel to allow a config option that determines the server group. See https://dev.blesta.com/browse/CORE-3024 This would allow the creation of a dropdown for selecting the server group, and you would organize your server groups by location. However, I don't have an ETA on this task. For now, what I would recommend is creating a Package Group for each location, and cloning your Packages (selecting the right server group for the cloned packages) and assigning them to the new Package Group for that location. On your order form, they would be listed by group like this: USA Hosting - Plan A - Plan B UK Hosting - Plan A - Plan B .. etc Then they would select the Package within the group for the location they want.

Did you check that Blesta is sending out the email every hour? Tools > Logs > Email. Is there only 1 transaction recorded for the payment in Blesta, or are you seeing many transactions? (Check all statuses) Blesta sends the email receipt after receiving an IPN notification from PayPal, so no others should be sent unless Blesta receives multiple IPN requests. See Tools > Logs > Gateway log to see PayPal IPN request logs.

The goal is to remain backwards compatible, so far it's looking like that will be possible. Meaning that existing registrar modules should continue to work, and it shouldn't break when installing the domain manager. However, the domain manager may not be able to recognize pre-existing domain packages and take control over them. A way of conversion may be required to take full advantage of the domain manager with existing domains unless starting fresh for domains going forward.

Welcome back @PauloV Good to see you!

Have you tried the OpenSRS module available from here:? We do have a Vultr module, which supports the application installation images. No AWS integration at the moment. How did you hear about Blesta?

The renew price option in 4.6 is one of the core updates required for the domain manager, and can be used now to support a separate new and renew price for domains in the current system. A separate transfer price and better support for domains is coming. While I don't have an ETA yet, we have been making progress. I know that it's highly requested, and much needed, and our 4.6 release puts us 1 step closer in terms of underlying core functionality to support the domain manager.

4.6 beta 1 should be out as early as Tuesday/Wednesday. We may be able to add 2CO to Github, but not before 4.6 is released, it's not the right time to do it and would interfere with our release.

How long ago did you upgrade to 4.5.2? What version did you upgrade from? Try re-uploading all the files from the full 4.5.2 release If you have ever upgraded from version 3.x, make sure you've removed the files listed in the yellow alert box at https://docs.blesta.com/display/user/Upgrading+Blesta

It's possible, you should check that. The NOC PS module is a 3rd party module, and not supported by us, so I don't know if it has unique requirements. If it continued to work fine after upgrading to 4.5.2 then it may be compatible with 4.5.2. Check also the file logs, ../logs_blesta/ defined under Settings > System > General. The logs may have more information if there is an error involved. Also check your firewall and logs in NOC PS.

I see INPUT but no OUTPUT, it appears that your NOC PS server is not responding, or Blesta is unable to reach it.

Did you change anything recently? Upgrade Blesta, upgrade the NOC PS module, move your installation, etc? To view the module log for NOC PS, click anywhere in the row for the log on that page (not the "NOC Provisioning System (NOC-PS)" link)

@elzek1 Take a look at what Mike from Blesta.Store mentioned with your client ID's. Any imports must be done on a fresh Blesta installation, and we recommend making a backup of your Blesta install before attempting an import so you can restore and retry. I assume you are using Blesta 4.5.2?

Invoice creation automation task runs once per day. If it already ran today, then invoices won't be generated again until tomorrow. So if you're billing 14 days in advance, and it's 8 days until the service is set to renew, then it should be invoiced at the next run.

Maybe we should ship the unminified version with Blesta also.

I think Blesta version 4.6 may solve this for you. Beta soon.

You can configure your packages now for pro-rata, if they purchased a 1 year term then it would be prorated to June 1st or July 1st depending on what you set for the cutofff day. Then you can adjust the renew date and generate a 2nd invoice for June 1st - Jan 1st. After that it'll renew on Jan 1st each year. So, an extra manual step in there unfortunately. We might be interested in adding a prorata month option for yearly services if you want to make a feature request. Prorata option works best with monthly services, so if you have a monthly service you want to renew on the 1st each month, then placing an order will prorate it.. and you pay either partial month or partial month + whole month to get it to renew on the 1st. It doesn't work so well with yearly terms because it will still prorate it to the 1st of the next month not the 1st of a particular month.

One thing I'd like to see is an export directly to Campaign Monitor list, or Mailchimp, etc. Separate feature for a separate time though. CORE-3111 sounds fine with me, so long as the default option is to use system mail settings.

Welcome! The cPanel doesn't utilize any configurable options currently. You can create them, but the module will not detect and use them for provisioning. That's not a bad idea though. Since the cPanel server or server group is selected on the Package level, you'd need to have another Package for Bermuda with the Package configured to use a cPanel server group that contains your Bermuda cPanel servers, or a specific server for Bermuda. I'd suggest doing the following: Create your regular cPanel Packages, assigned to their own Package Group. Create another Package Group for Bermuda, call it "Bermuda Hosting" or whatever you want. Use the "Copy" feature under Packages to copy the Package, modify the name, price, package group, and cPanel server or server group for Bermuda and save. Repeat for all your Packages. Make sure both Package Groups are assigned to your order form (Packages > Order Forms: Edit). You can sort their display by drag and drop within the order form where the Package Groups are shown. You can sort the display of the Packages within their groups under Packages > Package Groups by clicking the row for the Package group and drag and drop packages within it. I hope that helps! You can make a feature request for using configurable options to override or set the cPanel server or server group at https://requests.blesta.com It's a good idea and something we'd be likely to add in the future.

Does the client have any contacts? What version of Blesta? What version of the widget?

At the time an invoice is generated, I believe we save the previous balance on the account. It might make sense to store the previous balance, but as you indicate it would be the balance at the time the invoice was generated, not including the generated invoice since application of payments/credits would occur later.