Jump to content

Paul

Blesta Developers
  • Content Count

    6,052
  • Joined

  • Last visited

  • Days Won

    730

Everything posted by Paul

  1. 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 '$%^'." } } }
  2. I'm not sure you want this, try removing it from your rule: "negate":true,
  3. Paul

    Blesta 4.8.1 Released

    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.
  4. 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.
  5. 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.
  6. It's in development right now.
  7. 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.
  8. 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.
  9. Like which? Are you using Softaculous on another panel? Plesk and CentOS WP were requested, so we added those.
  10. 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/.
  11. 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.
  12. 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.
  13. Open a ticket with them and they should be able to help.
  14. 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.
  15. I didn't get a PM from you after the one that included your license key.
  16. 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.
  17. 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?
  18. Are you talking about a domain & other order form where the domain is not auto populated for the cPanel domain field? This is because Blesta expects the field to have a specific name, and the author has given it a different name.
  19. For whatever reason your tickets cannot be imported. Make sure you have the IMAP PHP extension and the Mailparse PECL extension. To test this, you can: Enable error reporting your /config/blesta.php (Change ErrorReporting value from "0" to "-1". Disable your cron job Execute the cron command manually via SSH after the next import should run (when task not stuck spinning).. but don't direct output to /dev/null. e.g. /path/to/php /path/to/blesta/index.php cron See if any errors are output. Alternatively, you can check your ../logs_blesta/ log files. Settings > System > General will show the full path.
  20. What was the complete error and the output?
  21. I wonder if there should be a Package override for this, to not allow upgrades downgrades to this Package. Admins would be able to do it anyway if they want. This would allow all Packages in a Group to be disabled for upgrade/downgrade, or only specific ones. Maybe some Packages could be upgraded to and not others.
  22. You must correct the error that you got, then re-import. If that is the only error, then the import will be able to continue with importing all of those other things.
  23. When an error occurs, it's not able to complete the import. It's important to correct the issue, re-import on your fresh Blesta database (why we recommend backing up Blesta after installing, then restore your database backup before attempting another import). I would also recommend importing from a cloned WHMCS database so that you can make adjustments to your database. For example, one error was a currency code longer than 3 characters. You'd need to modify any currencies longer than 3 characters to be 3 characters, then retry the import. Same goes for any contacts that are not associated with any clients.
  24. Importer is trying to import a contact that has no client id associated with it. You may have some contacts that are not associated with a client in whmcs, check your database to see. whmcs does very little to enforce data integrity, so when something is expected to exist and it doesn't it causes issues.
×
×
  • Create New...