Paul

Blesta version 4.9.0-b1 (BETA 1) is now available. You can download it from right here (Client Area Login Required). Read the blog post announcement at https://www.blesta.com/2020/03/31/blesta-4.9-beta-released/ This is a BETA release. Beta releases are not considered stable enough for production use, and are UNSUPPORTED. DO NOT INSTALL IN A PRODUCTION ENVIRONMENT. Please report any bugs you find in the v4.9 beta bug forum. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.9.0-b1. For older releases see all Change Logs.

Thanks for the update, glad to hear it's working!

To revert you'll need to undo all the things you did when installing BlestaCMS. From their docs https://cms.blesta.how/ If you have uninstalled the BlestaCMS plugin under Settings > Company > Plugins, you may also be able to re-upload a copy of the Blesta files to restore them to their original, essentially undoing your custom modifications for BlestaCMS. Backup your files + database first just in case. The re-upload the full version of Blesta that matches the version you are running. Don't delete anything, you want to make sure /config/blesta.php is not removed and remains in place. Then, install the portal plugin for Blesta if it's not installed under Settings > Company > Plugins.

Did you enter the full URL to the logo in the field? If you copy/paste that URL into your browser does the logo load? It's a good idea to use https:// for the logo, some browsers will not load unsecured content, and that could explain why it doesn't appear also.

Will this be an issue for everyone using DA? Should this be the recommended tag in the doucmentation?

You need to use Blesta to create your DirectAdmin hosting accounts. Blesta will provision them, no need to do it manually through DirectAdmin any longer. Here's the docs for DA https://docs.blesta.com/display/user/DirectAdmin If you are provisioning from Blesta and getting an error, check the module log under Tools > Logs. Click a record to expand it and show the raw input/output.

New tasks were created for the Affiliate system, so the old task was closed. Those tasks are currently private, but will be made public closer to release. The Affiliate system is in active development, and it is integrated with the Order Manager. It will be able to be enabled or disabled through a new core feature that allows individual plugin actions to be disabled or enabled. I hope that makes sense. New tasks (many) related to Affiliate, old task closed as a result. Affiliate system in development.

Also, you're missing a comma before your password rule. Try this ruleset: { "Domain":{ "valid":{ "rule":["matches", "/^[a-zA-Z0-9][a-zA-Z0-9-]{1,61}[a-zA-Z0-9]\.[a-zA-Z]{2,}$/i"], "message":"Domain must not be empty." } }, "username":{ "valid":{ "rule":["matches", "/^[a-z0-9\\$\\%\\^]{6,8}$/i"], "message":"Please enter a username using alphanumeric characters between 6 and 8 characters in length. You may also include number characters like 123." } }, "password":{ "valid":{ "rule":["matches", "/^[a-z0-9\\$\\%\\^]{8,20}$/i"], "message":"Please enter a password using alphanumeric characters between 8 and 20 characters in length. You may also include special characters like '$%^'." } } }

I'm not sure you want this, try removing it from your rule: "negate":true,

Version 4.8.1 is now available, please see the release announcement. Patching Blesta See Patching Blesta in the User Manual for instructions. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Migrating to Blesta See Migrating to Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.8.1. For older releases see all Change Logs.

What do you sell with AWS? Lightsail? EC2 instances? Route53 DNS? They have so many products that it would be impossible to support them all. I've thought about a Lightsail module, it probably wouldn't be too difficult.. but it helps to understand what you are selling.

We don't really do ETA's, but I don't expect it to be very long at this point. Things are happening, and the fact that you won't need wimps anymore gives us an extra boost.

It's in development right now.

Are you provisioning accounts as an admin? If so, is the "Use Module" box checked? What is in your module log? Tools > Logs > Module tab. Click a row for CyberPanel to expand and show the raw input/output with the API.

Packages with pro-rata enabled will prorate the service to a specific date, e.g. 1st or 15th of the month, but not both. The cutoff date only determines whether the client should be billed for a partial month, or a full + partial month, the renew date will be the same.

Like which? Are you using Softaculous on another panel? Plesk and CentOS WP were requested, so we added those.

Great! Just FYI, the number 1 indicates company ID 1. So a 2nd company would have a directory named 2, third a 3, etc. I assume that's how you have things set, but since you didn't say it was missing from /uploads/2/ I thought it was worth mentioning. You wouldn't have 2 client_documents directories under /uploads/1/.

Uploads directory should be the parent directory of the 1 directory. Path is to uploads. Files should be written to the client_documents directory automatically. If they can't be written, and the directory exists, and the path is defined correctly in the settings, then it's likely an ownership or permissions issue.

Is your uploads directory defined and writable under Settings > System > General? What are the contents of your uploads directory? It should contain a "1" directory, and that directory should contain some others, one of which is for the download manager. They should be writable by your web server.

Open a ticket with them and they should be able to help.

Thanks, I got the details. Your server is not able to connect to us at all. Please check that port 443 egress is open at your firewall and that you have valid DNS resolvers in /etc/resolv.conf. Open a ticket with your hosting provider if you need help checking these.

I didn't get a PM from you after the one that included your license key.

The license is currently unactivated. It's likely that your server is not able to connect to us for license validation. Make sure port 443 egress is open at your firewall and that you have CURL SSL in your PHP. It looks like you completed Blesta installation though, did you install previously with a trial or another license key and are now updating the key? Did you move your Blesta installation? You can PM me your Blesta admin login if you want me to run a couple tests to see if it can connect to us or not.

What changed between the time it was working and when it stopped working? Did you upgrade or move Blesta, or update your server? Or is this a new installation?

Is it ko_kr? Please confirm and we'll add it.