Paul

I don't have an ETA unfortunately.

Is it configured properly? I'm not aware of any other reports. LicenseCart has been accepting payments with BitPay, and so have we.

Where did you get the logo? Something that mixes the idea of chemical and servers together would make more sense. For example, a test tube coming out of a rectangular box or something. Still, better than the old one

Right now it's mostly geared toward plugin, module, gateway development. If we open it up to theme integrations as well I'll add you then. Cheers

Overall I like it, but Mike's right a nice logo will do wonders.

@siteAdmin I PM'd you a trial key you can use on localhost.

Would you prefer a direct Teamspeak integration or through TCAdmin?

We are working on it, beta 2 really soon.

I have created 2 tasks for this: CORE-2287 and CORE-2288 Please review and advise if you have any suggestions for the tasks beyond what is described.

The cPanel Extended module is not officially supported, but the first place I would look is in the module log. Tools > Logs: Module tab. If you see any requests, click anywhere in the row to expand the row and show the raw input/output. This assumes that the cPanel Extended module is logging actions to the module log. If so, the raw response will be helpful in determining what the error is.

Yes, thanks for the update. I'm not sure I understand the OPs issue with services, that sounds unusual and we would need more details to be able to replicate that. Upgrading from 3.x to 4.0 should work pretty much exactly the same as before.. but yeah, don't forget to run ~/admin/upgrade, there's some important database changes in there.

Certain fields are encrypted automatically, but modules and plugins can define which fields to encrypt. Because search operations cannot be performed on encrypted data, we usually don't recommend encrypting all fields, but that's a decision the developer should make. This page should give you a basic understanding of what is encrypted in Blesta and how it's performed: https://docs.blesta.com/display/user/Encryption

I have no experience with MariaDB's data-at-rest encryption or AWS key management service (I assume that's related to db encryption?). Are there any special requirements? According to https://mariadb.com/kb/en/mariadb/data-at-rest-encryption/, it seems like the application would be responsible for setting encryption on the tables. If so, then it would be unsupported.

Looks great, thanks for the contribution!

Thanks, the license is valid and eligible for transfer. There is a $25 transfer fee to be paid by the seller after a buyer has been found. Please open a ticket with us with the name and email address of the buyer when ready to transfer. https://docs.blesta.com/display/support/License+Transfers

That's exactly what we do.

Thanks for the feedback. If the web server is responsible for running the mailer, and the connection drops or the browser is closed, it's likely that it will be interrupted. I *think* this is how the competition works. We build it to be more rock solid than that, by queuing mailings for the cron to process. So, for Blesta, you can watch the email go out, but if you close your browser it will not interrupt anything.

The GoGetSSL module could use some improvements. Watch out for some news regarding TheSSLStore.

I like the idea of an IP block. One thing I want to do that I believe we have a task for is with the PHPIDS plugin, where it could issue a "csf -d IP" command on your Blesta server to block the attacker at the firewall. In this context, are you just asking for the ability to ban specific IPs from being able to say, place an order or login to the client area? Can you elaborate on how you would expect this to work?

Thanks for the information, I'll discuss rate limits with the team. Does anyone have a problem with mail being sent from the cron rather than from the browser? For me, I like being able to keep the window open and see the email go out when the cron starts, but not having to worry about leaving the page and interrupting the mailing.

Ok, just to clarify: You'd like the IP address field renamed to hostname? Trying to use a hostname now does not work because of an error check that expects an IP address? The Plesk module generates passwords that are considered insecure in Plesk by default. Is "Strong" the default password strength setting in Plesk? It's likely any modification to the password generation would be to simply meet the requirements that Plesk typically expects. In this case, it looks like it must be: 8 characters, contain upper and lower case letters, digits, and special characters.

Please PM me the license key so I can verify that it's legit and eligible for transfer

If you want to help, please do more testing. There will be more to test in beta 2, which we hope to have out really soon.

As Mike mentioned, start here - https://docs.blesta.com/display/user/Migrating+to+Blesta Do a backup of your fresh Blesta install so you can restore it and re-attempt.. do a test import to start with to see if there are any issues, and make sure your Blesta cron is DISABLED. 30K clients may take a while to import

Have you enabled GeoIP? Settings > System > General > GeoIP Settings. If setup, hovering over the IP address on a client profile and other areas will show information about the IP address.